Reference

bds168 Privacy Policy for Indonesia Accounts

bds168 Privacy Policy explains what we collect when you create an account, complete phone verification, sign in from mobile, or check DANA and QRIS wallet status.

Account dataDevice controlsWallet recordsYour privacy requests

Explore Our Lobby Read FAQ

How Our Privacy Policy Applies in Indonesia

bds168 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers details you provide during account creation, including your phone number and verification result, plus records created when you sign in, contact support, or request a wallet action. We may record device type, browser signals, session time, approximate location, and security events so

1
we can identify unusual access and keep your account protected. Payment references can include DANA, OVO, GoPay, QRIS, bank transfer, or virtual account details, but we use them to match a request rather than to collect wallet credentials. We retain records only for operational, dispute, security,
2
or legal needs, then remove or anonymise them when they are no longer needed. Access and eligibility depends on local law. You can ask what we hold, request a correction, or ask about deletion through our account help path. This policy applies to our Indonesia-facing service
3
where local law permits.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Where To Ask About Your Privacy Policy Data

A clear contact route matters when a phone check, login event, or wallet reference appears unfamiliar. We handle privacy questions through the account help path, so your request can be matched to the correct profile without asking you to post personal details in a public channel. Keep your request specific and include the account step involved.

Team online

Account help path

Use the account help route to ask what personal data is linked to your phone verification, sign-in history, or profile. We may request proof that you control the account.

Wallet data query

Ask us to check a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference. We can explain the record without requesting your wallet password or security code.

Access concern

If a mobile or desktop sign-in looks unfamiliar, contact us through account help and describe the device path. We can review security events and guide the next account protection step.

SIX DATA CONTROLS

Six Controls Behind Your Account Data

We keep the Privacy Policy practical by tying each data use to an account action you can recognise.

Collection at signup

When you open an account, we collect the details needed for profile creation and clear phone verification before access. We do not need your DANA, OVO, or GoPay password for this step.

Device and browser signals

A mobile browser or desktop session may create records such as device type, browser version, session time, and security events. These signals help us investigate an unfamiliar login without reading your private files.

Cookie choices

Cookies can remember sign-in progress, protect a session, and help us understand which Privacy Policy page brought you to an account action. You can manage browser cookie settings, though some access steps may then require repetition.

Account protection

We use phone verification, session checks, and account activity records to reduce unauthorised access. Never send a password, wallet PIN, or one-time security code through a support request.

Retention decisions

We keep account, payment-reference, and security records for as long as needed for service operations, disputes, fraud checks, or legal duties. When that purpose ends, records are deleted or anonymised where practical.

Changes and questions

You can request access, correction, or clarification through the account help path. Tell us which record concerns you, such as a QRIS reference or device event, so we can respond accurately.

Privacy Policy Questions For bds168 Accounts

These answers focus on the questions you are most likely to ask before opening an account or checking a wallet record. If your situation involves a particular device, payment reference, or phone verification event, use the account help path so we can address the relevant Privacy Policy section.

It covers account details, phone verification, device and browser signals, cookies, support messages, security events, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account requests.

We use your phone number to create and protect your account and to complete the clear verification step before access. We do not ask for your wallet password or PIN during this process.

The policy allows records such as device type, browser version, session time, and security events when you sign in. These details help us assess unfamiliar access; they do not give us access to private files on your device.

We may keep a payment reference, amount status, and related account event for reconciliation, support, security, or legal needs. We do not need your DANA or QRIS password to match that request.

Yes. Use the account help path and identify the record, such as your phone verification detail, device event, or wallet reference. We may verify account control before responding, and timing depends on local law.

We retain records while they support account operations, payment reconciliation, security checks, disputes, or legal duties. After the purpose ends, we remove or anonymise them where practical and where local law permits.

Contact us through account help and describe the mobile or desktop sign-in, approximate time, and account step involved. Do not include a password, wallet PIN, or one-time security code in your request.

bds168 Privacy Policy for Indonesia Accounts

Where To Ask About Your Privacy Policy Data

Account help path

Wallet data query

Access concern

Six Controls Behind Your Account Data

Collection at signup

Device and browser signals

Cookie choices

Account protection

Retention decisions

Changes and questions

Privacy Policy Questions For bds168 Accounts

01 What does the bds168 Privacy Policy cover?

02 Why does bds168 need my phone number?

03 Does the Privacy Policy record my mobile device?

04 How does bds168 handle DANA and QRIS data?

05 Can I request a copy or correction of my data?

06 How long does the Privacy Policy allow data retention?

07 Who should I contact about an unfamiliar login?

Related Pages