Reference

Privacy Policy for Your Account

fancybet Privacy Policy explains what we collect when you open an account, sign in on mobile or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
Explore The Lobby Read FAQ
fancybet Privacy Policy for Your Account
CONTACT YOUR WAY

Three Routes For Privacy Help

A clear contact route helps when you want to ask about the Privacy Policy, correct an account detail or check why a data request needs more time.

Policy questions Use the support contact route from your account area for questions about the Privacy Policy, collected details or cookie choices. Tell us the email or phone detail linked to your account, and we can direct the request without asking for your DANA, OVO, GoPay or QRIS password.
Correction requests If your account name, phone detail or contact address needs correction, send the request through support after signing in. We may ask for an account step to confirm that the request comes from you before changing stored details or replying about linked wallet records.
Access concerns If a mobile sign-in looks unfamiliar, contact support from the account path and describe the device and time shown. Do not send a password or one-time code. We can review the access record, explain the next step and help protect the account.
SIX DATA CONTROLS

What We Do With Account Data

Privacy Policy requests are handled against the account record rather than a broad marketing profile.

Collected details

We collect details you enter during account opening, such as contact and verification fields, together with sign-in events and support messages. When you use QRIS or a wallet route, related references may be stored to connect the request with your account without storing your wallet password.

Cookie controls

Cookies can remember a session, keep a policy choice available and help us spot repeated unusual access. On a phone browser, you can clear site cookies through browser settings; doing so may sign you out and require the account step again.

Account security

We use sign-in details, device signals and verification steps to reduce unauthorised account access. If you move from mobile to desktop, a fresh sign-in may be required. Keep your password and one-time code private, because our support route does not need either.

Wallet references

Payment records can include a reference, amount status and selected rail for DANA, OVO, GoPay, QRIS, bank transfer or virtual account. These details help us match a receipt or pending status to the correct account; they do not replace your bank or wallet records.

Retention periods

We keep account, support and transaction records only while they serve account administration, dispute handling, security checks or legal duties. When a record no longer has a valid purpose, we remove it or separate it from direct account details according to our internal retention process.

Change requests

You can ask us to access, correct or delete eligible personal details through the support contact route. Include the account email or phone detail and the exact request. We may verify ownership first, and some transaction or security records may remain when a legal or dispute need applies.

Privacy Policy Questions Answered

These answers address the Privacy Policy searches we hear most often from people opening or using an Indonesia account. They explain the practical route for checking stored details, managing cookies, asking for changes and understanding why wallet or device records may appear. If your question is not covered, use the account support contact path and include enough detail for us to locate the right record.

The fancybet Privacy Policy covers account details, verification fields, sign-in events, device and browser signals, cookie choices, support messages and payment references. It explains why we use these records for account access, DANA, OVO, GoPay, QRIS, bank transfer and virtual account administration.

We may keep a payment reference, selected rail and status so we can connect a DANA or QRIS request with your account. We use that record for matching, support and security checks. We do not ask for or need your wallet password through our contact route.

Yes, you can ask for access to eligible account data through the support contact route shown in your account area. Include the email or phone detail linked to the account. We may verify ownership first, and records kept for legal, dispute or security reasons may have limits.

Sign in, open the support contact path and state which contact or verification detail is inaccurate. We may request an account ownership check before making a change. The Privacy Policy allows corrections where appropriate, while transaction records may need to remain unchanged for traceability.

Cookies can keep your session active, remember a policy choice and help identify unusual sign-in behaviour. You can clear them in your mobile browser settings, but that may sign you out and require the account step again. Cookie handling remains subject to your browser choices.

We retain records while they support account administration, payment matching, support, dispute handling, security checks or legal duties. Retention is not unlimited by default. When a record no longer serves a valid purpose, we remove it or separate it from direct account details.

The Privacy Policy is written for the account and data routes available to our Indonesia audience, but access and eligibility depends on local law. If a local rule affects your request, we will explain the applicable account path and any limit on the data response.

Related Pages

fancybet Indonesia FAQ Blackjack fancybet Login fancybet Casino