Reference

gerhanatoto Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open an account, sign in on mobile, browse Sic Bo or Rocket Crash, and use a local wallet.

Clear collection rulesWallet data contextAccount request path
gerhanatoto gerhanatoto Privacy Policy for Your Account
ASK ABOUT YOUR DATA

Three Ways To Reach Policy Support

A clear contact path matters when your account record or payment reference needs checking.

Account support route Sign in, open account support and describe the Privacy Policy request.
Wallet status path For OVO, GoPay or DANA references, include the transaction reference and date rather than…
QRIS receipt check Send the QRIS receipt through the available support contact when a status record looks…
HANDLING YOUR RECORD

Six Privacy Practices Behind Your Login

We keep this Privacy Policy practical by tying each data use to an account action you can recognise.

Account details

We use the name, phone detail and login credentials you submit to create and maintain your account. Keep your sign-in details private, and contact support if an account record looks unfamiliar.

Device signals

Browser type, device identifiers and sign-in times can help us spot an unexpected access pattern. These signals are reviewed alongside your account details when a login question reaches support.

Cookie choices

Cookies and similar storage can keep a session working and remember basic preferences. You can manage browser storage through your device settings, though changing it may affect account access.

Payment references

A DANA, OVO, GoPay, QRIS or bank-transfer reference helps us match a cashier event to your account. We do not request wallet PINs or full banking passwords in support messages.

Retention periods

We retain account, security and transaction records only for the period needed for account administration, dispute handling, legal duties or a documented policy request.

Change requests

To request access, correction or deletion, contact us through account support with your registered phone detail. We may verify ownership before changing or releasing personal data.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account steps you are most likely to search before opening an account. They cover collection, cookies, device access, payment references and contact routes, so you can decide what to share and how to request a change.

It covers personal data handled when you create an account, verify your phone, sign in, use the mobile lobby, contact support or provide a DANA, OVO, GoPay or QRIS reference.

Phone verification connects an account request to the person attempting access and helps us respond to account questions. We may use that record when checking a login or correcting account data.

Yes. The Privacy Policy explains that cookies or similar storage can keep a session active and remember basic preferences. Your browser settings can manage storage, although access may change.

We may receive browser type, device identifiers, language settings and sign-in times. These details help us investigate unusual access patterns and are considered alongside the account record.

Use account support and include the registered phone detail plus a clear request for access or correction. We verify account ownership before releasing or changing personal data.

We use transaction references, dates and status details to match a payment event with your account. We do not ask for wallet PINs, banking passwords or unrelated private credentials.

You can submit a deletion request through account support. We assess the request against active account needs, dispute handling and legal retention duties, then explain any records we must keep.