Reference

How tegaltoto Handles Your Privacy Policy

Your privacy choices stay close to the account steps you use, from phone verification to DANA or QRIS payment records.

Clear data purposesCookie choicesAccount access requestsIndonesia account context
tegaltoto How tegaltoto Handles Your Privacy Policy
HELP ROUTES

Where To Ask About Privacy Access

A clear contact route helps when you want to see, correct or remove personal data connected with your account.

Account support Use our account support chat for a Privacy Policy request involving your login, phone verification or profile details. Include the registered contact and a short description so we can locate the correct account without asking you to send a wallet password or payment PIN.
Cashier records For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account record, use the cashier help path and attach the payment receipt reference only. We use that detail to check status while keeping your wallet credentials outside our support conversation.
Privacy request Ask for a copy, correction or removal of eligible personal data through our privacy contact route. We first confirm that you control the account, then explain any lawful reason a record must remain before we complete the requested change.
ACCOUNT CARE

Privacy Controls From Login To Retention

Our privacy process follows the points where account data is most useful: opening access, confirming a phone, matching a wallet record and answering a support request.

Account details

We use the contact details you provide to create and maintain your account, send access-related messages and respond to requests. If your phone number changes, ask support to update it after an account check so an old number is not left as the active contact.

Phone verification

Before account access or a sensitive data request, we may compare your phone verification status with the account record. This step helps us avoid disclosing profile or payment details to someone who only knows a username.

Cookies and device

Cookies and similar device signals can remember session settings, protect sign-in flow and show whether a page has already loaded. You can adjust browser controls, though refusing essential cookies may prevent the account path from working correctly.

Payment references

Payment references from DANA, QRIS, bank transfer or a virtual account help us reconcile a receipt and investigate a status question. We do not ask you to provide a wallet PIN, full password or unrelated private credential.

Account security

We record sign-in time, device context and verification events when needed to protect your account. If an unfamiliar session appears, contact support through the account route and avoid sharing one-time codes in chat or messages.

Retention and changes

We keep each data category only for its stated operational, security or legal purpose. You can request access, correction or deletion where local law permits, and we will explain the result when a record must remain for a defined reason.

Privacy Policy Questions Indonesian Accounts Ask

These answers cover the requests we expect from someone checking the tegaltoto Privacy Policy before opening an account. They focus on account records, wallet references, device activity, cookies and contact steps rather than general lobby use. If your situation involves a specific receipt or verification event, include that reference in your private support request so we can check the right record.

It covers account details, phone verification, sign-in and device signals, cookies, support messages, payment references and retention. It also explains why we use those records, who may access them for a stated purpose, and how you can request access, correction or deletion.

We keep a payment reference to match a receipt with your account, confirm a status or resolve a support question. The reference is not permission to access your wallet, and we do not ask for your DANA, QRIS, OVO or GoPay PIN.

Yes, where local law permits. Contact account support from the route linked to your login, identify the registered phone or email, and request a data copy. We may verify account control before releasing records that contain private account or payment details.

Send a correction request through our privacy contact route and state which account detail is inaccurate. We may ask for phone verification or another account step, then update the relevant record or explain why a particular historical entry cannot be changed.

We may use essential cookies and device signals to maintain sign-in, remember session choices and protect account access. Browser settings can restrict optional cookies, but blocking essential ones may interrupt the mobile path from login to the account area.

Retention depends on the data type and its purpose, such as account operation, payment reconciliation, security or a legal requirement. We remove or anonymise records when they are no longer needed, unless a longer period depends on local law.

You can submit a deletion request through support, and we will assess it under the Privacy Policy and applicable local rules. Where local law permits, eligible records are removed or anonymised; some security, payment or legal records may need to remain.