Reference

garitoto Privacy Policy, Clearly Explained

Our Privacy Policy tells you what data we collect when you open an account, sign in, use the lobby, or check a DANA, OVO, GoPay or QRIS transaction.

Plain data purposesCookie choicesAccount request stepsIndonesia access
garitoto garitoto Privacy Policy, Clearly Explained
PRIVACY HELP DESK

Where to Ask About Privacy Policy

A privacy question should not get lost among account messages, so we keep a direct support route beside the cashier path.

Access request Ask us to confirm which personal details are linked to your account. We may request phone verification before releasing account-specific data, so the request reaches the correct person.
Correction request If your phone number or account detail is inaccurate, send the affected field through our site contact route. We compare the request with account records before making a change.
Receipt question For a DANA, OVO, GoPay or QRIS receipt, provide the reference and status shown in your account. We use those details to trace the payment record without asking for wallet credentials.
CONTROLLED DATA CARE

Account Security, Cookies and Retention

We keep privacy work close to the account actions that create data: registration, phone verification, sign-in, wallet status and support requests.

Phone verification

Before account access, we use the phone verification step to confirm control of the registered number. This reduces the chance that a request for personal data is handled for the wrong account.

Login records

We record sign-in time, device type and related technical signals when you access the mobile lobby or desktop site. These records support account security checks and help explain unusual login activity.

Cookie controls

Session cookies keep you signed in during an active visit, while preference cookies remember choices such as language. You can manage browser cookie settings, though some account functions may then need repeating.

Wallet references

Payment records contain references, status and timestamps for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We use these fields to reconcile receipts, not to request wallet passwords.

Retention review

We assess stored account, security and transaction records against their operational or legal purpose. When a record no longer has a valid purpose, our process removes it or separates it from direct account details.

Change requests

You can ask for access, correction or clarification through the contact route on our site. Include your account identifier, describe the requested change, and complete any identity check needed to protect your data.

Privacy Policy Questions for garitoto

These Privacy Policy answers cover the questions you are most likely to have before opening an account or checking a wallet status. They explain account data, cookies, payment references, requests and access conditions in direct terms, with the site contact route available when your situation needs a specific answer.

It covers personal details collected during account creation, phone verification, sign-in, lobby use, payment checks, cookies and support requests. It also explains purposes, retention, security practices and ways to request access or correction.

Phone verification confirms control of the number attached to your account before account access or an account-specific data request. It helps us reduce mistaken disclosures and investigate unusual sign-in activity.

Yes. We may store the payment reference, amount, status and timestamp for DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. These records help match receipts without requesting your wallet password.

Use the contact route shown on our site and state that you want an account data access request. Add your account identifier and complete the identity check we require before providing account-specific details.

Yes. Send a correction request through the site contact route, identify the field that needs updating, and explain the accurate value. We compare the request with account records before applying a change.

Session cookies support sign-in while you move from a mobile browser to the lobby, and preference cookies remember selected settings. Browser controls can limit cookies, but some account steps may need repeating.

Where local law permits, we may share the transaction or identity details needed to process a lawful payment check or answer a valid request. We do not share wallet passwords, and we limit the details to the stated purpose.