Reference

Privacy Policy for DANA and Account Data

Your account details, DANA references and device access records have a clear place in our Privacy Policy.

Account dataWallet recordsDevice cookiesPrivacy requests
Explore Our Lobby Read FAQ
idealhoki88 Privacy Policy for DANA and Account Data
PRIVACY HELP DESK

Get Help With Privacy Requests

A clear contact route matters when you want to ask about your personal data. Start from the support path attached to your account and describe the request, the phone number on the account and the relevant wallet reference if your question concerns DANA, OVO, GoPay or QRIS. We use those details to locate the right record without asking you to send a wallet password. If access stalls after phone verification, contact us through the same account support route and we will separate a login issue from a privacy request.

Team online

Account privacy path

Use the support route inside your account to ask which personal details we hold, why they are used or whether a correction is possible. Include your verified phone number so we can match the request safely before discussing account records.

Wallet data question

For a DANA, OVO, GoPay or QRIS query, add the transaction reference and approximate date rather than a wallet password or PIN. We can use the reference to trace the account record while keeping sensitive wallet credentials outside the request.

Access issue route

If phone verification or a mobile login blocks your request, tell us the device path you used, such as Android browser or desktop browser. We can first restore the account route, then handle the Privacy Policy request attached to it.

DATA CONTROL MAP

How Device And Cookie Data Stays Managed

We keep our Privacy Policy practical by explaining the handling steps behind account access. Phone verification confirms the account route; wallet references help reconcile DANA or QRIS activity; cookies remember session choices…

Account creation

We collect the details needed to create and maintain your account, including a phone number and verification result. The account step gives us a reliable way to connect later privacy requests with the correct person instead of relying on an unverified message.

Payment references

A wallet or bank record may show a method, amount reference, status and time, but it is not your wallet password. DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI references help us reconcile activity and answer account questions.

Cookies and sessions

Cookies can keep a signed-in session and remember selected settings on the device you use. You can adjust browser cookie controls, though disabling them may require another login or prevent the account route from working as expected.

Device protection

Browser type, device details, IP address and login time can help us spot an unusual access pattern. If you switch from mobile to desktop, these signals support an account check without giving us access to private files stored on your device.

Retention period

We retain account, payment and security records only for the operational, dispute, fraud-prevention or legal purpose that requires them. When a purpose ends, we delete, anonymise or restrict the record where practical and where local law permits.

Changes and requests

You may ask for a copy, correction, restriction or deletion of relevant personal data through our account support path. We may request phone verification or another account check before acting, and some limits depend on local law and record-keeping duties.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the searches we expect from an Indonesian account holder. We explain the data connected with login, phone verification, wallet references, cookies and support requests without asking you to share private credentials. If a request concerns eligibility, deletion or access outside Indonesia, the outcome depends on local law. Use the account support route when you need a record checked against your own details.

It covers account creation, phone verification, wallet and bank references, device signals, cookies, support requests, retention and data rights. It also explains when operational providers may handle records for payment matching, account security or technical delivery, with access depending on local law.

We use your phone number to create the account route, complete verification and connect a later privacy request to the right account. It can also help us investigate a blocked login. We do not need your DANA, OVO or GoPay password for this step.

Our records can include the selected method, transaction reference, status, amount reference and time needed to reconcile account activity. QRIS and DANA credentials remain with the relevant wallet service. Send a reference, not a PIN or password, when asking us to trace a payment record.

Yes. Use the account support path and state whether you want a copy, correction, restriction or deletion of specific records. Include your verified phone number and a precise request. We may confirm account control first, and the available action depends on local law.

Cookies can keep your session and selected settings working when you use a mobile browser. Device and browser details may also help identify unusual access. You can change cookie controls in your browser, but disabling them may require a fresh login or affect account access.

We keep records for the period needed for account operation, payment reconciliation, security checks, disputes or legal duties. After that purpose ends, we delete, anonymise or restrict the record where practical. Some retention periods cannot be shortened when local law requires the record.

Start with the support route inside your account and describe the data request clearly. For a wallet question, add the DANA, OVO, GoPay, QRIS or bank reference involved. If you cannot pass phone verification, explain the device path and request account-access help first.

Related Pages

idealhoki88 Indonesia Sriwijaya Gold Megaways Badminton Sudirman Cup Bet About Us idealhoki88 Casino