Reference

com66 Privacy Policy For Your Account

The com66 Privacy Policy explains what we collect when you open an account, sign in from a phone, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice accessPrivacy requests
Explore Our Lobby Read FAQ
com66 com66 Privacy Policy For Your Account
HELP ROUTES

Contact Routes For Privacy Questions

A privacy question should reach a clear account path, not disappear inside a payment issue. From your signed-in account, use the support route and state that your request concerns the Privacy Policy; include the email or phone linked to your account and the subject you want checked. We can then match the request to account records without asking you to send wallet passwords or private security codes.

Team online

Account request

Use the support route connected to your signed-in account when you want a copy of personal data, a correction or clarification about how com66 handles your details. Include your linked phone or email so we can identify the correct account before replying.

Wallet record

For a DANA, OVO, GoPay or QRIS record, send the payment reference, date and status shown in your account. We use those details to locate the relevant entry without requesting your wallet password, PIN or one-time security code.

Access concern

If a privacy request follows an unusual login or a blocked account step, tell us which device path was used and when it happened. We may ask for account verification before disclosing or changing personal data, protecting your account during the request.

SIX DATA CONTROLS

Six Controls Behind Your Account Data

We handle Privacy Policy requests through the same account checks used to protect sign-in and payment records.

Account collection

When you open an account, we collect the contact and verification details needed to create that account and respond to you. Sign-in events may include device type, browser details and approximate access signals, helping us distinguish your normal phone path from an unusual attempt.

Cookie choices

Cookies can keep a signed-in session working and help us understand whether a page loads correctly on mobile or desktop. Your browser settings can restrict cookies, though some account and Privacy Policy request steps may then require another sign-in.

Account security

We use account verification before changing sensitive details or disclosing personal data. Never send us a DANA PIN, OVO password, GoPay code or QRIS security credential; our support route does not need those secrets to locate a payment record.

Payment records

A wallet or bank payment can leave a reference, amount, route and status in account records. We use that information to reconcile the transaction and answer your question, while keeping the payment context separate from credentials held by DANA, OVO, GoPay or your bank.

Retention period

We retain account, security and payment records only for as long as needed for the stated purpose, account administration, dispute handling or a lawful requirement. When a record no longer has a valid need, our process is to delete or securely de-identify it.

Changes and contact

To request access, correction or deletion, use the account support route and identify the data subject clearly. We may verify ownership before acting, then explain what can be changed under the Privacy Policy and where local law permits.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the searches we hear most often from Indonesian account holders. They explain the practical route for checking data, handling wallet records and asking for a change. If your question is not listed, use the support path above and include the account detail needed to locate your request.

The com66 Privacy Policy covers account details, verification records, sign-in and device signals, cookies, payment references and support messages. It also explains why we use each category, when limited sharing may occur, how long records are kept and how you can request access or correction.

No. Our Privacy Policy does not require your DANA PIN, OVO password, GoPay code or QRIS security credential. We may retain a payment reference, amount, route and status so we can reconcile the account entry, while the wallet provider handles its own credentials.

Use the support route inside your signed-in account and state that you want a personal data request under the Privacy Policy. Provide the phone or email linked to the account. We may verify ownership first, then explain the available records and next step.

Yes. Send a correction request through the account support path, identify the field that is wrong and provide the accurate replacement. We may ask for an account check before changing contact or verification details, and the result depends on local law and record requirements.

Device type, browser details and sign-in timing help us investigate unusual access and keep an account session working. Under the Privacy Policy, these signals are used for account security and service operation, not as a request for your wallet password or private code.

We keep payment references and related account records for the period needed to reconcile transactions, answer disputes, protect the account or meet a lawful requirement. After that need ends, our process is to delete or securely de-identify the applicable record.

You can ask for deletion through the signed-in account support route. We will verify the request and explain which data can be removed, retained or de-identified. Some account, security or payment records may need to remain for a lawful requirement or unresolved dispute.

Related Pages

com66 Indonesia About Us toronusa indobola88 Account information