Reference

Privacy Policy for Your gemilangtoto Account

The gemilangtoto Privacy Policy explains what we collect when you open an account, sign in from a mobile device, browse Auto Roulette or use DANA and QRIS.

Account dataDevice signalsWallet recordsCookie choices
gemilangtoto Privacy Policy for Your gemilangtoto Account
CONTACT DATA HELP

Where to Ask About Privacy Policy

A clear contact path helps when your Privacy Policy question concerns an account record, device session or wallet receipt.

Account record request Ask us to identify the personal details connected with your account.
Wallet data question For a DANA, OVO, GoPay or QRIS receipt question, share the transaction reference and…
Correction support If a contact detail or device record appears incorrect, tell us what needs changing…
HANDLING YOUR DATA

What We Do With Account Details

Our handling process follows the account events that create a record: registration, phone verification, sign-in, wallet activity and requests sent to support.

Account creation

When you open an account, we collect the details needed to create that account and connect it with your phone…

Device and session data

A mobile browser or desktop session can create records such as device type, browser details and sign-in time.

Cookies

Cookies can keep an account session connected while you move from the lobby to account settings.

Wallet records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create payment references linked to your account.

Retention questions

We keep records for as long as needed for the purpose that created them or for a period required by…

Account security

Never place your password or phone verification code in a support message.

Privacy Policy Questions Before Access

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover the data connected with account access, mobile sessions, local wallets and requests to change or remove a record. If your question is not listed, use the account help route and describe the specific data involved. We will use that context to direct the request.

It covers account details, phone verification, device and session signals, cookies, wallet references and messages sent through account help. It also explains how to ask about access, correction, deletion and retention where local law permits.

Yes. A DANA or QRIS action can create a reference connected with your account so we can check its status and match a receipt. We do not need your wallet PIN or full authentication code for that request.

A mobile or desktop session may provide device type, browser details, session time and access signals. We use these details to connect activity with the right account and examine an unfamiliar sign-in, not to request your private device password.

Use the account help route beside the cashier area and state that you want access to your personal data. Include your registered phone or email detail, but leave out your password and phone verification code.

You can ask us to correct a contact detail or another account record that appears wrong. Tell us the existing detail, the requested change and the account step that helps us verify ownership before we edit it.

Retention depends on why the record was created and on applicable local rules. Account, device and wallet references may be kept while needed for account security or status checks. Ask about a specific record for a tailored response.

The policy is intended for access where local law permits, and account eligibility depends on local law. If your location gives you a specific privacy request right, contact us with that request so we can assess the applicable route.