Reference

gelora188 Privacy Policy for Your Account

Our Privacy Policy explains how gelora188 handles the details you provide when opening an account, signing in from a phone, or checking DANA and QRIS payment status.

Account dataCookie choicesWallet recordsSecurity requests
gelora188 gelora188 Privacy Policy for Your Account
CONTACT THE POLICY TEAM

Ask About Privacy Through Your Account Path

A clear contact path helps you ask what we hold, why we use it, or how to correct an account detail. Start from your signed-in account and include the email or phone linked to your profile so we can confirm the request belongs to you. If login is unavailable, use the support contact route and provide a payment reference without sending a password or wallet PIN.

Team online

Data access request

Ask us for the account details associated with your verified phone or email. We may request an account step before responding, so private records are not released to the wrong person.

Correction request

Tell us which profile detail needs changing and why. We compare the request with your account record, then explain the next step if a phone verification check is required.

Wallet record question

For a DANA, OVO, GoPay or QRIS query, include the transaction reference and date. Do not send your PIN, password or complete wallet credentials through a support message.

HOW DATA IS HANDLED

Explore How gelora188 Protects Policy Details

We keep this Privacy Policy practical by linking each data use to an account action you recognise: access, verification, payment matching, security or support.

Account collection

We collect details you enter during account creation and phone verification, plus records created when you sign in. This lets us connect a request to the correct profile without relying on a display name alone.

Cookie controls

Cookies and similar browser data can keep a session active and help us understand basic access errors. You can adjust browser cookie settings, although blocking them may interrupt sign-in or policy access.

Device signals

We may record device type, browser version, session time and related security signals. These details help us spot unfamiliar account access when you move from a mobile browser to a desktop.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can be stored beside the related account action. We use that link to check status rather than requesting your wallet PIN.

Retention choices

We retain records only for the stated operating, security, support or legal purpose. When a request concerns deletion or reduced use, we explain what can change and what must remain for an applicable duty.

Security contact

Send privacy questions through the account support path and identify the affected record. We may verify your phone or email before making changes, and we will not ask for your password.

Browse Privacy Policy Answers for gelora188

These Privacy Policy answers cover the account steps Indonesian customers ask about most often, including phone verification, cookies, device access and wallet references. If your situation is not listed, contact us through the support path with the smallest useful set of details. Access remains subject to local requirements, and where local law permits we will explain the available request route.

It covers account details, phone verification, login and device signals, cookies, support messages, payment references and retention. It also explains why we use each category and how to ask about your records.

DANA and QRIS references can appear when a payment is matched to your account. We use the reference, amount and status needed for checking, while your wallet PIN remains private.

We use your phone number for account identification, verification and access-related support. If you request a profile change, we may confirm control of that number before updating the account record.

Yes. Contact us through the signed-in support path and describe the account record you want to access. We may verify your email or phone first, then explain the available response.

Yes. The policy covers data created when you sign in through a mobile browser, including device and session signals. Changing to desktop does not create a separate policy for the same account.

Send a correction request through support, name the affected field and provide the account contact linked to it. We may ask for phone verification before changing a record.

Retention depends on the reason for keeping a record, such as account operation, security, support or a legal duty. Ask us about a specific record and we will explain the applicable retention position.