Reference

66j Privacy Policy For Your Account

Our 66j Privacy Policy explains what we collect when you create an account, sign in from a mobile browser, browse Dragon Tiger or use DANA, OVO, GoPay and…

Account dataWallet recordsCookie choicesMobile access

Explore Our Lobby Read FAQ

How DANA And QRIS Data Is Used

66j Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy sets out how we handle details linked to your account, including your phone number, verification status, sign-in events, device signals and payment references. When you use DANA, OVO, GoPay or QRIS, we receive the transaction status and reference needed to match a wallet

1
action to your account; we do not need your wallet password for that matching step. Bank transfer and virtual account references may also be retained when they relate to an account action. We use records to process requests, protect access, resolve payment questions and meet applicable
2
legal duties. If you ask us to change or remove data, we first confirm the request belongs to you. Access or eligibility depends on local law, and this policy applies to the services we make available where local law permits. The current policy is available from
3
the privacy link on our site.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

PRIVACY SUPPORT ROUTE

Get Privacy Help Through Your Account

A clear contact route helps you ask about a record without sending sensitive details into an open channel.

Account privacy chat Use the support chat available after sign-in to ask what account data we hold, why it is used, or how to request a correction. Share only the details needed to locate your account.

Wallet record check For DANA, OVO, GoPay or QRIS questions, provide the relevant transaction reference rather than a wallet password. We use that reference to trace status without asking for secret wallet credentials.

Access request path If you cannot sign in, use the account recovery route shown on the login screen and explain that your request concerns Privacy Policy rights. We may ask for account details before replying.

ACCOUNT DATA PRACTICE

Your Data Path From Login To Retention

We keep this Privacy Policy practical: your account records support sign-in, verification, wallet matching and support replies, while cookies and device signals help us remember settings and identify unusual access.

Sign-in details

We record the account step needed to authenticate you, such as your phone number and verification state. This helps us return you to the correct account when you move between mobile browser sessions.

Device signals

A mobile browser may send device and sign-in signals that help us spot repeated or unusual access. These signals support account protection and are handled as part of the Privacy Policy.

Cookie choices

Cookies can remember session settings and help pages work as you move from login to the lobby. Your browser controls may let you remove or restrict them, though some account steps may then need repeating.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account actions can create reference records. We use those references to match status, answer receipt questions and separate one account action from another.

Retention periods

We retain records only for the account, support, security or legal purpose connected to them. When a record is no longer needed for those purposes, our handling follows the applicable retention process.

Change requests

You can ask us to access, correct or remove eligible personal data through support chat. We verify the request first, then explain any limit that depends on local law or a required record.

Privacy Policy Answers For 66j Accounts

These Privacy Policy answers cover the account actions Indonesian customers ask about most: sign-in records, cookies, wallet references, device access and requests for changes. Read the relevant answer before opening your account, and contact us through the signed-in support route when a case needs account-specific checking.

It covers account details, phone verification, sign-in and device signals, cookies, payment references, support messages, retention and requests to access or change eligible data. Access depends on local law.

No. When you use DANA or QRIS, we handle the transaction status and reference needed to match the action to your account. Do not send wallet passwords through support chat.

Phone verification helps connect an account request to the correct person and supports account recovery. We may ask for matching details before discussing records, payment references or Privacy Policy requests.

Sign in, open the support chat shown in your account and ask for a data access request. Include your account phone number, then complete the identity check we provide.

Yes, you can request a correction or removal through account support. We assess the request against the record involved, active account needs and duties that apply where local law permits.

Cookies can retain session settings and support movement from login to the lobby. Your browser can restrict or clear them, but you may need to repeat verification or sign-in steps.

Use the support chat available from your signed-in account and label the request as a Privacy Policy question. If you cannot sign in, begin with the recovery path on the login screen.

66j Privacy Policy For Your Account

Get Privacy Help Through Your Account

Your Data Path From Login To Retention

Sign-in details

Device signals

Cookie choices

Payment references

Retention periods

Change requests

Privacy Policy Answers For 66j Accounts

01 What does the 66j Privacy Policy cover?

02 Does the Privacy Policy store my DANA or QRIS password?

03 Why does 66j need phone verification?

04 How can I request a copy of my account data?

05 Can I ask 66j to correct or remove my data?

06 How are cookies handled on a mobile browser?

07 How do I contact 66j about this Privacy Policy?

Related Pages