Reference

Open istanastar Privacy Policy With Clarity

istanastar Privacy Policy explains what we collect when you open an account, verify your phone, enter the casino lobby or use DANA, OVO, GoPay and QRIS.

Account collectionWallet recordsCookie choicesAccess requests
istanastar Open istanastar Privacy Policy With Clarity
CONTACT PATHS

Check Privacy Help From Your Account

A privacy question should not leave you searching through unrelated pages. We keep the contact route close to your account and cashier status area, so you can identify the account concerned and attach the relevant receipt or sign-in detail. Tell us whether your request concerns access, correction, deletion, cookies or a wallet reference. We will use the details you provide to locate the right record, ask for reasonable account verification and explain the next step in plain English.

Team online

Account support route

Open the support path inside your account when you need a Privacy Policy answer. Include your registered phone detail and the subject of your request, but do not send a password, one-time code or wallet PIN. We use the account context to direct the question correctly.

Cashier status check

For a privacy question about DANA, OVO, GoPay or QRIS, keep the payment reference and approximate time ready. The cashier status path helps us separate a wallet record from an account record, while you keep sensitive wallet credentials private throughout the request.

Receipt clarification

If a bank transfer or virtual account receipt appears in a data request, send only the reference needed to identify it. We can explain how that record is used, verify the account step involved and tell you whether a correction request can be made.

DATA HANDLING

Browse How istanastar Handles Your Data

Privacy controls work best when they match real account actions. We separate sign-in protection, wallet references, device signals and cookie choices so a question about one area does not expose unrelated details.

Account data

When you open an account, we use the details you submit to create access and connect your phone verification step. We do not need your password in a privacy request. If a detail is inaccurate, contact us with enough account context for us to locate it safely.

Payment references

A DANA, OVO, GoPay or QRIS reference can show that a wallet action belongs to a particular account. Bank transfer and virtual account references serve a similar matching purpose. We use these records to trace status questions, not to request your wallet PIN.

Cookies and devices

Cookies can remember a session choice, while device and browser signals can help identify unusual sign-in behaviour. On a phone, clearing site data may remove remembered choices and require another account step. You can ask us which cookie category relates to your question.

Account security

Phone verification helps us distinguish an account request from an unauthorised attempt. We may ask for account checks before discussing personal data or changing a record. Never place a password, verification code or wallet PIN in a support message.

Retention approach

We keep account, payment and security records for the period needed to operate the account, investigate a dispute or meet a legal handling requirement. When a record is no longer needed for those purposes, our process addresses its removal or continued restricted storage.

Change requests

You can contact us to ask about access, correction, deletion or a cookie choice. Describe the request clearly and identify the account step involved. We may verify your identity first, then explain what can be changed and any reason a record must remain.

Browse Privacy Policy Answers Before Joining

These Privacy Policy answers focus on the questions we expect you to ask before opening an account. They cover the data created by phone verification, sign-in, device use and local payment references. If your situation is different, use the account support route and describe the exact record or action involved. We will ask only for the account context needed to respond and will keep sensitive credentials out of the conversation.

It covers data connected with your account, phone verification, sign-in activity, device and cookie choices, game-page access and payment references. That includes DANA, OVO, GoPay, QRIS, bank transfer and virtual account records when they are linked to an account action.

Phone verification helps us create the correct account and check that a privacy request comes from the account owner. If you ask about access or correction, we may use that step to confirm identity. We will not ask you to disclose your password or wallet PIN.

We use a DANA or QRIS reference to connect a payment status or receipt question with the correct account action. The same approach can apply to OVO, GoPay, bank transfer and virtual account records. Wallet credentials remain with you and should not be sent to support.

Yes, you can request a correction through the account support route. State which detail is wrong and identify the account step where it appears. We may complete an account check before making a change, then explain the result and any record that cannot be altered.

Use the contact path shown inside your account and describe the data you want to access, such as phone verification, cookie choice or a payment reference. Include only necessary identifying details. We may verify the request first and then explain the available records and response process.

You can send a deletion request through account support, specifying the records involved. We assess whether the data is still needed for account security, a payment status question or a legal handling requirement. Where local law permits, we explain what can be removed and what must remain.

Yes, the policy applies when you use the mobile browser to sign in, verify your phone, choose cookies or reach the lobby. Clearing browser data can remove saved choices and prompt another account step. Access and eligibility depend on local law in your location.