Reference

Privacy Policy For Your rans303 Account

Our Privacy Policy explains what we collect when you open a rans303 account, use the mobile lobby, or check DANA, OVO, GoPay and QRIS status.

Account dataWallet recordsCookie choicesContact rights
rans303 Privacy Policy For Your rans303 Account
CONTACT THE DESK

Privacy Questions Reach Our Support Path

A clear contact path matters when you want to ask about your Privacy Policy rights or correct an account detail. Start from the support route connected to your rans303 account and include the phone number on the account, the subject of your request and any relevant receipt reference. Do not send a wallet password or full authentication code. We use the account step to check that a request concerns you before discussing stored records.

Team online

Account privacy request

Ask us to explain, correct or remove personal details through the support path attached to your account. Include your account phone number and the exact change you want, so we can locate the right record without asking for your wallet password.

Payment record check

If a DANA, OVO, GoPay or QRIS entry looks wrong, send the transaction reference and date through support. We compare that reference with the account record, then tell you what can be corrected under the current Privacy Policy.

Access question

For a Privacy Policy question about account access from Indonesia, tell us your device type and the account step where the issue appears. We can explain the relevant data use, while eligibility depends on local law.

DATA HANDLING

Six Practical Privacy Controls

We keep our Privacy Policy tied to actions you can recognise: opening an account, confirming a phone number, entering the lobby, checking a wallet status or contacting support.

Account creation

We collect the details needed to create and maintain your account, including your phone number and verification status. The account step lets us distinguish your request from another person’s request before we discuss or change personal data.

Phone verification

A clear phone verification step helps protect account access and limits disclosure to the person connected with the account. Keep your verification code private; our support path does not need you to publish it in a request.

Wallet matching

When you use DANA, OVO, GoPay or QRIS, transaction references may be stored with account and status details. This lets us investigate a receipt or pending state without treating your wallet password as support evidence.

Cookies and device

Cookies can retain necessary session settings, while device and browser signals can help identify unusual sign-in behaviour. Clearing cookies may require you to complete the account access step again when you return to the lobby.

Retention timing

We retain account, security and payment records only for the period needed for the stated service, dispute handling and applicable requirements. A retention question can be sent through support with the record type you want us to check.

Change or deletion

You can ask us to correct inaccurate details or request deletion where the applicable rules allow it. We may first verify account ownership, and some records may need to remain when a legal or payment dispute requires them.

Privacy Policy Questions About rans303

These Privacy Policy answers address the account and payment questions you are most likely to ask before opening an account. We explain the practical path for checking data, changing a phone detail, handling cookies and asking about wallet records. If your situation is not covered, use the support path from your account and mention the exact Privacy Policy point you want clarified.

The rans303 Privacy Policy covers account details, phone verification, device and browser signals, cookies, payment references and support requests. It explains why we use each category, how we protect account access and how you can ask about, correct or delete eligible personal data.

We collect the details needed for account creation and access, such as your phone number and verification status. We can also record device, browser, session and payment-reference details when you use the lobby or check DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Yes, you can ask for access to personal data connected with your account through the account support path. Include your account phone number and describe the data period or category you need. We may verify ownership first and handle the request under applicable rules.

Send a correction request through support with the account phone number, the inaccurate detail and the replacement value. For a wallet record, add its transaction reference and date. We check the request against the account step before changing information that can affect access.

Yes. The Privacy Policy covers payment references and status details linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use them to trace a receipt, investigate a status or handle a dispute, while wallet passwords and authentication codes should stay private.

Cookies help retain necessary session settings when you move from phone verification to the mobile lobby. Device and browser signals can also help identify unusual access. If you clear cookies, you may need to complete the account access step again on your next visit.

You can request deletion through the account support path and identify the records involved. We assess the request under applicable rules; some account, security or payment records may need to remain for a legal duty, dispute or transaction requirement. Access depends on local law.