Reference

Open garuda365 Privacy Policy before account access

garuda365 Privacy Policy explains how we handle your phone verification, device signals and wallet details when you open an account or access the lobby.

Account dataWallet recordsCookie choicesAccess requests
Explore Our Lobby Read FAQ
garuda365 Open garuda365 Privacy Policy before account access
CONTACT PATHS

Switch to the right privacy support route

A clear contact path helps you ask about personal data without explaining your whole account history. Use the support route displayed in your account, and include the email or phone detail attached to your profile so we can locate the correct record. We keep privacy questions separate from game or wallet troubleshooting, while still checking receipt and access references when they are needed.

Team online

Policy request

Send a question through the account support channel shown to you, naming the data concern and the phone verification detail connected with your garuda365 account.

Wallet record

For DANA, OVO, GoPay or QRIS privacy questions, include the payment reference rather than your wallet password; this lets us check the record without requesting unnecessary credentials.

Access help

If a policy page or account request does not open on mobile, use the support path beside the account area and tell us your device type and sign-in stage.

ACCOUNT SAFEGUARDS

Browse our data safeguards and request steps

Privacy becomes practical when each account action has a clear data purpose. We use the safeguards below to explain how your records move through account access, payment checks and policy requests.

Collection purpose

We collect details needed for account creation, phone verification, sign-in protection, wallet matching and support replies. Browsing Dragon Tiger or Aviator does not by itself require unrelated profile details.

Cookie controls

Cookies and similar device signals help maintain your session and remember selected settings. On mobile, review browser cookie controls before signing in if you do not want those preferences stored.

Account security

Phone verification, sign-in events and device signals help us identify unusual account access. Never send a password or wallet PIN through a support request about the Privacy Policy.

Retention periods

We retain account, payment-reference and support records only for the period needed for the stated purpose, account administration, dispute checks or duties that depend on local law.

Data sharing

We may share necessary records with service parties that help process account access, payment references or security checks. We limit the shared detail to the task being handled.

Change requests

You can ask us to access, correct or clarify personal data through the account support route. Include the profile contact detail and explain the requested change so we can verify ownership.

Ask garuda365 Privacy Policy questions directly

These answers address the privacy searches we hear most often before account access. They cover wallet references, mobile browsing, correction requests and the local-law wording that applies when you ask whether the service is available to you.

It covers account creation, phone verification, sign-in events, device signals, cookies, support records and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect an account request with the correct profile and supports account-security checks. We use the verification detail for that purpose rather than asking for your wallet PIN.

Our Privacy Policy concerns payment references and status checks, such as a DANA receipt or QRIS transaction reference. Do not send a wallet password, PIN or one-time code through support.

Use the account support route displayed on the site and state whether you want access, correction or clarification. Add your profile phone or email detail so we can verify the request.

Cookies can maintain your sign-in session and selected settings on a phone browser. You can inspect or clear them through your browser controls, though clearing them may require another account sign-in.

Retention depends on the purpose of each record, such as account administration, payment-reference checks or support history. We keep records for the period needed for that purpose and applicable local duties.

Access or eligibility depends on local law and is available where local law permits. Check the policy and access wording for your location before opening an account or sending personal details.

Related Pages

garuda365 Indonesia Access guide MotoGP Betting FAQ About Us