Reference

Open rikatoto Privacy Policy with clarity

The rikatoto Privacy Policy explains how we handle your account, wallet and device data before you open the lobby.

Account dataWallet recordsCookie choicesSecurity steps
rikatoto Open rikatoto Privacy Policy with clarity
CONTACT ROUTES

Contact us about your privacy choices

A clear support route helps when you want to ask about a record, cookie choice or account detail.

Account privacy request Send your request through account support and name the data subject, such as phone verification or login history. We may ask for account checks before discussing private records.
Wallet record question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account references, tell us the date and account step involved. Avoid sending a wallet PIN or full secret credential.
Security concern If your account access looks unusual on mobile or desktop, contact our support desk promptly. We can review security signals and explain the privacy steps connected to an access check.
DATA PRACTICES

Browse your data security controls

We keep privacy practical by linking each data practice to an account action you recognise.

Account data

We use your account contact details and phone verification status to identify the correct account, answer privacy requests and protect account access. Please keep those details current through the available account path.

Payment references

A DANA, OVO, GoPay or QRIS reference can help us match a cashier event to your account. Bank transfer and virtual account records may serve the same checking purpose.

Cookies and sessions

Cookies and session records help remember sign-in state and detect unusual browser activity. You can manage browser cookie controls, although changing them may affect access to account privacy settings.

Account security

Phone verification and device signals help us distinguish your account session from suspicious access. Never share a password, wallet PIN or verification code when asking about your Privacy Policy rights.

Retention checks

We keep a record while it supports account security, a requested response or a legal requirement. We then assess whether the record still has a clear purpose before continued storage.

Changes and contact

To request access, correction or removal, contact our support route with your account contact and a specific request. We may verify account ownership before making a privacy change.

Check rikatoto Privacy Policy questions

These answers address the searches we hear most often about the rikatoto Privacy Policy. They cover account access, wallet references, cookies, device records and requests for changes, so you can choose the right support path before opening an account.

It covers account and phone verification details, device and browser records, cookie use, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We ask you not to send a wallet PIN or secret credential to support. Our policy concerns the payment reference needed to match an account action, not unrestricted access to your DANA or QRIS wallet.

Phone verification helps us identify the account connected to a request and check unusual access. We use its status for account security and support handling, subject to the purposes described in our Privacy Policy.

Use the account support route and state that you want access to your personal data. Include your account contact and the records you mean; we may verify ownership before responding.

Yes. Send a correction request through support with the inaccurate account detail and the replacement you believe is correct. We may ask for an account check before changing a private record.

Cookies and session records can keep your sign-in state and help detect unusual device activity. Browser controls may remove or block them, but some account privacy settings may then require another sign-in.

Processing and access depend on local law. If you are in Jakarta or another Indonesian location, contact support with your account question so we can direct you to the relevant policy path.