Reference

one69 Privacy Policy Explained Clearly

Our Privacy Policy explains what data we collect when you open an account, enter the lobby, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
one69 one69 Privacy Policy Explained Clearly
CONTACT ROUTES

Privacy Policy Help Through Support

A clear contact route matters when you want to ask about your personal data rather than a wallet balance.

Account data request Ask us what personal details are connected with your one69 account, why we hold…
Wallet record question If a DANA, OVO, GoPay or QRIS entry looks unfamiliar, contact support with its…
Policy contact path For correction, deletion or cookie questions, state the exact action you want and the…
DATA PRACTICES

How one69 Handles Privacy Requests

We keep the Privacy Policy practical by linking each data use to an account or support action you can recognise.

Collection at account creation

When you open an account, we collect the contact and verification details needed to create an access path.

Payment reference handling

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records may include a reference, status and timing needed for reconciliation.

Cookies on each device

Cookies can remember sign-in continuity, language display and selected page settings. You can manage them through your browser controls.

Account security checks

We may compare a sign-in request with account and device signals before discussing personal data.

Retention and deletion

We retain records while they support account operation, payment reconciliation, dispute handling or a legal duty.

Changing your details

If your phone number or account detail is inaccurate, contact us with the current record and requested change.

Privacy Policy Questions About one69

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening access. They cover the records created during phone verification, payment reconciliation, cookie choices, support contact and requests to see, correct or remove personal data. If your situation is not listed, contact us with the account phone number and the relevant receipt or device detail.

It explains how we collect account details, phone verification results, sign-in signals and support messages. We use them to provide access, investigate account questions and meet applicable duties. We do not ask you to send passwords or banking PINs when you contact us.

Your phone number connects account creation and verification with the correct access path. It also helps us confirm ownership when you ask about a wallet record or request a correction. We use it for those operational purposes and handle access where local law permits.

Yes. The policy covers payment references, status records and receipt details created when you use DANA, OVO, GoPay or QRIS. We may also handle bank transfer and virtual account references to reconcile a transaction without requesting your wallet password or banking PIN.

Contact our support channel and state that you want a copy of the personal data connected with your account. Include your account phone number and a clear request. We verify ownership first, then explain the available records and any legal reason for limits.

You can ask us to correct inaccurate account details or remove eligible records through support. Tell us which record is wrong and what should replace it. Some transaction or access records may need to remain for reconciliation, disputes or legal duties.

Cookies can preserve sign-in continuity, browser settings and page preferences on your phone or desktop. You can change cookie controls in your browser. Restricting cookies may require another account sign-in or affect some page behaviour, but it does not automatically delete stored records.

Where access or eligibility is discussed, it depends on local law. Our Privacy Policy is available for you to read before account access, but legal rights, retention duties and available services can differ by location. Contact support if you need a location-specific explanation.