Reference

Privacy Policy for gajah55 Accounts

Our Privacy Policy explains how gajah55 handles the details you provide when opening an account, signing in, using the lobby or checking a wallet status.

Account dataWallet referencesCookie choicesContact route

Explore Our Lobby Read FAQ

How Local Payment Data Is Used

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

This Privacy Policy applies when you create or use a gajah55 account from Indonesia, where local law permits. We collect details needed to open the account, confirm your phone, protect sign-in activity and match a transaction to the correct account. A DANA, OVO, GoPay or QRIS

1
reference can appear in our payment records, while bank transfer and virtual account records may include a bank name such as BCA, BRI, Mandiri or BNI. We use those references to check status, investigate an unmatched receipt and complete account support; we do not use them
2
as a reason to send unrelated messages. Your device type, browser path and cookie choices may also be recorded to keep the account session working. If you are in Makassar or elsewhere in Indonesia, access still depends on local law. The full policy applies to the
3
account information you submit and the activity needed to maintain account security.

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

ACCOUNT HELP

Where To Ask About Your Data

A clear support path helps you act on this Privacy Policy without searching through unrelated pages. Sign in when possible and use the account help route linked near your wallet status.

Account access Use the account help route when phone verification or sign-in blocks a Privacy Policy request. We can identify the account path without asking you to share a password or one-time code.

Wallet status For a DANA, OVO, GoPay or QRIS record, send the transaction reference and date through support. We use those details to locate the payment entry and avoid requesting unnecessary wallet data.

Data request Ask us to explain, correct or remove eligible account details through the same support route. We may confirm ownership before changing records connected with your gajah55 account.

DATA PRACTICE

Six Data Practices Behind Our Policy

We keep this policy practical by linking each data use to an account action you can recognise. Phone verification supports account access, device signals help identify unusual sessions, and payment references help…

Account details

We use your submitted account details to create the profile, support phone verification and respond to requests about the same account. Required fields are limited to the account process.

Device signals

Browser type, device path and session activity may be recorded to protect sign-in. These signals help us investigate unusual access without treating your device as a permanent identity.

Cookie controls

Cookies help remember a session and selected settings. You can manage cookies through your browser controls, although turning them off may affect sign-in or movement between account pages.

Wallet records

DANA, OVO, GoPay and QRIS references are used to match status checks and receipts. Bank transfer or virtual account details are handled for the same account-led payment purpose.

Security checks

Before changing account details or disclosing account records, we may ask for a phone verification step. Never send your password, one-time code or complete wallet credentials to support.

Retention requests

We keep records only as long as needed for the stated account, security or legal purpose. Contact support to ask what can be corrected, exported or removed from your account record.

Privacy Policy Questions for gajah55

These Privacy Policy answers cover the account and payment questions you are most likely to ask before opening or using a gajah55 account. Each answer points you toward a practical step, including phone verification, cookie settings and the support route for data requests.

It covers account details, phone verification, device and session signals, cookies, payment references and support requests connected with your gajah55 account in Indonesia.

We may store transaction references and status details for DANA, OVO, GoPay or QRIS. These records help match receipts and investigate payment questions, rather than collect unrelated wallet content.

Yes. Contact us through the account help route, describe the correction and complete an ownership check if requested. We will explain any record that must remain for security or legal reasons.

Cookies can keep your session and selected settings available between account pages. You can adjust them in your browser, but some sign-in functions may not work correctly after cookies are disabled.

We retain data only for the account, security or legal purpose for which it is needed. The support route can explain the status of a particular record and whether removal is available.

Ask through account support for a data access request. We may confirm your phone or account ownership first, then identify the records available for access under local requirements.

Yes. Account access and eligibility depend on local law. If you need clarification about a data request from Indonesia, contact support through the account help route before submitting private documents.

Privacy Policy for gajah55 Accounts

Where To Ask About Your Data

Six Data Practices Behind Our Policy

Account details

Device signals

Cookie controls

Wallet records

Security checks

Retention requests

Privacy Policy Questions for gajah55

01 What does the gajah55 Privacy Policy cover?

02 Does the Privacy Policy store my DANA or QRIS details?

03 Can I ask gajah55 to correct my account data?

04 How does the Privacy Policy handle cookies?

05 How long does gajah55 keep personal data?

06 Can I access my data under this Privacy Policy?

07 Does eligibility for gajah55 depend on local law?

Related Pages