Reference

Privacy Policy for Your maps168 Account

maps168 Privacy Policy explains what we collect when you open an account, verify your phone, browse Live Blackjack Salon or use DANA and QRIS.

Account dataWallet recordsDevice securityCookie choices
maps168 Privacy Policy for Your maps168 Account
REQUEST HELP

Contact Paths for Privacy Requests

A privacy question should not get mixed into a general account issue, so we keep a clear path for data requests. Use the support route available from your maps168 account and include the email or phone detail linked to your account, without sending a password or wallet PIN. We may ask for an account step to confirm that the request concerns you. If access or eligibility is discussed, it depends on local law.

Team online

Account privacy route

Open the account support path and state whether you want access, correction or deletion of eligible data. Include your registered contact detail so we can locate the correct account record without asking for your password.

Payment record question

For a DANA, OVO, GoPay or QRIS record, share the date, amount shown in your receipt and wallet label, while hiding PINs and full security codes. We use those details to find the relevant payment entry.

Device access concern

If your phone browser shows an unfamiliar sign-in or repeated verification prompt, tell us the device type and approximate time. We can direct the account-security request while keeping the privacy discussion separate from game activity.

DATA HANDLING

How We Handle Wallet And Device Data

We handle privacy through the same account steps you already see: phone verification, wallet selection and sign-in from a recognised device.

Account opening

When you create an account, we use the details you submit to establish the account record and communicate about access. Phone verification helps connect the request to you before account features become available.

Payment matching

A wallet label, bank transfer reference or virtual account detail can be used to match a payment event with the correct account. We do not need your wallet PIN to investigate a receipt or status question.

Phone and browser

A phone browser may provide device and session signals used to protect sign-in. If the same account moves from phone to another browser, an additional verification step may appear before access continues.

Cookies and sessions

Cookies can retain a session preference or help us recognise a returning account session. You can manage cookie settings through your browser, although changing them may affect sign-in or page continuity.

Retention period

We keep account, payment and security records only while they support an active purpose such as reconciliation, support, fraud prevention or a legal duty. We then remove, anonymise or reassess records where appropriate.

Changes to your data

You may ask us to correct inaccurate contact or account details, request a copy where applicable, or ask about deletion. We may verify your identity first and explain any record that must remain for a stated purpose.

Privacy Policy Answers For maps168

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening an account. We keep the wording practical: what is collected, why a phone check appears, how payment records are handled, and how to contact us. For access or eligibility, the applicable position depends on local law.

It covers personal data connected with your account, phone verification, sign-in sessions, cookies, payment records and support requests. It also explains retention, security handling and how to ask for access, correction or deletion where those rights apply.

Phone verification helps connect an account request to the person seeking access and can reduce mistaken or suspicious sign-ins. We record the verification result and related security event for account protection, rather than asking for your wallet PIN.

Yes. The policy covers payment references and status information linked to DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. A payment partner may also apply its own privacy terms to data handled directly through its service.

Use the account support path and identify the phone number or email attached to your account. State whether you want access or correction, and describe the field that seems wrong. We may verify the request before sending or changing eligible records.

We retain account, payment and security records while they serve a stated purpose such as support, reconciliation, account protection or a legal duty. When that purpose ends, we assess the record for removal, anonymisation or continued storage.

You can ask us to delete eligible personal data through the account support route. We first confirm the request and then explain what can be removed. Some records may need to remain for payment reconciliation, security or legal duties.

Contact us through the account privacy route and provide the device type and approximate sign-in time, without sharing a password, PIN or security code. We can direct the account-security check and explain which session data relates to the event.