Reference

Privacy Policy For Your 3wickets Account

3wickets Privacy Policy explains how we handle the details connected to your account, device, wallet status and support requests while you use our Indonesia service.

Account dataWallet checksDevice privacyYour choices
Explore Our Lobby Read FAQ
3wickets Privacy Policy For Your 3wickets Account
PRIVACY HELP DESK

Get Clear Answers About Your Data

A privacy question should not leave you guessing about the next account step. We provide a direct support route for requests about stored details, phone verification, wallet matching, device records and policy access. Include the email or phone detail linked to your account, the subject of your request and any relevant payment reference. We may ask for an account check before changing personal details, so that a request from Makassar or another Indonesian location is handled against the correct account.

Team online

Account data request

Ask us which account details are connected to your profile and why they are used. Include your registered phone number or email, but never send a password or one-time verification code in a support message.

Wallet status question

If DANA, OVO, GoPay or QRIS shows an unexpected status, share the payment reference and approximate time. We use those details to trace the account record without asking you to repeat unrelated personal data.

Policy contact path

For correction, deletion or access requests, use the contact path linked from your account area and describe the change clearly. We confirm account ownership before acting and explain any local-law reason for keeping a record.

DATA CONTROL POINTS

What We Do With Account Details

Privacy at 3wickets is handled through practical controls rather than broad promises. We separate account access records from the payment references needed to reconcile DANA, OVO, GoPay, QRIS, bank transfer and virtual…

Account creation

When you open an account, we collect the details needed to create your profile and begin phone verification. We use that information to connect your sign-in, account notices and requested support work to one record.

Payment matching

A wallet name alone does not complete a payment record. We may use a reference, amount, status and timing to match DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity with your account.

Cookies and devices

Cookies and device signals can remember session state, detect unusual sign-in behaviour and keep the mobile path from login to the lobby consistent. You can manage browser permissions, although some account functions may then need another check.

Account security

Phone verification and sign-in records help us identify attempts to enter your account. Keep your password and verification code private, sign out on shared devices and contact us if a device record looks unfamiliar.

Record retention

We keep personal and payment records for as long as needed for account operation, security checks, dispute handling or a legal requirement. When a record is no longer needed for those purposes, our process addresses its removal.

Changing your details

You can ask us to correct account details that are inaccurate or incomplete. Send the requested change through the account contact path, identify the affected field and complete any ownership check required before we update it.

Privacy Policy Questions You May Have

These Privacy Policy answers focus on the account actions Indonesian customers ask about most often. We explain what may be collected, how payment references are used, how to request a change and what can affect access. If your case involves a specific DANA, OVO, GoPay or QRIS reference, include that reference when you contact us so we can locate the relevant record.

The 3wickets Privacy Policy covers details linked to your account, phone verification, sign-in activity, device and cookie signals, support requests, and payment references. It explains why we use those details, how long records may remain and how you can request access or changes.

We may retain the payment reference, status, timing and account-matching details needed to check a DANA or QRIS transaction. The exact record depends on the payment route. We use these details for reconciliation, security and support rather than unrelated account purposes.

Yes. Send a correction request through the account contact path and describe the field that needs changing. We may ask you to confirm ownership using the registered phone or email before editing the record, which helps prevent an unauthorised change.

Cookies can keep your session active, remember basic choices and help us identify unusual sign-in behaviour. Device signals may also support security checks from mobile or desktop. Browser controls can restrict cookies, but some account steps may require another sign-in.

We keep records while they are needed for account operation, payment matching, security, dispute handling or a legal requirement. Retention can vary by record type. When the relevant purpose ends, we follow our process for deletion or removal where applicable.

Contact us through the account privacy path, identify the records you want removed and provide the registered account detail for an ownership check. Deletion applies where local law permits; some transaction or security records may need to remain for a stated reason.

Yes. Account access and eligibility depends on local law and applies where local law permits. If a local requirement affects your account or a data request, we use the available contact path to explain the relevant restriction and next step.

Related Pages

3wickets Indonesia 3wickets Casino Register Volleyball Betting About Us