Reference

Open fantatogel Privacy Policy for Indonesia

Our Privacy Policy explains how fantatogel handles the account details, device data and wallet records connected with your access to Auto Roulette, Aviator and other lobby areas.

Clear data purposesWallet record contextRequest path included
fantatogel Open fantatogel Privacy Policy for Indonesia
CONTACT PATHS

Find help for privacy requests

A clear contact path helps when you want to ask what data we hold or why a wallet record appears in your account history. Use the support route shown on our site and include your registered phone detail, request type and any relevant receipt reference. We will use those details to locate the correct account without asking you to send a password or full payment credentials.

Team online

Account questions

Ask about profile details, phone verification or sign-in records through the listed support route. Include your registered contact detail so we can distinguish your request from another account.

Wallet records

For DANA, OVO, GoPay or QRIS data questions, add the transaction date and visible status reference. Never send a password, wallet PIN or complete card credential in a message.

Correction requests

Tell us which account detail needs changing and why. We may ask for an account step or phone verification before acting, so a request is connected to the right person.

HOW WE HANDLE DATA

Browse fantatogel privacy practices

Privacy choices work best when each data use has a clear reason. We separate account access, payment status, security checks and service messages so your request can be handled without collecting unrelated…

Account details

We may hold your registered phone detail, login identifiers and verification result to connect your account with the correct access request. We use these details for account handling rather than asking for unnecessary profile data.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create reference data such as amount status, date and receipt code. These records help us trace a wallet question without storing your wallet PIN.

Device signals

Browser, device and session signals can be assessed when you sign in or complete phone verification. They help us spot unusual access patterns and protect the account without reading unrelated files on your device.

Cookie choices

Cookies and similar storage may keep a session active, remember selected settings or measure page performance. Your browser controls can remove or restrict them, although some account steps may then need to be repeated.

Retention period

We retain account, security and payment references only for the period needed for the stated purpose, dispute handling, security checks or legal duties. The applicable period can differ by record type and local requirement.

Policy requests

You can ask what we hold, request a correction or question a data use through the listed support contact. We may verify your account first, then explain the outcome and any reason a record must remain.

Find answers about Privacy Policy

These Privacy Policy answers cover the account, device and payment questions you may search before opening access. If your situation is not covered, send a focused request through the contact path and include only the details needed to identify your account.

It covers data linked to your account access, phone verification, device sessions, cookies, support requests and payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

Phone verification helps connect an access request to your account and supports security checks when sign-in activity looks unusual. We may ask you to confirm details before changing account information.

Yes. The Privacy Policy explains how we use QRIS, DANA, OVO and GoPay reference details, including status, date and receipt codes, to trace payment questions without requesting your wallet PIN.

Use the listed support contact and state whether you want access to stored details or a correction. Include your registered phone detail, but do not send passwords, wallet PINs or complete credentials.

Retention depends on the type of record and its purpose. Account, security and payment references may remain for handling disputes, security needs or legal duties, then are removed or managed under applicable requirements.

Your mobile browser settings can remove or restrict cookies and similar storage. Some sign-in or account steps may need to be repeated after that change, because session settings may no longer remain.

Use the support route shown on the site for a Privacy Policy question. Access and eligibility depends on local law, and we may verify your account before discussing personal records.