Reference

sonic66 Privacy Policy For Your Account

VIP Baccarat, Aviator and Mega Fishing give you a clear reason to open an account, while our Privacy Policy explains what happens to your personal data from registration…

Account dataWallet recordsCookie choicesContact routes

Explore Our Lobby Read FAQ

DANA And QRIS In Your Privacy Policy

sonic66 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers the data needed to open and maintain your account, confirm your phone, record wallet actions and answer payment questions. When you select DANA, OVO, GoPay or QRIS, we may retain transaction references, status changes and the account identifier attached to that request;

1
we do not present those payment names as a reason to collect unrelated data. Bank transfer and virtual account records can also appear in your account history. We use these records to match a receipt, investigate a stalled status and protect account access. Access to the
2
service depends on local law, and we apply the policy where local law permits. The current policy remains the reference point if a payment route or account step changes.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP DESK

Support Paths For Privacy Requests

A clear contact path matters when you want a copy, correction or explanation of account data. Start from the support route connected to your sonic66 account and include the phone number or account reference used at registration, rather than sending wallet credentials. Our team can connect a privacy question with a payment receipt, login event or device issue without asking you to publish sensitive details. If you are in Surabaya or elsewhere in Indonesia, the same account-based path applies where local law permits.

Team online

Account contact

Use the support path attached to your account when you need to ask about personal data, phone verification or a stored login record. Include your registered contact and the specific request so we can locate the correct account without confusing it with another sonic66 profile.

Wallet question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, mention the payment route and receipt reference only. We use that narrow detail to check status and explain what was retained, without asking for your wallet PIN, password or full authentication code.

Access concern

If a phone verification step or unfamiliar device event concerns you, contact us through the account help route before sharing further details. We can review the access context, explain the relevant Privacy Policy section and tell you which account step should happen next.

SECURITY PRACTICE

How sonic66 Handles Six Data Areas

The Privacy Policy is practical because each data area connects to an account action you can recognise.

Registration data

When you open an account, we handle the contact details you submit and the account identifier created for you. This lets us connect your login, support request and wallet status without treating unrelated browsing activity as part of your account record.

Phone verification

Phone verification is an account access step, so the related event can show when confirmation was requested or completed. We use that record to help resolve failed access and to separate a genuine account request from an unfamiliar attempt.

Device signals

A phone or desktop session may provide basic device and connection signals for account protection. These signals help us examine an unusual login or repeated access failure; they are handled for that purpose rather than used as a substitute for your identity details.

Cookies

Cookies can keep a session active, remember a selected page setting and help the account path work between login and the lobby. You can manage cookie behaviour through your browser, although changing those settings may affect sign-in continuity.

Retention

We retain account, support and payment records for the period needed for the stated service, security or legal purpose. A request about retention should identify the record, such as a QRIS receipt or login event, so we can assess it accurately.

Policy changes

If this Privacy Policy changes, the updated page becomes the place to check what applies to your account. Before continuing with a new phone verification or wallet step, read the current wording and contact us if any change needs clarification.

Privacy Policy Questions About Your Account

These Privacy Policy answers address the account and payment questions you are most likely to have before opening access. We keep the examples close to real steps: phone verification, device use, DANA and QRIS records, cookie settings and requests sent through support. Where eligibility or access is relevant, it depends on local law.

It covers the personal data connected with your account, phone verification, device access, cookies, support requests and payment records. That includes references linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity when those routes are used.

The Privacy Policy names DANA and QRIS because a wallet or payment request creates useful status and receipt records. We use those records to match an account action, investigate a stalled payment status and answer your support question without requesting your wallet PIN.

Use the support path connected to your account and state whether you want a copy, correction or explanation. Add your registered phone detail and identify the relevant record, such as a verification event or payment receipt, so we can handle the request accurately.

Yes. It explains how basic device and connection signals may be used to protect account access and investigate unusual login behaviour. The same policy applies when you move from a mobile phone to desktop, including a session that checks QRIS or wallet status.

Cookies can support session continuity, remember selected settings and keep the route between login and the lobby working. Your browser controls these choices. If you block or remove cookies, you may need to repeat an account step or sign in again.

We keep records for the operational, security or legal purpose described in the Privacy Policy, rather than for an undefined period. To ask about one record, name its type and reference, such as a GoPay status entry or phone verification event.

Read the current Privacy Policy on this page, then use the account support route if a clause or new data practice is unclear. Include the section and account step you mean. Access remains dependent on local law and applies where local law permits.

sonic66 Privacy Policy For Your Account

Support Paths For Privacy Requests

Account contact

Wallet question

Access concern

How sonic66 Handles Six Data Areas

Registration data

Phone verification

Device signals

Cookies

Retention

Policy changes

Privacy Policy Questions About Your Account

01 What does the sonic66 Privacy Policy cover?

02 Why does Privacy Policy mention DANA and QRIS?

03 How can I request a copy or correction of my data?

04 Does sonic66 Privacy Policy cover mobile devices?

05 How do cookies affect my sonic66 account?

06 How long are payment and account records kept?

07 Where can I ask about a Privacy Policy change?

Related Pages