Reference

Privacy Policy for Your Account

The z6 memory slot Privacy Policy explains what we collect when you open an account, sign in from a mobile device, browse No Commission Baccarat or Bogor Lucky…

Account dataWallet recordsCookie choicesRequest access
z6 memory slot Privacy Policy for Your Account
PRIVACY HELP DESK

Three Ways To Ask About Data

A clear contact route helps when your Privacy Policy question concerns an account record, a wallet reference or a cookie choice. Start from the account support path and include the phone number or email connected to your account, but leave out passwords, wallet PINs and one-time codes. We use the details in your request to locate the relevant record and may ask for an account step that confirms you are requesting data about yourself. Requests linked to DANA, QRIS or bank transfer can include the receipt reference so we can separate payment status from personal data.

Team online

Account access

If you cannot reach the account area, use the account help route and state that your request concerns the Privacy Policy. We can ask for your registered contact detail and a sign-in date, while keeping passwords, wallet PINs and one-time codes out of the message.

Wallet records

For a DANA, OVO, GoPay or QRIS record, send the transaction reference rather than a wallet secret. We use that reference to locate the matching account event, explain what is stored and separate a receipt question from a request to change personal data.

Policy requests

To ask for access, correction or deletion where local law permits, identify the account contact detail and describe the record involved. We may verify the request before taking action, so another person cannot obtain your account history through a simple message.

DATA HANDLING

Six Privacy Controls We Explain

We keep the Privacy Policy practical by linking each principle to an account action you can recognise.

Collected details

We may store your account contact detail, phone verification result, sign-in time, device signals, support messages and wallet references. These fields help connect an account request with the correct record without treating your DANA, OVO, GoPay or QRIS PIN as data we need to receive.

Cookie settings

Cookies can support sign-in continuity, page preferences and security checks on a mobile browser or desktop. Your browser controls can remove or restrict them, although changing those settings may affect the account path used to reach the lobby and privacy request tools.

Account security

Phone verification is used before account access, while sign-in and device signals help us detect activity that does not match your normal path. Never place a password, wallet PIN or one-time code in a Privacy Policy request or support conversation.

Record retention

We keep account, support and transaction references for as long as they serve the stated handling purpose or a legal requirement. When a record is no longer needed, our process removes it or changes it so it no longer directly identifies your account.

Correction requests

If your contact detail or another account field is wrong, tell us which record needs correction and provide the account detail used for verification. We compare the request with the account path before changing data, including details linked to a QRIS or bank transfer receipt.

Deletion questions

You can ask whether deletion is available for a particular record where local law permits. Some account or transaction references may need to remain for a legal or security reason; we will explain that limit and identify the data affected by the request.

Privacy Policy Answers Before Access

These Privacy Policy answers address the searches we hear before an account is opened or a wallet is connected. They explain the data linked to phone verification, mobile browsing, cookie settings and payment references without asking you to disclose private wallet credentials. If your question concerns a particular account record, use the support path with the registered contact detail and the narrowest useful description.

It covers account details, phone verification, sign-in and device signals, cookie activity, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains retention, security handling and how to request access or correction.

No. We do not need your DANA, OVO, GoPay or QRIS wallet PIN for a privacy request or a receipt check. Send the relevant transaction reference instead, and never include passwords, one-time codes or other secret credentials in a support message.

Use the account support route and state that you want a Privacy Policy data request. Include the registered phone number or email, describe the record you want and complete any identity check we ask for. Where local law permits, we can explain the available access process.

Yes, you can ask us to correct an inaccurate account field where local law permits. Identify the detail, provide the registered contact information and explain what needs changing. We verify the request before editing the record, including details connected with payment receipts.

Cookies may support sign-in continuity, page preferences and security checks when you browse on a mobile device. Your browser lets you remove or restrict them. If you block required cookies, the account path may not keep its session or display privacy request tools correctly.

We retain records while they are needed for the purpose described in the Privacy Policy or while a legal or security requirement applies. This can include account, support and transaction references. When retention ends, we remove or anonymise the record through our handling process.

Yes. Account access, eligibility and some Privacy Policy requests depend on local law. Where local law permits, you can ask about your stored data, correction or deletion. We apply the current policy wording to the account and records connected with your request.