Reference

ran303 Privacy Policy For Your Account

ran303 puts its Privacy Policy beside the account path, so you can see how we handle phone verification, login records, wallet references and cookie settings before opening an…

PHONE VERIFICATIONDANA AND QRIS RECORDSCOOKIE SETTINGSACCESS REQUESTS
ran303 ran303 Privacy Policy For Your Account
CONTACT PATHS

Get Policy Help Near Your Login

A clear contact route matters when you want to understand a Privacy Policy entry or check an account record.

Account message Use the support message route after login for a Privacy Policy question, data access…
Login assistance If you cannot reach your account, contact support through the available account-help route and…
Payment record check For a DANA, OVO, GoPay, bank transfer or virtual account record, send the transaction…
DATA PRACTICES

How ran303 Handles Your Policy Choices

We keep the Privacy Policy practical: it connects each data category to an account action you can recognise.

Data collection

We collect account details that you submit, such as a phone number used for verification, and technical signals created when you sign in. The Privacy Policy links each category to access, support, security checks or a payment record rather than treating every field the same way.

Cookie controls

Cookie settings can affect how your browser keeps a session or remembers a page preference. Check the browser controls on your phone or desktop, then contact us if you need help understanding a cookie entry connected with the ran303 account pages.

Account security

We may compare login timing, device signals and verification details when an account access pattern needs checking. Never send us a password, wallet PIN or one-time code in a support message; we use account verification instead before discussing private records.

Payment references

A DANA, OVO, GoPay or QRIS reference can show that a payment status belongs to your account without exposing your wallet secret. Bank transfer and virtual account records may follow the same matching process, with the relevant provider handling its own data terms.

Retention choices

We retain records for as long as needed for the stated account, support, security or legal purpose, then assess whether they are still required. Ask us about a specific phone, login or payment record and we will explain the applicable retention position.

Request changes

You can ask us to access, correct or clarify personal data through the support route linked to your account. State the requested change clearly and provide enough account context for verification; fulfilment depends on local law and the rights that apply to your request.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account questions we expect before you open an account or connect a local wallet. They cover the records created during phone verification, browsing on a mobile device, payment matching and support contact. If your situation is more specific, use the account help route with the smallest amount of detail needed to locate your record.

It covers personal details you submit for an account, phone verification data, device and login signals, cookie use, support messages and payment references. It also explains why we use those records, how retention is assessed and how you can ask for access or correction.

No wallet password or secret PIN is needed for our payment matching process. We may receive a transaction reference or status connected with DANA, OVO, GoPay or QRIS, while the wallet provider handles its own account data under its separate terms.

Open the support route from your account and ask for a data access request. Include the phone number linked to the profile and name the record you want, such as login history or a QRIS reference. We verify the request before discussing personal data.

Yes, send a correction request through the account support path and identify the field that needs changing. We may ask you to complete phone verification before editing it, because account changes affect access. Processing depends on local law and the applicable request rights.

Cookies and similar browser records may help maintain a session or remember a page setting when you use a phone. You can inspect or clear them through your mobile browser controls. Clearing them may require another login, while the policy explains their stated purpose.

Retention varies by the reason for keeping a record, including account access, support, security checks or legal needs. A DANA, bank transfer or virtual account reference may therefore follow a different period from a temporary browser signal. Ask us about a named record.

Use the support contact route connected with your account and describe whether you need access, correction, clarification or a retention answer. Do not include a password, wallet PIN or one-time code. If access or eligibility is part of the request, it depends on local law.