Reference

istanaimpian1 Privacy Policy for Your Account

istanaimpian1 Privacy Policy explains how we collect, use and protect the details connected to your account, from phone verification to payment status.

Account dataWallet recordsCookie choicesRequest access
istanaimpian1 istanaimpian1 Privacy Policy for Your Account
CONTACT ROUTES

Get Privacy Answers Through Your Account Path

A clear contact route helps you ask about personal data without explaining your whole account history. Start from the support area linked to your account or the contact route shown beside the cashier path, then include the email or phone detail attached to your account. We use that step to locate the right record, limit disclosure and respond to requests about privacy, cookies or payment references.

Team online

Account support

Use the support path after signing in when you need a copy of account data, a correction, or an explanation of a phone verification record. We match the request to your account before discussing details.

Wallet status help

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the receipt reference through the account support route. We use the payment trail to check the record without asking for your wallet password.

Access questions

For a privacy question before account access, use the published contact route and state your country and request clearly. We can explain the relevant handling process where local law permits, without exposing another account's data.

DATA HANDLING

See How We Handle Account Data

We keep our privacy process tied to real account actions rather than collecting details without a reason.

Data we collect

We collect details needed for account creation and phone verification, plus device signals, sign-in events and support messages. Payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account help us reconcile your account activity.

How we use it

We use account and device records to let you sign in, identify unusual access, answer support requests and match payment status. Game activity such as Baccarat or Bingo may appear in account records when needed for account servicing.

Cookies on devices

Cookies may keep your session active and remember practical choices on mobile or desktop. You can clear them through your browser settings, although clearing session cookies may require you to sign in again.

Account security

Phone verification and sign-in checks help us reduce unauthorised account changes. Never send us a wallet PIN or password; our support process relies on account identifiers and transaction references instead.

How long we retain

We retain account, support and payment records only for the period needed for account servicing, dispute checks, security review and legal duties. When a record is no longer needed, we remove or separate it where our process allows.

Requesting a change

You can ask us to access, correct or clarify personal data through the account support route. Include the account email or phone detail, describe the change, and provide a matching reference when the request concerns payment data.

Privacy Policy Answers for Indonesia Accounts

These Privacy Policy answers address the questions we expect before you create or use an account from Indonesia. They explain what happens to account details, how wallet references are checked, and where to send a request. If your situation is not covered, use the account support path and we will direct the question to the right privacy process.

It covers account creation, phone verification, sign-in events, device signals, cookies, support messages and payment references. It also explains how we use and retain those records when you access the account where local law permits.

No. Our Privacy Policy distinguishes payment references from secret wallet credentials. We may retain a DANA or QRIS receipt reference to check status, but you should never send a wallet PIN or password to support.

We use phone verification to connect account access with the detail you submitted and to help identify unauthorised changes. A verification event can remain in account records while it is needed for security and account servicing.

Yes. Send the request through the account support route with your account email or phone detail and describe the data you want checked. We verify the request before sharing or changing personal records.

Cookies can keep a signed-in session active and remember browser choices on mobile or desktop. You can clear them in your browser settings, but doing so may sign you out and remove saved preferences.

We keep payment and virtual account references for the period needed to reconcile status, handle a dispute, support account questions and meet applicable legal duties. Records are removed or separated when that need ends.

Use the support area connected to your account or the published contact route beside the cashier path. Include a clear request and matching account detail; do not include your password, wallet PIN or secret code.