Reference

doku303 Privacy Policy For Your Account

Your doku303 Privacy Policy page explains how we handle account details, device access, cookies and payment references before you open the lobby.

Account dataCookie choicesWallet referencesAccess requests
Explore Our Lobby Read FAQ
doku303 doku303 Privacy Policy For Your Account
CONTACT ROUTES

Get Privacy Help Beside Account Access

A clear contact route matters when a privacy question appears during login or a wallet check. We keep privacy requests close to the account support path so you can identify the relevant account step without sending sensitive details through an unrelated route. Tell us whether your question concerns cookies, phone verification, DANA, QRIS or a device session. We will use the account context you provide to locate the request and explain the next step.

Team online

Account support path

Use the support route connected to your account when you need a Privacy Policy answer. Include the account identifier requested on that screen, but do not send your password or wallet PIN. We can then connect your question to login, verification or cookie records.

Payment record check

If a privacy request concerns DANA, OVO, GoPay or QRIS, tell us which wallet status or transaction reference you are asking about. We use that context to separate payment matching data from account data and explain what can be corrected or removed.

Device access question

When a phone or desktop session appears unfamiliar, contact us through the account help route and identify the device step. We can explain the related session record, help protect account access and describe how cookie or device data is handled.

DATA HANDLING

Inside doku303 Privacy Controls

We treat the Privacy Policy as an operating process, not a label placed beside the lobby. Account creation, phone verification, wallet matching and device sessions each produce a different kind of record…

Account creation

When you open an account, we use the details needed to establish that account and connect it with the phone verification step. Our Privacy Policy explains the purpose of each requested field, so you can distinguish account access data from optional browser or cookie signals.

Cookie handling

Cookies can help keep your session connected while you move from login to a lobby page. We describe their role in the Privacy Policy and separate session needs from broader preference signals. You can ask support how a particular cookie record relates to your account visit.

Wallet references

DANA, OVO, GoPay and QRIS may create payment references when you check wallet status. We use those references to identify an account step or reconcile a request, not to expose your wallet PIN. Bank transfer and virtual account references follow the same limited-purpose approach.

Session security

Login records and device signals help us identify an unusual account session, including a change between mobile and desktop access. If a session does not look familiar, use the account support path and ask us to explain the record before continuing with account actions.

Retention requests

We keep records for account operation, security checks, dispute handling or legal duties, then assess whether continued retention is needed. A Privacy Policy request can ask about a specific record, its purpose or its retention basis. Some records may remain where a legal duty applies.

Change or correction

You can ask us to correct an inaccurate account detail or clarify how a device, cookie or payment reference is linked to you. Include the affected account step rather than a password or PIN. We use that route to verify the request and explain the result.

Privacy Policy Questions About doku303

These Privacy Policy answers focus on the questions you are most likely to have before opening an account or asking for a data change. We cover account creation, phone verification, cookies, local wallet references, device sessions and access requests. If your situation is different, use the account support path and name the exact step you want us to check.

The doku303 Privacy Policy covers account details, phone verification, login records, device signals, cookies and payment references. It explains why we use each type of data, how retention works and how you can ask for clarification or correction through the account support path.

We collect the account details needed to create access and complete the phone verification step. Login activity, device signals and cookie records may also support session continuity or security. The Privacy Policy explains these purposes and the choices available for questions about a record.

When you use DANA, OVO, GoPay or QRIS, we may handle a payment reference or wallet status linked to an account step. We use that reference for matching and support, not for exposing your wallet PIN. Ask us to clarify a specific payment record.

Yes, you can ask us to correct an inaccurate account detail or clarify how it is used. Use the account support route, identify the affected account step and provide only the details needed to verify the request. We will explain any legal reason a change cannot be made.

Cookies can keep your mobile session connected as you move from login to the lobby, while preference signals may support a more consistent visit. Our Privacy Policy explains their roles. If you want a cookie-specific answer, tell support which device session you mean.

We retain account, security, dispute and payment-reference records only while they serve account operation, protection, dispute handling or legal duties. Retention can differ by record type. You may ask which purpose applies to a particular record and whether continued storage is required.

Yes. Where access or eligibility is discussed, it depends on local law. Our Privacy Policy explains how we handle account and device data within that context, but it does not change legal requirements. If your location or access status is unclear, contact support through your account path.

Related Pages

doku303 Indonesia FAQ Account information Live In-Play Football About Us