Reference

gacoan88 Privacy Policy Made Clear

gacoan88 Privacy Policy explains what we collect when you open an account, check wallet status or enter the lobby, and why each data point is needed.

Account dataWallet recordsDevice choicesPrivacy requests
gacoan88 gacoan88 Privacy Policy Made Clear
PRIVACY HELP ROUTES

Choose a Clear Route for Privacy Help

A clear contact path helps you resolve a data question without repeating your account story. Start from the account help link when a phone verification record, login event or wallet reference looks unfamiliar. For a payment receipt connected with DANA or QRIS, include the transaction date and account contact detail, while leaving out your password or full security code. We use the details you send to locate the relevant record and respond through the available account support route.

Team online

Account help link

Use the account help path for questions about phone verification, login records, device access or a correction to the contact data attached to your account.

Wallet record request

For DANA, OVO, GoPay, QRIS or bank transfer data, share the payment date and reference so we can trace the record without requesting your password.

Privacy request

Ask us to access, correct or remove eligible personal data by naming the request clearly; we may verify account ownership before making a change.

DATA CONTROL DETAILS

Browse How We Handle Your Data

Privacy choices work best when the account path is specific, so we separate identity checks, payment references and device security events.

Data we collect

We may collect your account contact details, phone verification result, login history, device signals and payment references used to connect DANA, OVO, GoPay or QRIS activity.

Cookie choices

Cookies and similar device storage can remember a session path or security setting. You can manage browser permissions, although blocking them may interrupt account access.

Account security

We use phone verification before account access and inspect unusual login or device events. Never send us a password, one-time code or complete wallet security credential.

Retention period

We keep account, payment and security records only while needed for the stated purpose, dispute handling or applicable legal duties, then remove or restrict them.

Correction requests

If your name, phone detail or account contact data is wrong, contact us through the privacy request path. We may ask for account checks before editing the record.

Deletion requests

You may ask whether eligible personal data can be deleted. Some records may remain restricted for security, payment reconciliation or legal duties where local law permits.

Find Answers About Privacy Policy

These Privacy Policy answers focus on the questions you may have before opening an account or sending a wallet record to our support route. They explain data access, device handling, payment references and account changes in plain terms. If your request involves eligibility or a legal restriction, the answer may depend on local law and the details attached to your account.

The gacoan88 Privacy Policy covers account contact data, phone verification, login and device events, cookies, payment references and requests to access, correct or delete eligible personal data.

We use the phone verification result to confirm account access and investigate unusual login activity. It helps us protect the account path without asking you to share a password or security code.

Yes. The Privacy Policy covers payment references linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity when those details are needed to match an account transaction.

You can request a correction through the privacy contact path. Tell us which account detail is wrong, such as a phone number, and we may verify ownership before changing the record.

Use the privacy request route and state that you want access to your personal data. Include the account contact detail needed to locate the record, but do not send your password.

We may store device signals, login events and cookie settings needed for session continuity and account security. Browser controls can restrict cookies, though some account paths may then stop working.

You may ask us to delete eligible data, and we will assess the request under applicable rules. Payment reconciliation, security records or legal duties may require restricted retention where local law permits.