Reference

igcplay Privacy Policy For Your Indonesia Account

Our igcplay Privacy Policy shows how account details, device signals and wallet records are handled when you use DANA, OVO, GoPay or QRIS.

Account data explainedWallet records coveredYour contact rights
igcplay igcplay Privacy Policy For Your Indonesia Account
CONTACT ROUTES

Ask About Privacy Near Your Wallet

A clear contact route helps when a privacy question appears beside a wallet receipt or login event. Send your request through the support channel shown on our site and include your account phone number only when asked. We use the account step and payment reference to locate the relevant record without asking you to post private details publicly.

Team online

Privacy request

Ask us which account or device records relate to your request. We may ask you to complete phone verification before discussing personal data connected with your igcplay account.

Wallet record

For a DANA, OVO, GoPay or QRIS question, include the payment reference and approximate date through our site support path. We use those details to trace status without exposing unrelated records.

Access concern

If sign-in or phone verification looks unfamiliar, contact support from the account help route. We can check device events and explain the next account-security step where local law permits.

HANDLING DETAILS

What Our Privacy Process Covers

We keep this policy practical: it connects the data you create during account access with the reason we need it.

Account records

We use your account details to manage sign-in, phone verification and requests made through support. Providing accurate details helps us match a privacy request to the correct account record.

Device signals

When you sign in from a mobile browser, we may record device type, browser events and security signals. These details help us identify unusual access without reading unrelated files on your phone.

Cookie controls

Cookies can remember session choices and help the account path load correctly. You can manage cookie settings in your browser, although changing them may affect sign-in and policy access.

Account security

Phone verification and sign-in checks help protect account data from an unfamiliar device. Never send a password or wallet PIN through support; use the account route shown on our site.

Record retention

We keep personal and payment-related records only for the period needed for account service, security checks, dispute handling or applicable legal duties. Retention can differ by record type.

Change requests

To request correction, deletion or a copy of personal data, contact us through the site support path. We may verify your phone and ask which records the request concerns.

Privacy Policy Answers For igcplay Accounts

These Privacy Policy answers address the searches we hear most often before account access. They cover wallet references, mobile browsing, cookie choices, retention and the checks we may use to confirm that a request belongs to you.

It covers account details, phone verification, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps us connect a privacy request or sign-in event to the correct account. We may use it before discussing account data, changing details or responding to an access concern.

Yes. The Privacy Policy covers payment status and reference details returned through DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account records used for account servicing.

You can send a correction request through the support path on our site. Tell us which account detail is wrong, and we may verify your phone before making or explaining the change.

Cookies can keep a session active and help the policy page or account path load as expected. Your browser controls them, but blocking cookies may affect sign-in and saved session settings.

Retention depends on the record and the reason it was created. We keep data for account service, security checks, dispute handling or legal duties, then remove or restrict it when no longer needed.

Use the support contact route displayed on our site and describe the account, device or wallet record involved. Do not send passwords or wallet PINs; access eligibility depends on local law.