Reference

hexatoto Privacy Policy for Your Account

Our hexatoto Privacy Policy explains what we collect when you open an account, use the lobby, or check a wallet status, and why each detail is needed.

Account dataCookie choicesPayment recordsAccess requests
hexatoto hexatoto Privacy Policy for Your Account
HELP WITH DATA

Contact Us About Privacy Questions

A clear support path helps when you need to ask about a record, correct an account detail, or understand a wallet reference. Start from the support route connected to your account and include the email or phone detail used during registration. We will use the smallest practical set of questions to locate your request, especially when your issue concerns a DANA receipt, QRIS status, or login record.

Team online

Account request

Use the support path beside your account area to ask what personal details are held, why they are used, or which verification step applies to your request.

Payment record

Send the relevant DANA, OVO, GoPay or QRIS reference without sharing a wallet password. We use transaction details to locate the correct account record.

Access correction

If your name, phone detail or contact record needs correction, tell us through account support. We may confirm ownership before applying a change.

OUR DATA PRACTICE

How We Handle Your Privacy Choices

We treat this policy as part of the account path, not as a separate page you have to decode.

Account details

We collect registration and verification details so we can connect your account activity to the right account. If a field changes, contact us with the updated detail and ownership confirmation.

Cookie controls

Cookies can keep your login path working, remember selected settings, and help us understand page errors. Your browser controls optional cookies, while essential session cookies may remain necessary.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references are used to match status and receipts. We do not ask for your wallet password through support.

Account security

Login events, device signals and verification steps help us detect unusual access. Keep your sign-in details private and contact support if a device record looks unfamiliar.

Retention approach

We keep records for as long as needed for account operation, dispute handling, security checks, and duties that depend on local law. Some records may remain after closure for those purposes.

Request handling

You can ask for access, correction, clarification or deletion where applicable through account support. We may verify your identity and explain any limit required by local law.

Privacy Policy Questions About hexatoto

These answers address the privacy questions you are most likely to have before opening an account or continuing through the Indonesia account path. If your situation is specific, use the support route and mention the account step, device, or payment reference involved.

The hexatoto Privacy Policy covers account, verification, device, cookie, support and payment-reference data collected while you use our pages. It also explains purposes, retention, requests and local-law limits.

We use registration contact details to identify your account, support clear account access, send account-related messages, and confirm ownership when you request a correction or data copy.

Yes. The Privacy Policy covers transaction references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps. These references help us match a payment status without requesting your wallet password.

Use the support route connected to your account and state that you are making a Privacy Policy data request. Include your registered contact detail; we may verify ownership before responding.

Yes, you can request a correction through account support. Tell us which record is inaccurate and provide the updated detail. We may ask for verification before changing the account record.

On a phone or tablet, cookies may keep your login path, settings and account pages working. Your browser manages optional cookies, while essential session cookies may be required for account access.

Yes. Some access, deletion or retention decisions depend on local law. We explain the reason for any limit and still handle your request through the account support path.