Reference

Privacy Policy For Your Account Data

citrabet77 Privacy Policy explains how we handle your account details, wallet records and device activity when you use our Indonesia service.

ACCOUNT RECORDSWALLET ACTIVITYCOOKIE CHOICESDATA REQUESTS
citrabet77 Privacy Policy For Your Account Data
REQUEST HELP

Get Help With A Privacy Request

A clear support path helps you ask what we hold, why a record appears, or how to correct an account detail.

Account data question Use the account help route to ask which profile details we hold or why phone verification is showing on your record. Include your registered contact detail so we can distinguish your request from another account without requesting your password.
Wallet record query For a DANA, OVO, GoPay or QRIS record, send the payment reference and approximate date through the cashier support path. We can then trace the matching account entry while keeping your wallet PIN, one-time code and full login secret out of the request.
Correction request If your name, phone detail or contact address needs changing, ask through account support after signing in. We may request a verification step before editing the record, which helps prevent another person from changing your profile or redirecting account messages.
HANDLING YOUR RECORD

What We Do With Your Privacy Choices

We keep this Privacy Policy practical by linking each data category to a clear account task. Login and phone verification records help protect access; payment references help reconcile cashier activity; cookie signals…

Account details

We use contact and verification details to create your account, confirm that the person requesting access matches the profile, and send account-related messages. You can ask us to correct an inaccurate phone number or contact address through the signed-in support route.

Cookie settings

Cookies can remember session choices, language settings and security signals on the device you use. If you clear cookies, some account steps may ask you to sign in again. Your browser controls provide a direct way to remove or restrict these files.

Login protection

We review sign-in time, device signals and unusual access patterns to protect your profile. Never send us a password or one-time code in a support message. If a login looks unfamiliar, use the account help path and tell us when you noticed it.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can be stored beside the related account entry. This lets us check a receipt or cashier status without needing your wallet PIN, full card secret or unrelated account content.

Retention choices

We keep account, security and payment records for as long as an operating need or legal duty requires, then remove or separate them according to our handling process. You can ask which category relates to your request and why it remains on record.

Changes and access

To request a copy, correction or removal assessment, contact support from the account route and identify the record involved. We may verify ownership before acting, and availability of any request depends on local law and the duties that apply to the account.

Privacy Policy Answers For citrabet77

These Privacy Policy answers address the searches we hear most often from Indonesian account holders. They explain what may be recorded during sign-in, phone verification and wallet reconciliation, along with the practical route for asking about access, correction or removal. For a request tied to an individual account, use the support path after signing in.

It covers account details, phone verification, login and device signals, cookies, support messages, and payment references linked with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains how we use, retain and handle requests about those records.

Phone verification helps us connect the person requesting account access with the correct profile and reduce unauthorised entry. The verification result becomes an account-security record. Do not send the code to support; use the signed-in account route if access appears unusual.

Yes. The Privacy Policy covers payment references and status details connected with QRIS and DANA, as well as OVO, GoPay, bank transfer and virtual account routes. We use these records to match receipts and investigate cashier status, not to request your wallet PIN.

Sign in and use the account support path, then state which detail is wrong, such as a phone number or contact address. Include the registered contact detail so we can locate the profile. We may complete an ownership check before making any change.

You can send an access request through the support route linked to your account. Explain whether you mean profile details, login records, cookies, payment references or support messages. We may verify your identity first, and the response depends on local law and applicable duties.

Retention depends on the purpose of the record, such as account security, payment reconciliation, support handling or a legal duty. We do not promise one period for every category. Ask through support which record you mean and why it is still being retained.

Use the support route inside your account and describe the Privacy Policy concern in plain English. For a wallet matter, add the payment reference and date; for a login matter, add the approximate time and device. Never include your password or one-time code.