Reference

Privacy Policy For Your one69 Account

Our Privacy Policy explains what one69 collects when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesContact requests
one69 Privacy Policy For Your one69 Account
HELP WITH YOUR DATA

Contact Paths For Privacy Questions

A clear contact path helps you act on this Privacy Policy without guessing which team to reach.

Account privacy request Ask us to access, correct or explain personal data connected with your account. Include the contact detail used during account creation and describe the specific record, such as a sign-in event or phone verification entry, so we can locate the right account.
Wallet record question If a DANA, OVO, GoPay or QRIS status appears incorrectly, send the payment reference and date through the stated support path. We can check the account-side record without asking you to disclose a wallet password or private security code.
Device access concern Tell us when a phone or browser entry does not look familiar. We can review the account access detail, explain the available security step and help you protect the account before you return to the lobby from that device.
DATA HANDLING DETAILS

What We Do With Your Personal Data

Privacy at one69 is handled through practical account controls rather than vague promises.

Account creation

When you open an account, we use the details you submit to establish your profile and support phone verification before account access. Keeping those details accurate helps us match a privacy request with the correct account rather than another person using a similar contact.

Wallet references

A payment entry may show the selected rail, reference, amount and status needed to reconcile your account activity. DANA, OVO, GoPay, QRIS, bank transfer and virtual account records are handled as account-linked data, not as a reason to request your wallet password.

Cookies and devices

Cookies and device signals can remember a session preference or help us identify an unusual sign-in. On a mobile browser, these signals may connect the login step with the lobby request; clearing cookies can require you to sign in again.

Account security

We use sign-in and device details to protect account access and investigate activity that does not match your normal session. If your phone is shared or replaced, contact us before changing several account details so the security check can follow the right record.

Data retention

We keep personal and payment-related records for the period needed to operate the account, address disputes, maintain security and meet applicable legal duties. A request to remove data may not erase records that must remain available for those specific purposes.

Policy changes

If this Privacy Policy changes, we will present the updated wording through the policy area so you can check what has changed before continuing. For a question about a particular paragraph, contact us with the section subject and your account contact detail.

Privacy Policy Questions For one69

These Privacy Policy answers address the searches we expect from someone deciding whether to open an account with one69. They cover the data connected with account access, wallet records, cookies, device use and requests sent to our support route. If your question concerns eligibility or service access, remember that access depends on local law. For a record-specific answer, use the contact route and share only the details needed to identify your account.

It covers personal details submitted during account creation, phone verification data, sign-in and device activity, cookies, wallet references and messages sent through support. It also explains why we use those records, how long they may remain and how you can request access or correction.

Yes. The Privacy Policy covers account-side records linked with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These may include a reference, amount and status used to reconcile your account. We do not need your wallet password to check that record.

Use the support route displayed on the site and ask for an account data request. Include the contact detail used to create your account, identify the record you want and explain whether you seek access, correction or a description of its use.

Cookies can keep a session preference and help connect a sign-in with the requested page. Device signals can also help identify unusual access. If you clear cookies on your mobile browser, you may need to sign in again before reaching the lobby.

You can ask us to correct inaccurate account details by using the stated privacy contact path. Tell us which field is wrong and provide the account contact detail needed for matching. We may verify the request before changing data linked to your profile.

We retain records for the period needed for account operation, payment reconciliation, security checks, dispute handling and applicable legal duties. The exact period can differ by record type. A removal request may not apply to data that must remain for one of these purposes.

No. The Privacy Policy describes data handling and contact rights; it does not alter eligibility or access requirements. Service access depends on local law. If you need a privacy answer for a specific account or device, contact us through the route shown on the site.