Reference

Privacy Policy For Your idr king Account

Our Privacy Policy shows what data we collect when you open an idr king account, sign in from a phone or desktop, and use DANA, OVO, GoPay or…

Clear data purposesWallet record handlingCookie choicesAccount access requests
Explore Our Lobby Read FAQ
idr king Privacy Policy For Your idr king Account
CONTACT THE TEAM

Get Privacy Policy Help Through Account Support

A direct support path helps you ask about Privacy Policy details without posting account data in a public message. Use the account contact channel when you need a copy of stored details, a correction to your phone record, or clarification about a DANA, OVO, GoPay or QRIS reference. We may ask you to confirm account ownership before discussing private records. Keep your receipt reference ready, but never send your password or one-time verification code.

Team online

Account contact

Send your Privacy Policy question through the signed-in account contact path. We use the account details already on file to locate your request, and we may ask for phone verification before discussing personal records or changing an account detail.

Wallet receipt

For a DANA, OVO, GoPay or QRIS question, include the transaction reference, date and amount shown on your receipt. We use those details to trace the record while avoiding a request for your wallet password, card secret or one-time code.

Access request

Ask for a copy, correction or removal review by stating which account detail you want addressed. We first confirm that you control the account, then explain what can be changed or retained under local requirements and our Privacy Policy.

DATA CONTROL

What You Can Check In Our Privacy Policy

The Privacy Policy is designed to give you a practical view of account data rather than a vague promise.

Account data

We may hold your account name, phone detail, verification result and support messages so we can provide account access and answer a Privacy Policy request. We do not need your password in a support message, and you should not send one.

Cookie controls

Cookies and similar browser storage can keep a session active, remember a selected setting and help us detect repeated sign-in failures. You can manage browser permissions on your phone or desktop, although blocking required storage may affect account access.

Account security

Phone verification helps us check account ownership before access or account changes. We also examine sign-in device and browser signals for unusual patterns. If a prompt looks unexpected, stop and contact support through the account path rather than sharing a code.

Payment records

DANA, OVO, GoPay and QRIS references help us match a wallet action with the correct account. Bank transfer and virtual account records may be handled in the same operational way, with payment identifiers used for reconciliation rather than public display.

Retention timing

We keep personal records while they support account operation, dispute handling, security checks or a legal requirement. When a record no longer serves one of those purposes, we aim to remove it or separate it from direct account identifiers.

Request changes

You can ask what data is linked to your account, request a correction, or ask whether deletion is available where local law permits. Include the affected detail and account contact route; we confirm ownership before releasing or changing private data.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers cover the questions we expect you to ask before opening an account or contacting us about a personal record. They explain collection, cookies, wallet references, deletion and access requests in plain terms. If your case involves a specific receipt or sign-in event, use the account contact path so we can check the relevant record.

It covers data connected with your account, phone verification, sign-in sessions, browser cookies, support messages and payment references. It also explains retention, account security and the steps for asking about access, correction or deletion where local law permits.

Phone verification helps us confirm that the person requesting account access or an account change controls the registered contact. It can also help us investigate an unusual sign-in. We will not ask you to place a password or one-time code in a support message.

Yes. The Privacy Policy covers operational references connected with DANA, OVO, GoPay and QRIS, including receipt or reconciliation details. These references help us match an action to your account and resolve a question without displaying your wallet data publicly.

Use the signed-in account contact path and state that you want an account data request. Mention the record or time period you need. We may confirm your phone or account ownership first, then explain the available response under local law.

You can ask us to correct an inaccurate account detail or ask whether deletion is available where local law permits. Some records may need to remain for security, disputes, payment reconciliation or legal requirements. Support will explain the result for your request.

The policy describes cookies or browser storage used for session continuity, saved settings and sign-in security checks. You can manage permissions in your mobile or desktop browser. Blocking required storage may prevent parts of your account from working correctly.

Contact us through the account contact channel, especially when your question concerns a private record, phone detail or wallet reference. Include a receipt reference when relevant, but do not send your password, wallet secret or one-time verification code.

Related Pages

idr king Indonesia Access guide Live Blackjack Elite About Us Liga 2 Over Under