Reference

Privacy Policy for Your Account Data

Our ratu303 slot Privacy Policy explains what we collect when you open an account, use a mobile browser in Jakarta, or check DANA and QRIS status.

Account dataWallet recordsCookie choicesAccess requests
ratu303 slot Privacy Policy for Your Account Data
CONTACT ROUTES

Where To Ask About Privacy Requests

A clear contact path matters when a privacy question affects your account or wallet record. We ask you to use the support route connected to your account access page, so we can match the request with the correct profile without asking you to post personal details publicly. Include your account identifier, the subject of the request and any relevant DANA, OVO, GoPay or QRIS reference, while removing passwords and one-time codes.

Team online

Account access

Choose the privacy contact path shown with account access and identify the account email or phone detail you used. We may ask for a simple account check before discussing records, so a request is not disclosed to the wrong person.

Wallet record

For a DANA, OVO, GoPay or QRIS privacy question, share the transaction reference and date rather than wallet credentials. We use that limited detail to locate the relevant record and explain its handling without requesting your wallet PIN.

Correction request

If your account detail needs correction, send the specific field and the accurate replacement through our support route. We review the account record, may confirm phone verification, and reply with the available change or the reason a record must remain.

DATA PRACTICE

What Your Privacy Settings Cover

Privacy control is practical when each record has a clear purpose. We separate account identity, device activity, cookie preferences and payment references so your request can be handled at the right level.

Data collection

We use details you enter during account creation, sign-in and verification, together with activity records needed to maintain the requested session. This can include browser type, device signals and account events connected with the casino or sportsbook areas.

Cookies

Cookies can keep your selected session and remember privacy choices on the same browser. If you clear them, the next visit may ask you to sign in again or select settings again; cookie changes do not erase account records automatically.

Account security

Phone verification before account access helps us compare a request with the account record. Never send a password, wallet PIN or one-time code to support. If a mobile device is shared, sign out and clear the browser session after checking your privacy settings.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may be used to reconcile account activity. We retain the reference needed for that purpose, but our privacy route does not require your wallet password or full payment login.

Retention choices

We keep records only for the period connected to account service, security checks, transaction reconciliation or legal duties. A request to remove data is assessed against those purposes, so some payment or verification records may need to remain.

Policy changes

When this Privacy Policy changes, we place the revised wording on the policy page and identify the effective version. Check the page before opening an account or after a major account change, especially when using a new device in Indonesia.

Privacy Policy Questions Before Account Access

These Privacy Policy answers focus on the searches Indonesian customers make before opening an account. We explain account records, cookies, payment references, correction requests and access limits in direct terms. If your question concerns a particular record, use the account-linked support route and avoid sending passwords, wallet PINs or one-time codes.

It covers details you submit for an account, sign-in and phone verification, plus device signals, cookies, account events and payment references. It explains why we use those records, how long they may remain, and how you can ask for access or correction.

Yes. The Privacy Policy includes references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We may use a reference, date and status to reconcile an account event, but our support route does not need your wallet PIN or one-time code.

Where local law permits, you can request access to personal data linked with your account. Send the request through the account-linked support route and include the relevant account identifier. We may complete phone verification first to prevent disclosure to the wrong person.

Cookies can preserve a sign-in session and remember your selected privacy choices in a mobile browser. Clearing cookies may sign you out or reset those choices. Device and account records are handled separately, so clearing browser data does not automatically remove them.

You can ask us to correct an inaccurate account field through the privacy contact path. Removal requests are assessed against account service, security, payment reconciliation and legal duties. Where local law permits, we explain which records can change and which must remain.

Use the support route shown beside your account access area and describe the privacy concern without sending passwords or wallet credentials. Add a payment reference only when relevant. We may request phone verification before discussing account data or a DANA, OVO, GoPay or QRIS record.