Reference

ind168 Privacy Policy: Your Data Path

The ind168 Privacy Policy explains how we handle your account details, device signals and wallet records while you use our Indonesia service.

Account clarityWallet recordsDevice choicesSupport access

Explore Our Lobby Read FAQ

How Wallet And Account Data Moves

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

Our Privacy Policy starts with the details needed to create, secure and maintain your account. We may handle your name, phone number, verification result, login events, device details and payment references when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. Payment providers

1
and Indonesian banks such as BCA, BRI, Mandiri and BNI may return a transaction status or reference so we can match your request to the right account. We use those records to check access, resolve wallet status and respond to support questions. We do not ask
2
for wallet credentials through an unsolicited message. Access or eligibility depends on local law, and our policy can be read before you submit account details.

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

ASK ABOUT DATA

Where To Send Privacy Questions

A clear contact route helps when you want to understand a record rather than guess what happened. We ask you to use the support route connected to your ind168 account and include the phone number or account detail needed to locate your request. For a wallet question, add the DANA, OVO, GoPay or QRIS reference shown in your receipt. We then focus on the Privacy Policy issue, confirm what we can discuss, and avoid asking you to send a wallet password or full security code.

Team online

Account privacy request

Use the account support path to ask what personal details are connected with your login. Include your registered phone number and the specific Privacy Policy question, so we can confirm the account before discussing its records.

Wallet record query

For a DANA, OVO, GoPay or QRIS record, attach the visible payment reference instead of private wallet credentials. We use that reference to check the matching status and explain which data was received from the payment rail.

Data change request

Tell us which account detail you want corrected, removed or clarified through the support route. We may ask for an account check first, then record the request and explain any data that must remain for payment or security purposes.

CONTROLLED DATA USE

What Our Privacy Process Covers

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

Account details

We use the phone number and account details you provide to identify your account, complete access checks and respond to requests about the Privacy Policy. Keep your registered phone available because we may need to confirm ownership before releasing account-specific details.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference lets us connect a payment status with the right account. We do not need your wallet password for that check, and a receipt reference is enough for most status questions.

Cookies and sessions

Cookies may keep your login session, remember a selected language setting or help us see whether a policy page loads correctly. On your phone or desktop browser, you can manage browser storage settings, though clearing it may require another account login.

Device security

We may record device type, browser details, sign-in time and related security signals when you access the account. These details help us examine a login that does not match your usual path without asking you to share a password or one-time security code.

Retention choices

We keep personal details only for the period needed for account operation, payment matching, security checks or a legal record. If you ask about deletion or retention, we explain what can be removed and what must remain for those specific purposes.

Your contact route

Questions about access, correction, deletion or a copy of your data should go through the support route attached to your account. State the request plainly, add the relevant account phone number, and avoid sending wallet passwords or complete security credentials.

Privacy Policy Questions For ind168

These Privacy Policy answers address the searches we hear most often before an account is opened. We keep the wording tied to real account steps, Indonesian wallet references and device behaviour. If your question concerns a specific record, use the support path with your registered phone number and the payment reference, when relevant. Account access depends on local law, and a support response may require an ownership check before we discuss personal data.

The ind168 Privacy Policy covers account details, phone verification, login and device signals, cookies, payment references, support requests, retention and requests to correct or remove data. It also explains why DANA, OVO, GoPay, QRIS and bank transfer statuses may appear in account records.

We may receive the account details and phone number you submit, plus verification results, login events, browser or device details and payment references. We use these details for account access, security checks, wallet matching and support, rather than requesting your private wallet password.

A wallet or QRIS reference helps us match a payment status with your account and answer a receipt question. We do not need your wallet credentials to perform that match. If a reference looks wrong, send the visible receipt number through the account support path.

Yes, you can ask us to correct, clarify or remove eligible account data through the support route connected to your account. We first confirm ownership, then explain the result. Some payment, security or legal records may need to remain for a defined purpose.

Our Privacy Policy allows cookies or browser storage to maintain a session and remember a page setting on your phone. You can clear or manage them in your browser controls. After clearing storage, you may need to complete the account login path again.

Retention depends on why the record exists. We keep information for account operation, payment matching, security checks, support handling or a required legal record, then remove or separate it when that purpose ends. Ask support about a specific category rather than guessing from a receipt date.

Use the support contact route shown with your account and describe the request in plain English. Include your registered phone number and, for a wallet issue, the DANA, OVO, GoPay or QRIS reference. Never send a password, wallet PIN or complete security code.

ind168 Privacy Policy: Your Data Path

Where To Send Privacy Questions

Account privacy request

Wallet record query

Data change request

What Our Privacy Process Covers

Account details

Payment references

Cookies and sessions

Device security

Retention choices

Your contact route

Privacy Policy Questions For ind168

01 What does the ind168 Privacy Policy cover?

02 What personal data does ind168 collect when I open an account?

03 Why are DANA, OVO, GoPay or QRIS details connected to my account?

04 Can I request a correction or removal of my ind168 data?

05 How does the Privacy Policy handle cookies on mobile?

06 How long does ind168 keep account and payment records?

07 Where can I ask about a Privacy Policy request?

Related Pages