Reference

Privacy Policy for Your garuda76 Account

Our Privacy Policy explains how we collect, use and protect details linked to your garuda76 account, device and wallet activity.

Account clarityWallet dataCookie choicesPolicy requests

Explore Our Lobby Read FAQ

How We Apply Privacy Policy

garuda76 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We use account details to create access, confirm a phone number, maintain login protection and answer requests about your records. Transaction details from DANA, OVO, GoPay, QRIS, bank transfer or virtual account are used to match a payment with the correct account and check its status.

1
Device and connection data help us detect unusual sign-ins and keep the session working on mobile or desktop. We do not describe access as universal: eligibility depends on local law and the location connected to your session. Our Privacy Policy also explains when data may be
2
shared with service providers that help operate account, payment or security functions, and how long relevant records are retained.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

REQUEST HELP DIRECTLY

Where Privacy Questions Go

A clear contact path matters when you want to ask what we hold, correct an account detail or question a wallet record. Use our support route from the account area and include the email or phone detail connected to your profile, plus the relevant transaction reference when your question concerns DANA, QRIS or a bank transfer. We use those details to find the right record without asking you to send a full password or wallet PIN. If you are in Yogyakarta and a login session stalls, the same route can connect an access question with a Privacy Policy request.

Team online

Account data request

Ask us which account details we hold by sending the contact detail linked to your profile through our support path. We may check phone verification before discussing private records, so a request reaches the correct account rather than another person.

Wallet record query

For a DANA, OVO, GoPay or QRIS question, provide the account identifier and payment reference, not your wallet PIN. We can then match the receipt status with the relevant record and explain what the Privacy Policy allows us to disclose.

Correction or deletion

If a profile detail is wrong or you want to ask about removal, contact us through the account support route. We assess the request against legal, security and transaction-retention duties before confirming the action or explaining why a record must remain.

HANDLING YOUR RECORDS

What Our Privacy Process Covers

We separate the practical parts of Privacy Policy handling so you can see why each type of data is used.

Account details

We use the details you provide during account creation and phone verification to maintain your profile, confirm access and respond to account questions. Keeping your contact detail current helps us send a request to the right profile without exposing records to another account.

Device and session data

When you move between a mobile browser and desktop, we may record device, connection and session signals linked to that login. These signals help identify unusual access around the lobby, including a sudden change before a wallet status check.

Cookies and settings

Cookies can remember choices that help the account page load in the way you selected. You can manage cookie controls in your browser, although restricting some cookies may affect login continuity or the display of the Privacy Policy and account settings.

Payment references

We receive transaction references and status details needed to connect DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity with your account. We do not need your wallet PIN for a receipt check, and you should never send it through support.

Security controls

We may compare login signals, phone verification status and account activity to protect private records from unauthorised access. If a check pauses your session, support can ask for account details that confirm ownership before discussing a payment or profile record.

Retention and requests

We keep records only for the period needed for the stated purpose or a legal and security duty. You can ask about access, correction or deletion through support; we will explain any identity check, restriction or retention reason that affects your request.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the searches we hear most often before an account is opened or a wallet is connected. We focus on the records that matter in daily use: phone verification, device sessions, cookies, payment references and requests sent through support. Where a request concerns access to garuda76, the result depends on local law and the account details available for verification.

The Privacy Policy covers account and phone-verification details, device and session signals, cookies, support messages and payment references. It explains how we use those records for access, security, transaction matching and requests, including activity connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account.

We use phone verification to connect an account request with the correct profile and to reduce unauthorised access to private records. If you ask about a payment or request a copy of account data, we may use that verified detail to check ownership before replying.

Yes. The Privacy Policy covers the transaction references and status details needed to match DANA or QRIS activity with your account. The same approach applies to OVO, GoPay, bank transfer and virtual account records. Do not send a wallet PIN when asking us to check a receipt.

Cookies can retain selected settings and help an account session work when you return through a mobile browser or desktop. You can control them through browser settings. If you restrict required cookies, login continuity or the display of account and Privacy Policy pages may change.

You can contact support from the account path and request access to, or correction of, records linked to your profile. Include the verified email or phone detail so we can identify the account. We may request an additional ownership check before releasing private account information.

We retain account and payment records for as long as needed for the purpose described in the Privacy Policy, security checks or applicable legal duties. A deletion request does not always remove transaction records immediately; support will explain which records can be removed and which must remain.

Where local law permits, you can ask about access, correction, deletion or other available rights through our support route. We assess each request against identity checks, account security and retention duties, then explain the result. Eligibility and access depends on local law and your account context.

Privacy Policy for Your garuda76 Account

Where Privacy Questions Go

Account data request

Wallet record query

Correction or deletion

What Our Privacy Process Covers

Account details

Device and session data

Cookies and settings

Payment references

Security controls

Retention and requests

Privacy Policy Answers for Indonesia

01 What does the garuda76 Privacy Policy cover?

02 Why does garuda76 need my phone verification detail?

03 Does the Privacy Policy cover DANA and QRIS records?

04 How does garuda76 use cookies on my device?

05 Can I ask for a copy or correction of my data?

06 How long does garuda76 keep account and payment data?

07 Where local law permits, can I use my data rights?

Related Pages