Reference

garuda62 Privacy Policy for Your Account

Our Privacy Policy explains what account, device and wallet details we collect when you open garuda62 in Indonesia.

Clear data purposesWallet status contextAccount access choicesPolicy contact path
garuda62 garuda62 Privacy Policy for Your Account
CONTACT YOUR WAY

Privacy Policy Help For Account Questions

A clear contact path helps when you need an answer about the Privacy Policy rather than a lobby instruction.

Policy questions Use the contact route displayed with this Privacy Policy and mention the subject of your request. We will explain which account details are needed before checking your record.
Wallet references For DANA, OVO, GoPay or QRIS questions, share the payment reference without sending a password or wallet PIN. This lets us separate receipt matching from wider account data.
Account corrections If your phone verification detail or account record needs correction, state the field clearly. We may ask for an account step that confirms the request belongs to you.
DATA HANDLING

What We Do With Your Privacy Choices

We keep this policy practical by connecting each data use to an account action you recognise.

Account details

We use your phone number and verification result to support sign-in and account recovery. We do not need your password in a support message, so keep that secret outside every contact request.

Payment records

A DANA, OVO, GoPay or QRIS reference can be retained with the related account event. Bank transfer and virtual account records help us trace a receipt without storing your wallet PIN.

Device signals

Our mobile page may receive browser, device and access-log details used to keep sessions working and identify unusual sign-in patterns. These signals support account protection rather than lobby personalisation claims.

Cookie choices

Cookies can keep a session active and remember settings needed for the account path. Your browser controls whether cookies are accepted, and changing that setting may affect sign-in continuity.

Retention periods

We retain records only for account support, receipt matching, dispute handling, security checks or legal duties. When a record is no longer needed for those purposes, our handling process addresses its removal.

Requests and contact

You may ask for a copy, correction or deletion of eligible account data through the policy contact route. We may verify your account step first, then explain any legal reason for keeping a record.

Privacy Policy Answers For garuda62

These Privacy Policy answers address the searches we hear most often from people checking account access in Indonesia. Each response focuses on the data path, payment reference or device step involved, so you know what to include when contacting us.

It covers account details, phone verification, device and browser signals, cookies, access logs, payment references and messages you send about your account or a DANA, OVO, GoPay or QRIS record.

Phone verification helps connect an account request to you and supports sign-in protection. If you ask us to change account data, we may use the same account step before handling the request.

No. We ask for a payment reference when checking DANA, OVO, GoPay or QRIS status, but you should never send a wallet PIN or password through a support contact route.

Cookies can maintain a session and remember settings needed for the account path on your mobile browser or desktop browser. Your browser settings can remove or block them, though sign-in may be affected.

Yes. Send a request through the contact route displayed with this Privacy Policy and identify the account record you want. We may confirm ownership before providing, correcting or assessing the requested data.

Retention depends on the record and its purpose, such as account support, payment reconciliation, security checks, disputes or legal duties. We address removal when a record is no longer needed.

Yes. Account access and eligibility depends on local law. Our Privacy Policy explains the data handling used on the available account path, while local requirements may affect whether that path is available.