Reference

Privacy Policy for Your grtoto Account

Our Privacy Policy explains what we collect when you open a grtoto account, sign in from a phone, or use DANA and QRIS at the cashier.

Account recordsWallet activityCookie choicesAccess requests
grtoto Privacy Policy for Your grtoto Account
CONTACT ROUTES

Three Ways to Ask About Your Data

A clear support route helps you act on this Privacy Policy when an account or wallet record looks unfamiliar. Contact us through the support chat and include the phone number connected to your account, the date of the event and the payment reference where relevant. We use those details to locate the right record without asking you to send a full wallet password or private login code. If you are checking a request from a mobile browser, keep the same device available until our team confirms the next step.

Team online

Privacy request

Use support chat to ask what account details we hold or to request a copy of information linked to your phone verification. Include your account phone number and a clear request so we can check identity before discussing private records.

Wallet record check

For a DANA, OVO, GoPay or QRIS record, send the transaction reference and date through the support route. We compare that reference with the cashier history and explain whether the entry is pending, matched or needs another account step.

Correction request

If your name, phone detail or account record needs correction, tell us which field is wrong and why. We may ask for phone verification before changing it, protecting the account from an unauthorised request made from another device.

DATA PRACTICES

Six Practical Controls Behind This Policy

The Privacy Policy is supported by practical handling steps rather than broad promises. We separate account access events from payment references, use device signals to identify unusual sign-ins and keep support requests…

Account details

When you open an account, we collect the details needed for account access and phone verification. This can include your phone number, submitted account fields and sign-in history. We use it to connect you with the correct account rather than exposing another person’s records.

Device signals

A phone browser or desktop session can create device, browser and connection signals. We use these signals to recognise an active session, investigate unusual access and protect account changes. They are not a substitute for your phone verification or private access details.

Cookie controls

Cookies and similar browser storage can remember session choices, support sign-in flow and help us understand which policy page was opened. You can manage cookies through your browser settings, although switching them off may require you to repeat an account step.

Wallet matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create references used to match a cashier event. We retain the reference, amount status and timing needed for reconciliation, while your wallet password remains outside our requested support details.

Retention timing

We keep account, security, support and payment-reference records only for the period needed for account administration, dispute handling, security checks and legal duties. When a record is no longer needed for those purposes, our handling process is to remove or securely separate it.

Access changes

You can contact us to ask for access, correction or clarification about personal data connected to your account. We first check the request through the account phone path, then explain any limitation where a record must remain for security, payment matching or legal reasons.

Privacy Policy Answers for grtoto

These Privacy Policy answers focus on the searches we hear before an account is opened or a wallet record is checked. They explain the data path, the account step and the contact route in plain English for Indonesian customers. If your question is not listed, use support chat with your account phone number and the relevant date or reference.

The grtoto Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, support messages and payment references. It applies when you access the lobby from a phone or desktop and when DANA, OVO, GoPay, QRIS or bank transfer creates a cashier record.

We use your phone number to create and identify your account, complete the phone verification step and route a data request to the correct record. It also helps us investigate an unfamiliar sign-in or account change without relying only on a device signal.

Yes. The Privacy Policy includes transaction references and status details connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. We use these records to match a cashier event, answer a receipt question and investigate a mismatch.

You can request access through support chat by giving the phone number linked to your account and describing the records you want. We check account ownership before sharing private details, then explain which account, device, support or wallet records can be provided.

Send a correction request through support chat and identify the field that is inaccurate, such as a phone detail or account name. We may ask you to complete phone verification before changing it, helping prevent a person on another device from editing your account.

Retention depends on the type of record and why it is needed. Account, security, support and payment-reference data may remain for account administration, dispute handling, security checks or legal duties. We remove or securely separate records when those purposes no longer require them.

Use the support chat and include your account phone number, the question, and a payment reference or date if your request concerns DANA, OVO, GoPay or QRIS. We use that information to locate the relevant record and explain the next step.