Reference

slot dana Privacy Policy For Your Account

Our Privacy Policy explains how slot dana handles the details connected with your account, device, wallet status and support requests.

Clear data purposesMobile access detailsWallet privacy contextContact request path
slot dana slot dana Privacy Policy For Your Account
ASK ABOUT PRIVACY

Open A Support Path For Policy Questions

Privacy questions should have a clear route, especially when a login or wallet record needs checking.

Account request Send a privacy request from the signed-in account area and include your registered phone details. We can then match the request to the correct account record without asking you to repeat unrelated payment data.
Wallet record For DANA, OVO, GoPay or QRIS questions, share the transaction reference rather than a wallet password or secret code. Our support route uses that reference to check the relevant status.
Access help If phone verification blocks access to your privacy request, tell us which step stopped on your mobile browser. We can explain the required account check while keeping the request focused.
HOW DATA IS HANDLED

Explore The Privacy Controls Behind Access

We separate the data needed to operate an account from details used to answer a support request.

Account details

When you open an account, we record the details needed for sign-in and phone verification. We use them to identify your account, protect the login path and respond to a request tied to that account.

Device signals

A mobile browser may provide device and session signals when you sign in or move between the lobby and account area. We use these signals to spot unusual access and maintain the requested session.

Cookie choices

Cookies can remember a session and help us understand whether a page such as the Privacy Policy opened correctly. Your browser controls can remove or restrict them, although some account steps may then need repeating.

Payment references

A DANA, QRIS, bank transfer or virtual account reference helps us match a receipt and status request. We do not ask for your wallet PIN, password or one-time secret through a support message.

Account security

Phone verification is an account protection step before access. If you sign in from a new device, we may use existing account details and session signals to check that the request belongs to you.

Retention requests

We keep records only for the operational, security or legal purpose described in this policy and then assess them for removal. Ask through the account support route if you want correction or clarification.

Find Answers About Privacy Policy

These answers address the searches we expect before an Indonesian account is opened. They focus on what slot dana collects, why a device or wallet reference may appear in a record, how you can request a change, and which access wording applies when local requirements affect an account.

It covers account and phone verification details, device and session signals, cookies, payment references, support messages and retention. It also explains why we use each category and how you can request clarification.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account checks. We use those references to match a receipt or status request, not wallet secrets.

A mobile browser can send session and device signals when you sign in or move between account pages. We use them for session continuity and unusual-access checks, as explained in the Privacy Policy.

Use the support link inside your signed-in account, identify the record you want corrected, and describe the account step involved. We may ask for verification before changing a phone or account detail.

You can ask through the account support route for the categories connected with your account and the purpose for keeping them. The Privacy Policy explains retention for operational, security and legal needs.

Cookies may maintain a sign-in session or show whether a page opened correctly. Your browser can restrict or remove them, but some account actions may require another sign-in or verification step.

Yes. Account access and eligibility depends on local law. Our Privacy Policy still explains the data process for a permitted request, including phone verification, device checks and any support contact you make.