Reference

rawontoto Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open an account, sign in on mobile, browse Live Roulette or use DANA and QRIS.

Account clarityWallet recordsCookie choicesAccess depends on local law
rawontoto rawontoto Privacy Policy for Your Account
CONTACT YOUR DATA TEAM

Get Privacy Policy Help Near Login

A clear contact path matters when a phone number, wallet reference or device record looks wrong. From your account support route, tell us which detail concerns you and include the relevant date or payment reference; please do not send a wallet PIN or full password. We can help with access questions, correction requests and policy-related concerns for accounts used on mobile or desktop.

Team online

Account support route

Use the support path connected to your account when a login record, phone verification detail or device entry needs checking. We will ask for account context rather than a wallet PIN.

Payment record request

For DANA, OVO, GoPay or QRIS questions, share the payment date and reference shown in your receipt. We use those details to locate the matching record without requesting your wallet password.

Correction request

If your contact detail or account record is inaccurate, state the field you want changed and why. We may verify account ownership before applying a correction or explaining the available route.

DATA HANDLING DETAILS

What We Do With Your Account Records

Privacy Policy choices should be understandable before you open the lobby, not hidden after a payment issue.

Account data

We use your contact details, phone verification status and account activity to create access, answer support requests and connect the correct wallet record. We do not ask for more account detail than the task requires.

Cookie controls

Cookies can keep your session and selected page settings available while you move from login to the lobby. You can clear or restrict them in your browser, although some account steps may then need to be repeated.

Device signals

A phone, tablet or desktop session may produce device and browser signals such as IP address and operating system. We use them to recognise unusual sign-ins and investigate access concerns, not to read wallet credentials.

Account security

Phone verification can be required before account access, and we may check session changes before discussing private records. Keep your password private and contact support if a sign-in does not match your activity.

Record retention

We keep account, support and payment-reference records for the time needed for service operations, security checks, disputes or legal duties. A retention question can be sent through the account support route.

Your requests

You can ask what personal data we hold, request a correction, ask about deletion where available or object to a particular use. We may confirm ownership before making a change to protect your account.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account steps you are most likely to encounter: phone verification, wallet references, cookies, device access and requests for changes. If your question is not covered, use the support route with the smallest useful detail, such as the affected field, device path or payment reference.

It covers account details, phone verification, sign-in activity, device signals, cookies, support records and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We use phone verification to confirm account access and help distinguish your session from an unfamiliar sign-in. It also gives support a safer way to discuss account records without exposing private wallet credentials.

No. We may retain a payment reference, amount and status for matching, but your DANA, OVO or GoPay password and PIN should remain with that wallet service. Never include them in a support request.

Use the account support route, identify the field that needs correction and provide the relevant account context. We may verify ownership before changing contact details, phone status or another private record.

The policy covers data created when you sign in through a phone, tablet or desktop browser. Device type, browser signals and IP data may support session checks, while cookies can keep login settings active.

We retain payment references and related account records for operational support, dispute handling, security checks or legal duties. Ask through support about a specific DANA, QRIS or bank transfer record and its retention category.

Yes. Send a data request through the account support route and describe the record you want to understand. We may confirm account ownership, then explain the available access, correction or deletion route.