Reference

Privacy Policy for garuda44 Account Data

Your garuda44 Privacy Policy gives you a clear path to see how account details, device signals and wallet records are handled before you open an account.

Account dataWallet recordsCookie choicesAccess requests
garuda44 Privacy Policy for garuda44 Account Data
CONTACT ROUTES

Get Help With Your Privacy Request

A privacy question should not require you to search through unrelated account pages. From your account area, use the support route shown near account access and include the phone number or email…

Access request Ask us to confirm which account data is held about you. Include your registered contact detail so our support route can match the request without exposing another account's records.
Wallet record query If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the date and visible transaction reference through account support. Do not include your wallet PIN or full security code.
Change request Use the same account support channel when your contact detail or profile data needs correction. We may ask for phone verification before changing details that affect account access.
SECURITY PRACTICE

Account Data Controls We Apply

We handle this Privacy Policy through practical account controls rather than a hidden back-office process. Access checks connect phone verification, login activity and payment references, while cookie settings help us understand which…

Data handling

We use account details, phone verification results, login events and payment references for the specific account, security and support purposes described in this Privacy Policy.

Cookies on devices

Cookies may remember session settings and help us understand whether you return through a mobile browser or desktop path. Your browser controls can remove or restrict them.

Account security

Phone verification and sign-in checks help connect requests to the right account. We do not need your DANA, OVO, GoPay or QRIS wallet PIN for a privacy request.

Retention window

Records remain available only as long as needed for account operation, security review, support history or legal duties. The period can differ by record type and local requirements.

Access copies

You can ask what personal data is linked to your account through the support route. We may request phone verification before sharing a copy or confirming account details.

Corrections

If your name, contact detail or other account data is inaccurate, tell us which field needs changing. We check the request against the account before applying an update.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the questions you may have before opening a garuda44 account from Indonesia. They explain wallet records, cookies, phone verification, requests for account data and the access wording that applies when local rules differ. If your question is not covered, use the support path connected with your account.

It covers account details, phone verification, login and device activity, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security checks and how to request access or correction.

Our Privacy Policy does not require you to send a DANA, OVO, GoPay or QRIS wallet PIN for account support. We may handle a payment reference, status or amount record needed to connect an account question with the relevant wallet action.

Open the support route shown in your account area and ask for an access copy under the Privacy Policy. Include your registered phone number or email. We may complete phone verification first so account data is not disclosed to the wrong person.

Yes. Send a correction request through the account support route and identify the field that needs changing. The Privacy Policy process may ask for phone verification, especially when the requested change affects login, wallet matching or account ownership.

The Privacy Policy explains that cookies can retain session settings and help distinguish a mobile browser from a desktop path. You can remove or restrict them through your browser controls, although some account steps may then require another sign-in.

The Privacy Policy does not use one period for every record. We keep account, security, support and payment references only for the time needed for their stated purpose, operational checks or legal duties, with the period affected by local requirements.

Yes. Account access and eligibility depend on local law. Where local law permits, we apply the Privacy Policy to account data and support requests from Indonesia, while any required regional restriction or identity step remains part of the access process.