Reference

rakatoto Privacy Policy Explained Clearly

rakatoto Privacy Policy sets out how we collect, use and protect the account details that help you reach the lobby, including records connected with DANA, OVO, GoPay and…

Account dataWallet recordsCookie choicesPolicy requests

Explore Our Lobby Read FAQ

How DANA and QRIS Records Are Used

rakatoto Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy applies when you open an account, complete phone verification, sign in from a mobile browser or contact our support path. We may receive details you submit, such as your phone number and account credentials, plus technical details such as device type, browser session,

1
IP address and security events. Payment activity can include the selected rail, transaction reference, wallet status and bank-transfer or virtual-account confirmation; we do not treat a payment reference as permission to use your wallet for another purpose. We use these records to provide account access, check
2
unusual sign-in activity, reconcile deposits or withdrawals and answer policy requests. A lobby route, including Speed Baccarat or Wild Wild Riches, may be linked to an account event for service security. Access depends on local law, and this policy applies where local law permits.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP WITH RECORDS

Where Your Privacy Questions Go

A clear support route matters when you need to ask what we hold or why a wallet record appears.

Account access If phone verification or a device session blocks your request, use account help and include the affected sign-in time. We use those details to locate the relevant security record without asking for your wallet password.

Wallet record For DANA, OVO, GoPay, QRIS, bank transfer or virtual-account questions, provide the transaction reference and status shown in your account. We can then match the request to the correct payment event.

Policy change To ask for a correction, access copy or removal where permitted, send the request through account help. We may ask for account verification before changing records connected to your identity.

HANDLING DETAILS

What We Do With Account Data

Our handling process follows the account action that created each record rather than treating every detail alike.

Collected details

We collect details you enter during account opening and phone verification, together with device, browser and session signals created when you sign in. Required fields are used for access and account protection.

Cookie control

Cookies and similar browser storage can preserve a sign-in session and remember a selected setting. You can manage browser permissions, although removing required storage may interrupt account access.

Account security

A new device, repeated failed sign-ins or an unusual session can create a security event. We use that event to check access and may request phone verification before restoring the account.

Payment matching

A DANA, OVO, GoPay or QRIS reference helps us match a wallet status to your account. Bank-transfer and virtual-account references serve the same reconciliation purpose without changing your account profile.

Retention period

We retain account, security and transaction records only while they support the stated service purpose, a legal requirement or an unresolved dispute. When no such reason remains, the record enters our removal process.

Your request

You may ask what account data we hold, request a correction or ask about deletion where permitted. Send the request through account help with enough detail for us to verify the correct record.

Privacy Policy Questions About rakatoto

These answers focus on the records you are most likely to notice while using an Indonesian account. They cover phone verification, mobile sessions, local wallet references, cookies, retention and the route for asking us to inspect or change your data.

The rakatoto Privacy Policy covers account details, phone verification, device and browser signals, cookies, security events, support requests and payment references connected with DANA, OVO, GoPay, QRIS or bank rails.

Phone verification helps us connect you with the correct account and investigate unusual access. We may request it before restoring a session or completing an account-data request, where local law permits.

Yes. When you sign in from a mobile browser, we may record device type, browser session and security signals. These details help maintain access and identify a session that needs checking.

We use DANA and QRIS references to match a payment status with your account and resolve a support request. The reference is handled as a transaction record, not as permission for unrelated wallet activity.

You can ask for an account-data copy through account help. Include your account phone number and request details; we verify the request first, then respond according to applicable law and available records.

Send a correction request through the signed-in account help path and identify the field that is wrong. We may ask for phone verification before changing identity, wallet or security records.

We consider removal when the stated service purpose, legal requirement and any unresolved dispute no longer require the record. Requests are assessed individually, and access depends on local law.

rakatoto Privacy Policy Explained Clearly

Where Your Privacy Questions Go

What We Do With Account Data

Collected details

Cookie control

Account security

Payment matching

Retention period

Your request

Privacy Policy Questions About rakatoto

01 What does the rakatoto Privacy Policy cover?

02 Why does rakatoto need my phone verification?

03 Does the Privacy Policy cover mobile browser data?

04 How are DANA and QRIS details handled under this policy?

05 Can I request a copy of my rakatoto account data?

06 How can I ask rakatoto to correct my data?

07 When does rakatoto remove personal records?

Related Pages