Reference

Privacy Policy for Your garuda365 Account

Our Privacy Policy explains how we collect, use and protect the details connected with your garuda365 account, including phone verification, login activity and wallet records.

Clear data purposesWallet record controlsCookie choicesAccount request path
garuda365 Privacy Policy for Your garuda365 Account
REQUEST SUPPORT

Reach Us About Privacy Policy Requests

Questions about our Privacy Policy should include the account detail that helps us locate the correct record without exposing extra personal data.

Account help path Use the account help route for Privacy Policy questions about your profile, phone verification…
Wallet record check For a Privacy Policy request involving DANA, OVO, GoPay or QRIS, provide the relevant…
Security concern If you suspect that your account details were accessed by someone else, contact us…
DATA PRACTICES

Explore How We Handle Policy Details

We keep our Privacy Policy practical by linking each data practice to an account action you can recognise.

Account data

We may hold your account name, phone details, verification state and selected account settings because those fields support login and account ownership checks. We do not need your DANA, OVO, GoPay or QRIS password to match a payment record.

Device signals

When you move from phone login to the lobby, we may record browser type, device identifiers and security events. These signals help us compare normal access with unusual attempts without treating your device data as a public profile.

Cookie controls

Cookies can keep a session active and remember selected settings, while limited usage data helps us identify broken policy or account pages. You can manage cookie permissions through your browser, although some account functions may then require another login.

Payment references

A wallet or bank record may include a reference, amount status and processing time needed to reconcile your account. For QRIS, DANA, OVO, GoPay, bank transfer or virtual account requests, we use the smallest useful record for the support check.

Security controls

Phone verification and login checks help us protect account access before profile or wallet changes are made. If a request looks unusual, we may ask you to confirm ownership through the account path rather than disclose details immediately.

Retention requests

We keep records only while they support the stated account, security, payment or legal purpose. You can ask what we hold, request a correction or ask whether deletion is available; we explain any record that must remain for a defined reason.

Browse Privacy Policy Answers for garuda365

The questions below cover the Privacy Policy points most relevant when you create or use a garuda365 account from Indonesia. Each answer focuses on a practical action, from checking phone verification to asking about cookies or a DANA, OVO, GoPay, QRIS, bank transfer or virtual account record. If your question concerns access or eligibility, that decision depends on local law. Use the account support path when your request includes private account details.

The Privacy Policy covers details connected with account creation, phone verification, login activity, device signals, cookies, support messages and payment references. It explains why we use each category, how we protect it, how long we retain it and how you can request access or correction.

Phone verification helps us confirm that you control the account before access or account changes are completed. It can also support security checks when login activity looks unusual. We use the verification state for account protection rather than asking for your wallet password.

Yes. The Privacy Policy covers payment references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account steps. Send only the reference needed for a support check; we do not need your wallet password to locate a record.

Open the account help path and state which detail needs correction, such as a phone number, profile field or verification status. We may ask you to confirm account ownership before changing it. Include the smallest useful detail so we can process the request safely.

Cookies can maintain your login session, remember selected settings and help us identify basic page errors. Your browser controls whether optional cookies are stored. If you block session cookies, you may need to log in again before reaching account or policy pages.

We retain personal data for the time needed to operate the account, check security events, reconcile payment records or meet a defined legal purpose. You can ask us which category applies to your record and whether deletion is available after that purpose ends.

You can request deletion through the account support route, and we assess which records are eligible. Some data may need to remain for security, payment reconciliation or a legal purpose. We explain the reason for any retained record and the next available action.