Reference

akun slot demo Privacy Policy for Your Account

akun slot demo Privacy Policy explains what we collect when you open an account, sign in, use the mobile lobby, or select DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record controlsMobile cookie choicesSupport-led requests
akun slot demo akun slot demo Privacy Policy for Your Account
REQUEST HELP

Privacy Questions Near Your Account Path

A clear support route helps when a Privacy Policy question meets a real account issue.

Account data request Ask us to locate the account details linked to your phone verification step.
Wallet record check If a DANA, OVO, GoPay or QRIS entry looks unfamiliar, send the payment reference…
Cookie assistance Tell us which device and browser you used when a cookie setting did not…
DATA HANDLING

What We Do With Your Privacy Choices

Our Privacy Policy is tied to actions you can recognise: opening an account, confirming a phone number, selecting a wallet, and returning to the lobby from a mobile browser.

Account details

We may hold the name or contact details you submit during account creation, along with the phone verification result needed for account access. These fields help us identify the correct record when you ask for a copy, correction, or deletion where local law permits.

Payment references

A wallet selection does not mean we need your wallet PIN. For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain transaction references, status and timing so a receipt can be checked against the account.

Cookies on mobile

Cookies and similar storage can keep a browser session connected to your account and remember a selected setting. On a phone, you can clear site data through browser settings; clearing it may require another login and phone check.

Security controls

We limit account discussions until we can match the request to the correct account. Keep your password private, sign out on shared devices, and contact support if a sign-in, phone verification or wallet record does not match your activity.

Retention approach

We keep records only for the period needed for account operation, payment reconciliation, security checks, dispute handling, or a legal duty. When a request conflicts with a required record, we explain the reason and identify what can still be changed.

Change request route

To request correction, access, deletion or a privacy explanation, use the support path inside your account and name the relevant record. We may ask for account verification before acting, then respond with the outcome or the reason a limit applies.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers cover the searches we hear most often before an account is opened. They explain the connection between account access, phone verification, local wallet records, mobile cookies and support requests. If your situation is not covered, use the account support route and mention the specific record or device involved so we can respond to the right question.

It covers account details, phone verification, sign-in security, cookies, payment references and retention. It also explains how to request access, correction or deletion of eligible data, and how local law affects those requests. Read it before opening an account so the data steps are clear.

We use the verification result to connect account access with the correct phone number and to reduce mistaken or unauthorised entry. We do not need your wallet PIN for this step. If the number is wrong, contact support through the account path before making a payment.

No. The policy concerns payment references, status and timing needed to match a DANA or QRIS transaction to your account. Your wallet PIN remains with the relevant wallet service. If a receipt does not match, send its reference through support rather than sharing a PIN.

Open the support link in your account area and ask for an account data access request. Include the account identifier and the record type, such as phone verification or a payment reference. We may verify ownership before explaining what can be supplied where local law permits.

Yes, you can request a correction or deletion through the same support route. We assess the request against account security, payment reconciliation and legal retention duties. Some records may need to remain stored, but we will explain the reason and identify any change that can be made.

Cookies can keep a browser session connected and remember a setting, which may reduce repeated sign-in steps. You can clear them in your phone browser settings, but this may sign you out and require phone verification again. The Privacy Policy explains the purpose of each relevant choice.

Use the support contact route available from the account access area and describe the sign-in problem without sending your password. Mention your account identifier, device type and whether the issue involves phone verification, cookies or a wallet reference. Access remains subject to local law.