Reference

gelora188 Privacy Policy for You

Your account, device and wallet details have a clear place in the gelora188 Privacy Policy.

Account clarityWallet contextDevice choicesPrivacy contact
gelora188 gelora188 Privacy Policy for You
PRIVACY HELP PATH

Where To Ask About Your Data

A direct support route helps you resolve a Privacy Policy question without explaining your concern to several teams. From your account support area, tell us whether the request concerns sign-in data, a wallet reference, a device record, a cookie choice or a correction. Include the phone number linked to the account and the relevant date where possible. We will use those details to locate the request while limiting unnecessary disclosure.

Team online

Account request

Use the account support path for a copy request, correction, deletion question or concern about phone verification. We may ask you to confirm account ownership before discussing personal data, so your request is not exposed through an unverified message.

Wallet query

For DANA, OVO, GoPay or QRIS references, include the payment date and account identifier rather than a wallet password or full private credential. We can check the status record and explain which payment data is held for that transaction.

Device concern

If a browser or phone appears in your access history unexpectedly, contact support from the account path and describe the device, sign-in time and action you recognise. We can review the related security record and advise on the next account step.

DATA CONTROL

What We Do With Privacy Requests

We keep this policy practical by linking each privacy choice to an account action you can recognise.

Data handling

We use account identifiers, phone verification status, device signals, support messages and payment references for the stated account, security and service purposes. We avoid asking for wallet passwords, and we use only the request details needed to locate your record.

Cookie choices

Browser storage can keep a session active or remember a language and display preference. You can clear site data through your browser settings; doing so may sign you out and require phone verification again before account access continues.

Account security

Phone verification, sign-in records and device signals help us identify unusual access. If your phone or browser changes, we may request an account check before discussing private records, especially when a request concerns wallet activity.

Record retention

We retain records for the period needed for the stated purpose, account support, security checks or a legal requirement. When a record no longer needs to remain, our handling process moves it toward deletion or removes its direct account link.

Correction requests

You can ask us to correct inaccurate account details by using the support path and identifying the field that needs changing. We may compare the request with phone verification or account records before applying an update.

Request identity

Privacy requests must come from the account holder or an authorised person. We may ask for a phone verification step, the account identifier and a clear request type so we can protect your data while processing the response.

Privacy Policy Questions Before Access

These Privacy Policy answers focus on the account actions you are most likely to take before opening or continuing an Indonesia account. They cover wallet references, mobile access, cookies, corrections and requests for copies or deletion. If your situation is not listed, use the privacy support path with your account identifier.

The gelora188 Privacy Policy covers account details, phone verification, sign-in and device records, browser storage, support messages and payment references. It explains why we use each category, how retention works, and how you can request access, correction or deletion where local law permits.

No. When you use DANA or QRIS, we may hold a payment status and reference so we can match the transaction to your account. We do not need your wallet password for that purpose. Never include a private wallet credential in a support request.

Phone verification helps us connect a privacy request or sign-in event to the correct account. It can also help us identify unusual device access before we discuss account records. The verification step is part of protecting your data, not a request for your wallet password.

Use the account support path and ask for a copy of your personal data. Include your account identifier, linked phone number and the categories you want checked, such as device records or wallet references. We may verify ownership before preparing a response where local law permits.

Yes. Send a correction request through the privacy support path and name the inaccurate field, such as a phone detail or account identifier. We may compare your request with the account record and phone verification before changing the relevant data.

Cookies and browser storage may retain a session, language choice or display setting. Clearing them through your browser can sign you out and remove remembered preferences. The Privacy Policy explains these uses, while your browser controls whether stored site data remains on your device.

You can ask about deletion through the support path and identify the account records involved. We assess the request against account security, payment reconciliation and legal retention needs. Where local law permits, data no longer needed for those purposes can move toward deletion.