Reference

Privacy Policy for zaraplay Accounts

The zaraplay Privacy Policy shows what we collect when you open an account, sign in from a mobile browser, or use DANA and QRIS at the cashier.

Account data explainedWallet records coveredCookie choices includedContact steps provided
Explore Our Lobby Read FAQ
zaraplay Privacy Policy for zaraplay Accounts
CONTACT ROUTES

Privacy Help Beside Your Account

A clear contact route matters when you want to ask about a record, cookie, or account detail. We keep privacy questions connected to the same account path used for login and wallet status, so you can identify the relevant activity without sending payment credentials in an open message. If you are in Jakarta or elsewhere in Indonesia, use the support path shown after account access and include the request type described in our Privacy Policy.

Team online

Account privacy request

Use the account support path to ask what personal details we hold for your zaraplay profile. Include the email or phone detail linked to the account, but never send your password, PIN, or full wallet credential in the message.

Wallet record question

When a DANA, OVO, GoPay, or QRIS reference needs clarification, tell us the date and payment rail shown in your account. We can direct the request to the relevant status record while keeping the wallet number masked where possible.

Access and cookie help

If a mobile browser does not retain your privacy choice or sign-in session, contact us through the account help route. We will ask for device and browser details only when they help trace the setting or access event.

HANDLING DETAILS

How We Apply This Privacy Policy

Privacy controls work best when they match real account actions, so we describe them beside the steps you take.

Account security records

We use sign-in time, device signals, and phone verification status to help protect your account from unusual access. These records support security checks around the account path; they do not give us your password or the private PIN held by your wallet provider.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity may create a reference in our records. We use that reference to match a cashier request and check its status, while payment credentials remain with the relevant payment service.

Cookies and browser use

Cookies can keep a session working, remember a selected setting, and help us understand whether a page loads correctly. On your phone, you can manage browser permissions; removing cookies may require you to sign in again before reaching the lobby.

Retention approach

We keep personal data only for the period needed for the purpose described in the Privacy Policy, account protection, dispute handling, or a legal requirement. When a record is no longer needed, our process calls for deletion or removal of direct identifiers.

Correction requests

You can ask us to correct an inaccurate contact detail or account record through the support route. We may verify that you control the account before changing it, which helps prevent another person from altering your phone, email, or wallet reference.

Policy questions

For a question about how your data was used, name the account step involved, such as login, phone verification, QRIS payment, or access to Fishing God. Specific details help us locate the relevant record without asking you to disclose unnecessary credentials.

Privacy Policy Questions for Indonesia

These Privacy Policy answers focus on the questions you are most likely to have before opening an account or checking a wallet record. We keep the examples practical, from phone verification and QRIS references to cookies on a mobile browser. If your situation is different, use the contact route described above and tell us which account action you are asking about.

The Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, support messages, and payment references. It explains why we use each category, how retention works, and how you can request correction or ask about a record linked to DANA, OVO, GoPay, or QRIS.

Phone verification helps us confirm that you control the contact detail used for account access and supports security checks when a sign-in looks unusual. We record the verification status rather than your private phone PIN, and the applicable access position depends on local law.

Yes. The Privacy Policy covers the payment reference created when you use DANA or QRIS, along with OVO, GoPay, bank transfer, or a virtual account. We use the reference to match a cashier request and check status; wallet credentials remain with the payment service.

Cookies may keep your sign-in session active, remember a privacy choice, or show whether a mobile page loads correctly. You can manage them through your browser settings. Clearing cookies can remove saved choices and may require another sign-in before account access.

You can contact us through the account support route to ask about personal data linked to your profile or request a correction. Tell us the relevant account step, such as phone verification or a QRIS reference, and we may verify account control before responding.

We retain account data for the period needed for the purpose stated in the Privacy Policy, account security, dispute handling, or a legal requirement. The retention period can differ by record type, including login events, wallet references, cookies, and support correspondence.

Use the support path connected to your account and describe the specific concern, such as a device record, cookie setting, or wallet reference. Do not send a password, PIN, or full payment credential. Our team can then route the Privacy Policy request to the relevant record.

Related Pages

zaraplay Indonesia Access guide About Us sportbet77 Account information