Reference

Open Privacy Policy Before Account Access

inter 66 slot Privacy Policy explains what we collect when you create an account, verify your phone, use DANA or QRIS, and move through the casino lobby.

Account clarityCookie choicesIndonesia access
inter 66 slot Open Privacy Policy Before Account Access
PRIVACY CONTACT

Reach Us About Your Privacy Policy

A direct privacy question should not get lost beside a cashier message. We separate account-access questions from requests about the Privacy Policy, then use the account details you provide to locate the relevant record. If a DANA receipt, QRIS reference or phone-verification entry is part of your question, include only the reference needed for us to trace it. Where local law permits, we can explain the request path, identity checks and any reason a record must remain available.

Team online

Account support

Use the support channel shown after account access when your Privacy Policy question concerns your phone verification, login record or device history. We will ask for enough account detail to locate the record, not for your password or wallet PIN.

Payment privacy

For a DANA, OVO, GoPay or QRIS privacy question, share the payment reference and approximate date through the account support path. We use those details to check the transaction record while keeping wallet credentials outside our support request.

Policy request

Ask support to route a correction, access or deletion request under the Privacy Policy. Where local law permits, we explain the identity check, expected next step and any retention reason before changing or removing an eligible record.

DATA PRACTICE

Explore The Privacy Policy Controls

Your privacy choices work best when they are tied to a clear account step. We limit access to account records by support need, use security checks around phone verification and distinguish device…

Data we receive

Creating an account can provide your phone number, verification result and login activity. Payment actions can add a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference. We use these details to operate the requested account path and check account security.

Cookie handling

Cookies and similar device signals may remember access settings, help identify an unusual login and keep the selected page available. You can manage browser controls on your device, although changing them may affect account access or require another verification step.

Account protection

Phone verification helps us connect an account request with the correct access path. We do not ask you to disclose a password, wallet PIN or one-time code in support messages. Contact us promptly if a login record or device entry does not look familiar.

Retention approach

We retain account, security and transaction references for the period needed for the purpose described in the Privacy Policy. A deletion request does not automatically remove records that must remain for security, dispute handling or a legal requirement.

Correction requests

If your account details are inaccurate, send support the field that needs correction and the account contact used for verification. Where local law permits, we may confirm your identity before updating the record and tell you when the change is complete.

Access questions

You can ask what personal data is connected with your account and how it is used under this Privacy Policy. Include your account contact and a focused request; we will explain the available response path and any limits that depend on local law.

Browse Privacy Policy Answers First

Searchable answers make the Privacy Policy easier to use when you are deciding whether to open an account or checking an existing record. Each response below stays on data handling, privacy choices and account access. If your situation includes a payment reference or a device change, use the support route described above and avoid sending secret wallet or login credentials.

The inter 66 slot Privacy Policy covers account creation, phone verification, login and device records, cookies, payment references, retention and privacy requests. It explains how we use these details for account access, security and requested transactions involving DANA, OVO, GoPay, QRIS or bank rails.

We may collect the phone number and verification result used to create your account, along with login activity and device signals connected with access. If you request a payment action, the related transaction reference may also be recorded so we can match status without requesting your wallet PIN.

Yes. The Privacy Policy covers transaction references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These references help us check payment status or resolve an account query. They are handled separately from secret wallet credentials, which you should never send to support.

Send a focused data-access request through the support channel available from your account, using the phone contact connected with verification. We may confirm your identity before responding. Where local law permits, we explain which records can be supplied and why some security or transaction records may remain limited.

You can ask us to correct inaccurate account information by naming the field and providing the verified account contact. We may request an account check before making the change. Our response explains the next step and whether any transaction or security record must stay unchanged for a stated reason.

We keep account, security and transaction references only for the period needed for the purposes described in the Privacy Policy, including access protection and dispute handling. A request to remove data is assessed against those purposes and any retention requirement that depends on local law.

Contact account support through the available in-account channel and describe the unfamiliar login or device entry without sending your password or one-time code. We can check the account security record, explain the verification step and help you follow the access path where local law permits.