Reference

Privacy Policy For Your zaraabet Account

zaraabet Privacy Policy shows how we collect, use and protect the account details that let you reach the lobby from an Indonesian phone.

Account clarityWallet contextDevice controlIndonesia access
zaraabet Privacy Policy For Your zaraabet Account
CLEAR HELP ROUTES

Get Privacy Help Near Wallet Status

A clear contact path helps you ask what we hold, why we use it or how to correct an account record. Start from the account help route when your phone verification, wallet status or receipt needs attention, and include only the details needed to locate your request. We use that context to keep a privacy enquiry separate from unrelated lobby activity.

Team online

Account request

Use your account help route to ask for a copy, correction or explanation of personal details. Include your verified phone reference where available, but do not send a password, wallet PIN or full payment credential in a support message.

Wallet query

If a DANA, OVO, GoPay or QRIS reference looks wrong, share the transaction date, amount reference and wallet name rather than secret credentials. We use those fields to trace the record and explain its privacy purpose.

Device access

When a login session on your phone or desktop looks unfamiliar, tell us the device path and approximate time. We can review the session record, help secure account access and explain which technical details were retained.

HANDLING DETAILS

Your Device And Account Records

We handle this Privacy Policy through practical controls rather than broad promises. Phone verification ties an account request to the right contact route, device signals help us identify unusual sessions, and wallet…

Account identity

We use your account contact and phone verification record to identify the person making a privacy request. This helps us avoid releasing account details to the wrong person and keeps a correction tied to the correct zaraabet account.

Session signals

Device type, browser details and login times can help us investigate an unfamiliar session. These signals support account security and are reviewed for that purpose, not presented as a public profile or attached to game activity unnecessarily.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records may contain references needed to match a receipt. We use the reference trail for reconciliation and support, while secret wallet credentials remain outside our request process.

Cookies

Cookies can preserve a signed-in path, remember a language setting or support session continuity on mobile and desktop. Your browser controls these files, and changing cookie settings may affect account access without changing the records held for a completed request.

Retention

We keep account, security and transaction records only while they serve an operational, security or legal purpose. When a record no longer needs retention, our process removes it or restricts its use according to the applicable policy requirement.

Changes request

You can ask us to correct inaccurate details, explain a processing purpose or clarify a retention question through account help. We may verify your account first, then respond with the action available under local requirements and the policy record.

Privacy Policy Questions About zaraabet

These Privacy Policy answers cover the account steps you are most likely to check before using zaraabet in Indonesia. They explain what we collect during phone verification, how wallet references are handled, how cookies affect a device session and how to request a correction or access decision. Where a right or restriction varies by location, access depends on local law.

The Privacy Policy covers account contact details, phone verification, device and session signals, wallet references, support messages, cookies and retention. It explains why we use each category, how you can ask about it and which access decisions depend on local law.

We may record the contact detail used for your account, the phone verification result, login events and device signals connected with access. We use these records to identify your account, investigate unusual sessions and answer a privacy request.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account reconciliation. We use those references to match receipts and wallet status, not to request secret wallet credentials.

Cookies may keep a signed-in path active, remember a language choice or support session continuity on your phone and desktop. Your browser settings control them. Restricting cookies can change how access works, but it does not erase records already retained for security or legal needs.

You can request a correction through the account help route and explain which record is inaccurate. We may ask for account verification before changing it, so the request is linked to the right account. The available action depends on local law and the record type.

We retain account, security and transaction references while they support operations, security or legal obligations. After that need ends, our process removes the record or limits its use. A retention question can be sent through account help with the relevant record type.

Use account help and state that your request concerns the Privacy Policy. You can ask about data access, purpose, correction, cookies, device sessions or wallet references. Share a phone reference or transaction date when useful, never a password or wallet PIN.