Reference

gacorr33 Privacy Policy For Your Account

The gacorr33 Privacy Policy explains how we collect, use and protect the details connected with your account, including login records, device signals and wallet activity.

Account dataCookie choicesWallet recordsSecurity steps
gacorr33 gacorr33 Privacy Policy For Your Account
PRIVACY SUPPORT

Open Support When Account Data Needs Attention

A clear contact path helps when your account record, wallet status or privacy request needs checking.

Account request Open your account help area, select the privacy request path and describe the correction or access question. We may ask for account details to confirm that the request comes from you.
Payment record For DANA, OVO, GoPay or QRIS records, include the payment reference and date. We use those details to locate the status without asking you to share a wallet password or private security code.
Access concern If a login or device event looks unfamiliar, tell us through the account support route. We can review the recorded access signals and guide you through the account security steps available to you.
DATA HANDLING

Explore How We Handle Your Privacy Choices

Privacy controls work best when each record has a clear purpose. We separate account identification, payment references, device security events and cookie preferences so a request can be handled with the right…

Account details

We use your phone number and verification details to create and protect your account. We do not ask you to place wallet passwords in support messages, and we use account checks before discussing private records.

Cookie settings

Cookies and similar browser storage can remember session state, security preferences and language choices. You can review available browser controls, although switching them off may require another login or affect account access.

Device signals

When you sign in from a mobile browser or desktop, we may record device type, browser details and access time. These signals help identify unusual sessions and are not a substitute for your account credentials.

Wallet records

DANA, OVO, GoPay and QRIS references can show a payment amount, status, time and transaction identifier. We use these fields to reconcile your account activity without storing a wallet password.

Record retention

We retain personal records only as long as needed for the purpose described here, account protection, dispute handling or a legal duty. After that period, records are deleted or reduced to non-identifying forms.

Change requests

To request access, correction or removal, use the privacy path in account support. Tell us which record concerns you, and we may verify account ownership before making a change.

Browse Answers About Privacy Policy

These Privacy Policy answers cover the questions we expect before account creation or a wallet connection. They explain what we collect, why we use it and how you can ask us to check a record. If your situation is not covered, use the account support route with the smallest amount of personal detail needed.

It covers account details, verification records, cookies, device signals, payment references and support requests. It also explains how we use, retain, protect and correct those records for your account.

Yes. The Privacy Policy includes DANA and QRIS references such as status, time and transaction identifiers. It also covers related OVO, GoPay, bank transfer and virtual account records.

We record device type, browser details and login timing to protect account access and identify unusual sessions. These signals help our checks without replacing your password or verification step.

Use the privacy request path inside account support and state which records you want to access. We may verify account ownership before searching or sending details connected with your account.

Yes. Send a correction request through account support, identify the field that is wrong and provide the updated detail. We may ask for verification before changing a protected account record.

We keep records for the period needed for their stated purpose, account security, dispute handling or a legal duty. When that need ends, we delete or de-identify the records.

Yes. Access and eligibility depends on local law. A privacy request does not change those rules, and we may limit or adjust a response when a legal requirement applies.