Reference

ratutoto Privacy Policy for Indonesia Accounts

ratutoto Privacy Policy explains how we collect, use and protect details connected with your account, mobile browser and wallet activity.

Account dataWallet recordsCookie choicesAccess requests
ratutoto ratutoto Privacy Policy for Indonesia Accounts
REQUEST ROUTES

Where To Ask About Privacy

A clear contact path helps when your account details, wallet status or policy request needs attention. Use the support route connected to your account and include the phone number or email attached to your profile, the relevant date and the request you want handled. We use those details to locate the correct record without asking you to send a password or full payment credentials.

Team online

Account contact

Open the account support route for a privacy request, then identify the phone number or email on your profile so we can match the request to the right record.

Wallet status

If a DANA, OVO, GoPay or QRIS status appears incorrectly, send the receipt reference and date through support; never include your wallet PIN, password or banking login.

Policy correction

For a correction, access or deletion request, describe the exact detail involved and your preferred reply route. We may ask for account verification before changing private records.

DATA PRACTICES

How We Handle Your Account Details

Our privacy process follows the account journey rather than collecting unrelated details. We use sign-in, device and transaction signals to secure access, check a wallet status and respond to a request.

Account security

Phone verification connects a sign-in attempt with your account before access is completed. We use login timing, device signals and session activity to identify unusual access without requesting your wallet PIN.

Cookies and sessions

Cookies and session tokens help keep your account area available between page loads. You can clear or restrict them in your Android or iPhone browser, though some account functions may then need another sign-in.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records help us match a receipt with an account status. We do not need your wallet password or banking login to perform that check.

Retention period

We retain account, support and transaction records for the time needed to provide the requested service, resolve disputes, protect access or meet a legal requirement, then remove or restrict them when appropriate.

Your requests

You can ask what eligible account details we hold, request a correction or ask about removal by contacting support. We verify the account first so a private record is not changed by another person.

Reply details

Include your account phone number or email, request type and relevant date when contacting us. We reply through the contact route you provide and may explain where local law limits a request.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the account, device and wallet questions you may have before opening access. We keep each response tied to a practical step, from phone verification to a QRIS receipt, so you know what to include when contacting us.

We may collect account contact details, phone verification status, login and device signals, support messages, cookie data and payment status references connected with DANA, OVO, GoPay, QRIS or bank transfer.

Phone verification helps connect a sign-in attempt with the correct account and reduces mistaken or unauthorised access. We may use related session and device signals to protect that account.

No. Our operational records can include a wallet route, receipt reference or transaction status, but we do not need your DANA, OVO or GoPay password, PIN or banking login.

Contact support using your account route and state the detail to correct, the relevant date and your preferred reply route. We may verify your phone number or email before making a change.

You can ask about removal of eligible details through support. We first verify the request, then explain what can be removed and what must remain for security, dispute handling or legal requirements.

Cookies and session tokens can keep policy and account pages working between loads. You can restrict or clear them in your Android or iPhone browser, although another sign-in may then be required.

Yes. Access or eligibility depends on local law. Where local law permits, we can explain eligible records, correction steps and request outcomes through the account contact route.