Reference

rokettoto Privacy Policy For Your Account

rokettoto Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity.

Account dataWallet recordsDevice accessPrivacy requests
rokettoto rokettoto Privacy Policy For Your Account
PRIVACY HELP PATH

Get Help With A Privacy Request

A clear contact route helps you ask what data we hold, correct an account detail or question a wallet record.

Account access If you cannot reach the privacy controls after login, tell us which account step stopped you. We use the account contact detail already on file to locate the request and may ask for verification before discussing private records.
Wallet record For a privacy question about DANA, OVO, GoPay or QRIS activity, send the payment reference and approximate transaction date through support. This lets us check the correct wallet record without asking you to repeat unrelated account details.
Correction request If your contact detail or verification record needs correction, state the change clearly and explain why. We review the request against the account record, then tell you whether more proof is needed before an amendment can be made.
DATA CONTROL

What We Do With Your Personal Data

Privacy controls work best when each data use has a clear purpose. We use account details to provide access, device signals to protect sign-in activity and payment references to resolve wallet status…

Account records

We keep the contact and verification details needed to create, secure and maintain your account. A clear account path helps us connect a privacy request to the right record, while access eligibility remains dependent on local law.

Device signals

Sign-in time, browser details and device signals can help us identify unusual access. These signals support account security rather than replacing your account verification, and they may be checked again when you move from mobile to desktop.

Cookies

Cookies and similar storage can keep a session working, remember selected settings and help us understand whether a page loads correctly. You can adjust browser controls, although disabling required storage may interrupt login or the privacy request path.

Payment matching

A DANA, OVO, GoPay or QRIS reference helps us match a wallet event to your account. Bank transfer and virtual account details serve the same checking purpose when a receipt or status question needs investigation.

Retention period

We retain records only while they support account operation, security checks, payment questions, dispute handling or legal duties. When a record no longer serves one of those purposes, our handling process can remove it or separate it from active account access.

Security contact

Tell us promptly if you suspect another person used your account or if a privacy detail looks wrong. Include the affected login step, device path or payment reference, but do not send a password or full wallet credentials.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and wallet questions we expect you to ask before opening access. They explain what we collect, how you can request a change and why a payment reference or device detail may appear in our records. If your question involves eligibility or access from Indonesia, the outcome depends on local law.

The rokettoto Privacy Policy covers account details, verification records, device signals, cookies, support messages and payment references. It explains why we use each category, how long it may remain connected with your account and how you can ask us to access, correct or remove eligible data.

We collect details needed for account access, such as your contact information and verification data, plus records created when you sign in or contact support. If you use DANA, OVO, GoPay or QRIS, a transaction reference may also be stored for payment matching.

Use the support path available after login and describe the exact record you want changed. Include the account contact detail connected with your request. We may ask for verification before making an amendment, especially when the request affects account access or payment records.

Yes. The Privacy Policy covers practical device signals such as browser type, session details and sign-in context when they help protect your account. Returning from mobile to desktop can trigger another verification step if the security context changes.

DANA and QRIS references help us connect a payment event with the correct account and investigate a receipt or wallet status question. We use the reference for that operational purpose; send only the details needed to locate the transaction and never send your password.

We keep personal data while it is needed for account service, security checks, payment reconciliation, dispute handling or legal duties. The retention period can differ by record type. You can ask support which purpose applies to a particular account or payment record.

Yes. Send an access request through the available support path and identify the account contact detail used for login. We may verify that you control the account before responding, then explain the relevant account, device, cookie or wallet records covered by the request.