Reference

gajah67 Privacy Policy, Made Clear

gajah67 Privacy Policy explains which account, wallet and device details we use, why we need them, and how you can ask about them before opening an account.

Account dataWallet recordsCookie choicesContact requests
gajah67 gajah67 Privacy Policy, Made Clear
CONTACT ROUTES

Get Help With Privacy Requests

A clear contact route helps you ask about the Privacy Policy without searching through account screens. We handle questions about stored details, wallet references, cookies, access records and correction requests through the support path shown on our site. Include the account contact you used and a short description of your request, but do not send a password or wallet PIN. We may ask for an account step to confirm that the request belongs to you.

Team online

Policy questions

Use the support contact route on gajah67 to ask which account or device details relate to your Privacy Policy request. We will explain the next account step before discussing private records.

Wallet records

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, provide the date and rail name through support. We use those details to locate the relevant payment record without requesting your wallet PIN.

Access concerns

When a login or phone verification issue affects your privacy request, tell us the device path and account contact used. We can then separate an access problem from a request to change stored data.

DATA PRACTICES

How We Handle Your Policy Rights

We keep the Privacy Policy practical by connecting each data purpose to an account action you can recognise.

Account details

We use contact and verification details to create, protect and maintain your account. Before discussing a private record, we may match your request with the account contact already held on our system.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us reconcile account activity. We do not need your wallet PIN for a Privacy Policy question or receipt check.

Device records

Your browser, device type and session signals can help us identify unusual account access. These records support security checks and are not a request for the contents of your personal device.

Cookie choices

Cookies can keep a session connected while you move between account and policy pages. You can adjust cookie controls in your browser, though blocking some cookies may affect sign-in continuity.

Storage period

We retain account, support and payment references for the time needed to provide the requested service, resolve disputes or meet a legal duty. When no purpose remains, we assess the record for removal.

Change requests

You can ask us to correct, access or clarify a personal detail through the support route. Include the account contact and requested change; we may verify identity before taking action.

Privacy Policy Questions Answered

These Privacy Policy answers address the account and payment questions you may search before opening an account with gajah67. Each response points you toward the relevant record, browser setting or support step, so you can decide what to submit and how to ask for a change.

It covers account contact details, phone verification, wallet references, device and browser signals, cookies, support records and retention. It also explains how to ask for access, correction or clarification.

Phone verification helps connect an account request with the correct account contact before access. It also gives us a security step when you ask about private records or request a change.

Yes. The policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use references for status checks and reconciliation, not wallet PIN collection.

You can send a correction request through the site support route. State the account contact, identify the detail that appears wrong and describe the requested correction; we may verify ownership first.

Cookies may keep your browser session connected between account and policy pages. You can change cookie controls in your browser, although blocking some cookies may interrupt sign-in continuity.

We retain records for the service purpose, support resolution, dispute handling or legal duty that applies. We assess records when those purposes end and remove them when continued storage is not needed.

Yes. Use the support contact route and include the account contact linked to your request. We may ask for a verification step, then explain which account, wallet or device records can be addressed.