Reference

Open garuda 55 Privacy Policy

Our Privacy Policy explains how garuda 55 handles the details connected to your account, mobile browser, wallet records and support requests.

Account dataWallet recordsDevice accessPolicy requests
garuda 55 Open garuda 55 Privacy Policy
CONTACT OUR TEAM

Check your privacy support path

A clear contact route matters when a name, phone number or wallet reference needs attention.

Account privacy request Use the support contact route shown on our site to ask about account data.
Payment record check For a DANA, OVO, GoPay or QRIS question, provide the transaction reference and approximate…
Access concern If a mobile browser sign-in looks unfamiliar, tell us the device path and account…
HANDLE YOUR DATA

Protect your account data choices

We handle this policy area through defined account, device and payment records rather than broad collection for its own sake.

Data we receive

We may receive your account name, phone number, verification result, sign-in details and support messages. DANA, OVO, GoPay, QRIS and bank references are used to connect a payment record with the correct account.

Cookie choices

Cookies can retain a session setting or help us understand policy-page use. You can review cookie controls in your mobile browser, although blocking them may require another sign-in.

Account security

Phone verification and sign-in checks help us distinguish your account from an unfamiliar access attempt. Never include your password, one-time code or complete wallet credentials in a support request.

Retention period

We keep account, support and payment references only for the period needed for account administration, dispute handling, security checks or legal duties, then review whether continued storage is needed.

Request a correction

If your phone number, account name or contact detail is wrong, contact us through the site support route. We may ask for an account step that helps confirm the request belongs to you.

Ask about access

You can ask what personal data we hold, how it was used, or whether a correction or deletion request is available. We assess each request under local requirements and reply through the contact route.

Ask about Privacy Policy access

These answers address the privacy searches we hear most often before an account is opened or a wallet record is checked. If your situation involves a particular phone verification, device sign-in or payment reference, contact us with the smallest useful set of details so we can locate the relevant record.

It covers account details, phone verification, mobile-browser access, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

We use your phone number for account identification and the verification step before account access. It also helps us match a privacy request with the correct account without exposing another person’s details.

Yes. The Privacy Policy explains how we handle DANA and QRIS references received for account records. The relevant wallet or bank may separately control data it collects during its own payment process.

You can send an access request through the support route on our site. Include your registered phone number and the data category you want checked; we may verify account ownership before replying.

Contact us with the incorrect field, such as an account name or phone number, and explain the requested change. We may ask you to complete a verification step before updating the record.

Retention depends on why the record exists, including account administration, payment matching, security checks, dispute handling or legal duties. We review whether continued storage is needed after that purpose ends.

The notice is written for Indonesian account activity, but access and eligibility depends on local law. Where local law permits, we handle requests through the account and support paths described here.