Reference

garuda55 Privacy Policy for Your Account

garuda55 Privacy Policy explains what we collect when you open an account, use DANA, OVO, GoPay or QRIS, and move between the mobile lobby and desktop access.

Account dataWallet recordsCookie choicesSecurity checks
garuda55 garuda55 Privacy Policy for Your Account
CONTACT ROUTES

Where Privacy Questions Reach Our Team

A privacy request should reach the same account route you already use, so we can confirm that the request belongs to you before changing or sending data. Our support chat and account contact form are available from the support area, with current service hours shown beside the contact route. If a wallet status or receipt raises a data question, include the account phone number and transaction reference, not your wallet password.

Team online

Support chat

Use the support chat for questions about the Privacy Policy, cookie choices or account records. We may ask for your verified phone number and a recent reference so we do not disclose data to the wrong person.

Account contact form

The account contact form handles requests to correct profile details, ask about retention or obtain a copy of personal data. Describe the requested change clearly and send it from the email or phone linked to your account.

Payment receipt check

For DANA, OVO, GoPay or QRIS records, attach the payment reference or receipt image with sensitive wallet credentials hidden. We use the reference to locate the record without requesting your wallet PIN.

HANDLING PRACTICES

Account Security From Login To Retention

We keep this policy practical by tying each data action to an account event: login, phone verification, wallet matching, support contact or a requested change.

Collection

We collect account details you provide, verification results, device and session signals, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Cookie control

Cookies can keep a login session active, remember selected settings and flag unusual access. You can clear browser cookies, although doing so may require a fresh login and phone verification.

Account protection

Before account data is changed or released, we compare the request with the phone or contact details on file. We never need your wallet PIN, banking password or one-time code for a privacy request.

Retention

We keep records for the period needed to operate the account, resolve a payment or security matter, and meet a legal duty. When a record is no longer needed, our process removes or de-identifies it.

Correction request

You can ask us to correct inaccurate account details through support chat or the account contact form. Include the old value, the requested correction and a matching account contact for verification.

Data access

You may ask what personal data we hold about your account and how it was used. We verify your identity first, then explain the available record format and any lawful reason for withholding a part.

Privacy Policy Answers For garuda55 Accounts

These Privacy Policy answers focus on the account and wallet questions we expect before access begins. They explain what you can request, why verification appears, how cookies behave on a phone, and which details help us locate a transaction without exposing sensitive payment credentials.

It covers account details, phone verification, device and session signals, cookies, support messages, payment references and retention. It applies when you use the mobile or desktop account path where local law permits.

No. We use transaction references and status details to match DANA, OVO, GoPay or QRIS activity. We do not ask for your wallet PIN, banking password or login credentials.

Phone verification helps us confirm account ownership before access or a data request is completed. It also helps identify unusual sign-ins and prevents another person from receiving or changing your records.

Yes. Send a request through support chat or the account contact form using your linked phone or contact detail. After identity checks, we will explain which records can be supplied and in what format.

Tell us which account detail is inaccurate and what it should say. We compare the request with your account contact, then update eligible records or explain why a legal or security record must remain unchanged.

Cookies can maintain a session and remember selected settings while you move from login to the mobile lobby. Clearing them may sign you out and trigger another phone verification step.

Use the support chat or account contact form shown in the support area. Include your account phone number and request type, but hide wallet passwords, banking credentials and one-time security codes.