Reference

Open indogame Privacy Policy Before Account Access

Our indogame Privacy Policy gives you a clear view of the data we use for phone verification, wallet records and account security before you open an account.

Clear data purposesWallet record detailsCookie controlsRequest steps
indogame Open indogame Privacy Policy Before Account Access
REQUEST SUPPORT

Open a Privacy Policy Request

A clear request path helps you ask about a record without repeating your account story. Start from the support route connected to your indogame account and state whether you need access, correction, deletion review or a question about cookies. Include the phone number linked to your account, but never send a password or wallet PIN. We may ask for account details to confirm that a request comes from you before discussing private records.

Team online

Account data request

Use the account support route to ask which personal details we hold, why they are used and which records relate to your phone verification. We will use the account details you provide to locate the correct record before replying.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the receipt reference through support and describe the account step involved. We can check the matching payment record without asking you to share a wallet PIN.

Cookie help

For cookie questions, tell us whether you are using a mobile browser or desktop browser and what changed after clearing site data. This gives our support team a practical route to explain settings without requesting unrelated account details.

DATA PRACTICES

Check Privacy Controls For Your Account

We handle this policy area through defined account steps rather than broad data collection. Phone verification helps us connect a request to the right account, while payment references help us trace DANA…

Account details

We use details such as your phone number and account activity to create access, confirm identity during support and protect the account from unusual login attempts. We do not need your wallet PIN to answer a Privacy Policy request.

Payment references

A DANA, OVO, GoPay, QRIS, virtual account or bank transfer reference can help us reconcile a receipt with your account. The reference is handled as a transaction record, while sensitive wallet credentials remain yours.

Cookies and devices

Cookies can keep a browser session working and help us identify security changes. On mobile, you can clear site data in browser settings; on desktop, the same controls are available through the browser privacy menu.

Account security

Phone verification is part of the account access path, and security checks may record login time, device signals or failed attempts. These records help us investigate an access concern without exposing another account's details.

Retention choices

We keep personal and payment records for the periods needed to operate accounts, investigate security events, answer requests or meet legal duties. When a record no longer has one of those purposes, we handle it under our retention process.

Change requests

You can ask us to correct inaccurate account details or explain a record through support. Include the phone number linked to your account and the specific field or event, so we can verify the request and avoid changing the wrong record.

Ask indogame Privacy Policy Questions

These Privacy Policy answers focus on the account actions you are most likely to take before opening access or while checking a wallet record. We keep the wording practical: what we collect, how cookies work on a phone, how payment references are used, and how you can contact us. If your request involves eligibility, remember that access depends on local law.

The indogame Privacy Policy covers account details, phone verification, browser cookies, device security records, support messages and payment references. It explains why we use each category, how long records may be retained and how you can request access or correction.

The policy can apply to references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use these references to match receipts and investigate account questions; you should not send us a wallet PIN or full secret credential.

We use the phone number linked to your account for phone verification, account identification and support checks. It helps us locate your records when you request a Privacy Policy change, but it does not replace the need to protect your own login details.

Yes. Your mobile browser provides controls to block, clear or manage cookies and stored site data. Clearing them may end a browser session or remove saved preferences, so support may ask which setting changed when you report a Privacy Policy or login issue.

Use the account support route and ask for access to your personal records. State the phone number linked to the account and the category you want, such as verification, cookies or QRIS receipts. We may verify your identity before releasing private details.

You can request a correction when an account detail or payment reference appears inaccurate. Describe the exact field or event and provide the linked phone number through support. We check the request first, then update eligible records under the Privacy Policy process.

The Privacy Policy explains data handling, while account eligibility depends on local law. Where local law permits, we may still need phone verification and security checks before account access. Contact support if you need the policy applied to a specific account situation.