Reference

Open dpboss Privacy Policy With Clarity

Your dpboss Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Clear data purposesWallet records explainedPhone verification context
dpboss Open dpboss Privacy Policy With Clarity
CONTACT PATHS

Check Privacy Questions Through Support

A clear support path helps you ask about the Privacy Policy without guessing which account detail matters.

Policy questions Ask us which account, device or transaction detail supports a specific process.
Wallet records For DANA, OVO, GoPay or QRIS questions, send the payment reference rather than a…
Data changes If your name, phone detail or contact record needs correction, state the exact change…
DATA PRACTICE

Browse dpboss Privacy Controls Clearly

We handle this policy area through ordinary account controls rather than hidden shortcuts.

Account details

We use the details you submit to create and maintain your account, complete phone verification and respond to account requests.

Device signals

A sign-in can create technical details such as device type, browser setting, approximate network context and session time.

Cookies

Cookies can keep a session active, remember a selected setting and help us understand whether a page loads correctly.

Wallet matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may be used to match a request with your account.

Retention

We keep account, security and transaction records only for the operational, dispute and legal period that applies to them.

Your request

You can contact us to ask about access, correction, deletion or the use of a particular record.

Ask About dpboss Privacy Policy

These Privacy Policy answers focus on the account decisions you may face before opening or using dpboss from Indonesia. We explain the records connected to phone verification, device sign-in, local wallets and support checks in direct terms. If your situation involves eligibility or lobby access, that question depends on local law, and we handle it where local law permits.

It covers details you submit for an account, phone verification results, device and session records, cookie settings, support messages, and payment references. It also explains why we use those records, how long we retain them, and how you can request access or correction.

Those wallet names identify transaction routes that may create account-linked references and status records. We use the minimum payment detail needed to match a receipt, confirm a request or answer a wallet question. We do not need your wallet password for that process.

A sign-in may create records about your device type, browser, session time and approximate network context. We use them to maintain the session, investigate unusual account activity and protect the phone verification path. They are handled alongside your account details, not as a separate profile.

Yes. Contact support with a clear request for access or correction and identify the account detail involved. We may confirm ownership through the phone verification step before responding. If a record is required for security, dispute handling or legal duties, we explain that limitation.

We retain wallet references, account activity and security records for the period needed to operate the account, resolve disputes, investigate unusual access and meet applicable legal duties. When the purpose ends, the record moves toward deletion or anonymisation under our handling process.

It applies to records connected with your account activity, including a request involving Lightning Roulette Room, Banjarmasin Night Spins or Fishing War Mobile Play. A title alone does not justify unrelated collection. We use relevant activity to provide the account service and answer a specific request.

Use our support path and state whether you want access, correction, deletion or an explanation of a record. Include your linked phone detail and any relevant receipt reference, but never send a wallet password or security code. Eligibility and access depend on local law where applicable.