Reference

Privacy Policy For Your idn68 Account

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

Account dataWallet detailsCookie choicesSecurity checks
idn68 Privacy Policy For Your idn68 Account
HELP WITH PRIVACY

Get Privacy Policy Help From Us

A clear support route matters when a data request and an account issue arrive together. Use the support link connected to your account and describe the exact Privacy Policy question, such as a wallet reference, cookie setting or incorrect profile detail. We may ask for account identifiers before discussing private data, and we will keep the request tied to the person who can access that account.

Team online

Account support link

Open the support path from your signed-in account and select a Privacy Policy request. Include the affected email or phone detail, but never send your password or a full wallet credential.

Payment data query

For DANA, OVO, GoPay or QRIS questions, share the transaction reference and date shown in your account. We use those details to locate the payment record without asking for your wallet PIN.

Correction request

If your account name, phone detail or contact record needs correction, tell us which field is wrong. We may complete an account check before changing information connected to access or verification.

DATA CONTROL DETAILS

What Our Privacy Policy Covers

We keep the Privacy Policy practical by describing how account data moves through sign-in, payment matching, security checks and support.

Account creation

When you open an idn68 account, we collect the details needed to create and protect that account. Phone verification can be required before access, helping us connect a sign-in attempt with the correct account holder.

Device activity

A mobile browser may send device, browser and session signals when you sign in or move between the lobby and account area. We use these signals to detect unusual access and keep the session working.

Payment matching

A DANA, OVO, GoPay or QRIS reference can be stored with payment status so support can trace a deposit or reconciliation issue. We do not request your wallet PIN or banking password.

Cookies

Cookies can keep your session active, remember a selected language or help us identify repeated security prompts. You can manage cookies through your browser settings, although some account functions may then need another sign-in.

Retention

We retain account, payment and support records for as long as needed for account operation, dispute handling, security checks and legal duties. When a record is no longer needed, our handling follows the applicable retention process.

Your request

You can ask us to access, correct or clarify personal data through the account support path. We may verify ownership first, and where local law permits, we will explain any reason a requested change cannot be completed.

Privacy Policy Answers For idn68

These Privacy Policy answers address the searches we hear most often before account access. They explain what we collect, why payment references appear in records, how cookies work on mobile, and how you can ask for a correction. If your question concerns a specific account, use the support path so we can check the relevant record securely.

It covers account details, verification data, device and session signals, cookies, support records and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security handling and routes for access or correction requests.

We need account information to create your sign-in, complete phone verification when required, protect access and connect support requests to the right record. We use the data for these stated purposes rather than treating account creation as permission for unrelated use.

Yes. The policy covers payment references and status connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use those details to match activity and investigate status issues, not to request your wallet PIN.

Cookies can preserve a sign-in session, remember a setting and help identify unusual access. You can remove or restrict them in your browser. If you block necessary cookies, the account may ask you to sign in again or may not retain selected settings.

You can contact us through the signed-in account support path and specify whether you want access, clarification or a correction. We may verify account ownership before responding. Where local law permits, we will explain the result and any applicable restriction.

Retention depends on why the record exists. Account, payment and support records may remain while needed for operation, security, dispute handling or legal duties. Once a record no longer serves an applicable purpose, it follows our removal or de-identification process.

The policy is available for you to read before using account services, but account access and certain data rights depend on local law. Where local law permits, we apply the stated request, correction and retention processes to your account.