Reference

disa4d Privacy Policy For Your Account

disa4d Privacy Policy explains how we collect, use and protect the details you provide when opening an account, checking wallet status or entering the lobby.

Clear data purposesWallet activity contextAccount access stepsPolicy contact path
Browse the lobby Read FAQ
disa4d disa4d Privacy Policy For Your Account
CONTACT ROUTES

Get Privacy Help Beside Your Account

Privacy questions should be easy to raise while you are looking at the account area.

Account request Use the account support path when you want to ask what personal details we…
Wallet record For a DANA, OVO, GoPay or QRIS question, mention the payment name, approximate time…
Access concern If a new device, browser session or phone verification event looks unfamiliar, contact us…
DATA PRACTICE

What We Keep Clear At disa4d

We handle privacy as part of the account path rather than as a separate promise hidden from the cashier area.

Account details

We collect details needed to create and maintain your account, including information connected with the phone verification step. This lets us distinguish your account from another account and helps us explain why access may pause when a required detail does not match.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account request can create a reference, amount status and time record. We use that trail to match the correct account and investigate a missing receipt without storing your private wallet PIN.

Cookies

Cookies and similar browser storage can remember a session, preserve account flow and help us see whether a page request belongs to the same device session. You can manage browser settings, though changing them may interrupt login or require another account check.

Device security

We may record device type, browser details, sign-in time and session signals to identify unusual access. If you move from mobile to desktop, these signals help us ask for the right account check rather than treating every change as a payment problem.

Retention period

We keep records only for the operational, security or legal period connected with their purpose. A payment reference may remain while an account or required record needs reconciliation, after which handling follows our deletion and retention obligations under applicable local law.

Change requests

You can ask us to access, correct or remove eligible personal details through the account support route. Tell us which record you mean and why; we verify account ownership first, then explain what can change and what must remain for a legal or security reason.

Privacy Policy Answers For disa4d

These Privacy Policy answers address the account and wallet questions you are most likely to ask before opening access. We keep the wording practical: what we collect, why a device or payment reference appears, how to request a change and where local law affects the response. If your situation is not listed, use the account support route and describe the record you want us to check.

The Privacy Policy covers account details, phone verification, device and browser signals, cookies, payment references and support requests. It explains why we use each category, how we connect it to your account and how you can ask about access, correction or removal where local law permits.

Phone verification helps us connect the person entering the account with the account record we hold. It can also reduce confusion when a mobile or desktop session changes. We use the verification result for account access and security checks, not as a request for your wallet password.

Yes. The Privacy Policy includes references created by DANA, OVO, GoPay and QRIS activity, as well as bank transfer and virtual account records. These references help us match a receipt or status to the correct account without needing your wallet PIN.

You can send an access request through the account support route and identify the account record you want checked. We may need to confirm ownership before responding. The records we can provide, and the format or timing of the response, depend on local law.

Describe the detail that appears wrong, explain the correction and include your account identifier through the support path. We check the request against the account before changing anything. A correction may be limited when the original record must remain for security, payment tracing or legal duties.

Device type, browser details, session time and related signals help us recognise ordinary access and spot an unfamiliar session. They are useful when you move between mobile and desktop or when account access stalls. We use them for account security and operational checks.

Send a deletion request through the account support route, name the records concerned and confirm that you control the account. We assess the request under applicable requirements. Some payment, security or legal records may need to remain for a defined purpose where local law permits.

Related Pages

disa4d Indonesia About Us FAQ Access guide Live Blackjack Gold