Reference

rans88 Privacy Policy For Indonesia Accounts

The rans88 Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
rans88 rans88 Privacy Policy For Indonesia Accounts
CONTACT ROUTES

Where To Ask About Privacy Policy

A clear contact route helps you resolve a data question without repeating your account story.

Account data request Ask us to explain the personal data connected with your account or request a copy where local law permits. Include your registered phone number and write Privacy Policy in the subject so we can route the request correctly.
Wallet record question If a DANA, OVO, GoPay or QRIS status appears beside the wrong account activity, send the transaction reference and date. We use those details to check the record while keeping your wallet PIN and password out of the message.
Security concern Tell us promptly if a login alert, phone verification message or device session looks unfamiliar. We can review the account access trail, help secure the session and explain what data was involved in the Privacy Policy request.
DATA CONTROLS

How rans88 Handles Privacy Details

Privacy work is part of the account path, not a separate promise you have to guess at.

Account information

We use the name, contact detail and phone verification information you provide to create and maintain account access. A clear account step helps us match a data request to the right record, while we avoid requesting details that are not needed for that purpose.

Payment references

For DANA, OVO, GoPay and QRIS, our records focus on the reference, amount status and account match needed to reconcile activity. Bank transfer and virtual account checks follow the same principle: we use transaction data for account servicing and status enquiries.

Cookies and devices

Cookies can remember a session preference, while device and browser signals can help identify an unusual sign-in. On mobile, the path from login to the lobby may create session data; clearing cookies can require you to verify the account again.

Account security

Phone verification before account access gives us an account event to compare with later sign-ins. Keep your password and verification codes private. If your device changes or a session seems unfamiliar, contact us before sharing any wallet or payment credential.

Retention decisions

We retain account, security and transaction records for as long as needed for the stated service, dispute handling and applicable legal duties. When a record is no longer needed, our handling follows the deletion or removal process available under local requirements.

Change requests

You can ask us to correct an inaccurate contact detail, clarify a data use or request removal where local law permits. Send the account identifier, the requested change and enough context to verify ownership; we may need an account step before making an alteration.

Privacy Policy Questions About rans88

These answers address the Privacy Policy questions you may have before opening an account or checking a wallet status. We keep the wording practical so you know what to send, what we use and how access requests connect to your account.

The rans88 Privacy Policy covers account details, phone verification, login events, device and browser signals, cookies, support messages and payment references. For DANA, OVO, GoPay or QRIS, we use the transaction context needed to match status with your account rather than requesting your wallet PIN.

Phone verification helps us confirm an account step before access and compare later sign-ins with the registered contact. It also gives our support team a safer way to locate your record when you ask about a Privacy Policy request, an unfamiliar session or a wallet status.

Yes. The Privacy Policy covers the account and transaction references created when you use QRIS, DANA, OVO or GoPay. We use these details to reconcile a status and respond to a receipt question. Do not include a wallet PIN, password or full payment credential in a message.

Send a request through our account contact route with your registered phone number or email, the phrase Privacy Policy and the records you want clarified. We may ask for an ownership check before responding. Where local law permits, we can explain the data held or provide an available copy.

You can ask us to correct an inaccurate name, phone number, email or account detail. Describe the exact change and include the registered contact so we can locate the record. We may require phone verification before editing information that affects account access or transaction matching.

Cookies can retain session preferences, while browser and device signals help us protect sign-in activity. If you clear cookies on your mobile browser, you may need to sign in and complete phone verification again. The Privacy Policy explains these uses and the choices available through your browser.

Yes. Send the bank transfer or virtual account reference, date and registered account contact. We use those details to locate the relevant record without asking for your banking password. We can then explain the transaction data connected with the account under the Privacy Policy and local requirements.