Reference

Privacy Policy for logo 66 slot

logo 66 slot keeps your account, wallet records, device details, and policy choices clear from the first phone verification step.

Clear data purposesWallet record contextAccount request pathMobile and desktop access
logo 66 slot Privacy Policy for logo 66 slot
REQUEST SUPPORT

Three Ways To Ask About Privacy

You can raise a Privacy Policy question without explaining your whole account history. We use a clear support path for requests about data access, correction, deletion, cookies, retention, or a payment receipt…

Account request Ask us to locate the personal data connected with your account by referring to the phone number used during verification. We check ownership first, then explain the available response and any reason a record must remain stored.
Wallet record For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account query, send the receipt reference and date rather than your wallet password. We use those details to find the relevant cashier record safely.
Policy contact Use the support contact path for cookie choices, correction requests, retention questions, or concerns about account access. We may confirm your phone verification before sharing or changing any account-linked record.
DATA HANDLING

How We Handle Your Account Data

Privacy controls sit alongside the account steps you already use: phone verification, login, wallet selection, and receipt checking.

Account details

We collect details such as your phone number and account identifiers when you open an account or complete phone verification. These details connect your login to the correct account and help us respond to a data access or correction request.

Device signals

Your browser and device may provide login time, language, screen, and security signals. We use these signals to identify unusual access and protect the account path; they are not a reason to collect unrelated files from your phone.

Cookies

Cookies can keep a session active, remember a selected language, and help us understand whether a policy page loads correctly. You can manage cookies through your browser settings, although changing them may affect login or lobby access.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference can appear in account records when you use that route. We use the reference to match status and receipts, not to request your wallet PIN.

Security controls

We use phone verification before account access and may request an additional ownership check when you ask to change account data. Keep your password and wallet credentials private; support will not ask you to disclose them.

Retention requests

We retain records only for operational, dispute, security, or legal needs that apply to the account. You can ask what remains stored, request correction, or ask whether deletion is available; we explain any retention requirement that prevents removal.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we hear most often before an account is opened or changed. They cover access, wallet records, device behaviour, cookies, retention, and contact steps for logo 66 slot. If your request involves a location or account condition, the response depends on local law and the records linked to your verified phone number.

The Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages, and payment records. It also explains why we use those records, how we protect account access, how long records may remain, and how you can request access or correction.

Yes. Send a request through the account support path and include the phone number used during verification. We first confirm account ownership, then identify the records we can provide. The response and any limits depend on local law and applicable retention duties.

We may store a DANA or QRIS reference, amount status, date, and receipt connection so we can match a cashier event or answer a support request. We do not need your wallet PIN for this process. OVO, GoPay, bank transfer, and virtual account records follow the same account-linked approach.

Device and browser signals help us identify unusual login activity, keep a session working, and understand whether the account path is being used securely. We use practical signals such as login time and browser details, not unrelated files stored on your phone.

Contact us through the policy support route and state which account detail is incorrect. We may repeat the phone verification step before making a change. This protects the account from an unauthorised request, while the available correction process depends on local law.

Retention depends on the purpose of the record, such as account security, a payment receipt, a dispute, or a legal requirement. You can ask which categories remain stored and why. We explain the applicable period or limitation rather than treating every record the same.

You can submit a deletion request through support, and we will assess the records connected with your verified account. Some data may need to remain for security, payment dispute, or legal reasons. Whether deletion is available depends on local law and the specific record.