Reference

Privacy Policy for Your citaru88 Account

citaru88 Privacy Policy explains what we collect when you open an account, sign in, use DANA, OVO, GoPay or QRIS, and contact our support team.

Account recordsWallet activityCookie choicesSupport requests
citaru88 Privacy Policy for Your citaru88 Account
CONTACT YOUR WAY

Get Privacy Help Near Account Support

A clear contact route matters when you want to check, correct or remove account data. We keep privacy requests close to the same account and cashier support path used for login or wallet status concerns. Tell us which account step you mean, such as phone verification, a QRIS receipt or a device sign-in, and we can locate the relevant record more accurately. For access in Indonesia, our service remains where local law permits.

Team online

Account support

Send a request through the support path connected with your account when you need a copy, correction or explanation of data used for phone verification. Include your registered phone number and the specific account step, but never send your password or wallet PIN.

Cashier records

If your request concerns DANA, OVO, GoPay or QRIS, mention the payment rail and receipt reference. We use that detail to separate a cashier record from a login record and to check the status without asking for your wallet password.

Device access

When a phone or desktop sign-in raises a privacy question, describe the device path and approximate time. We may ask for account verification before discussing records, helping us avoid disclosing account data to the wrong person.

DATA HANDLING

What We Do With Account Data

Privacy choices are tied to practical account operations: signing in, checking a wallet status, opening a lobby page and receiving support.

Account data

We may hold your name, phone number, account identifiers, verification result, sign-in history and support messages. These records help us return you to the correct account and answer a request about a particular login or cashier event.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account action can create a reference, amount, status and time record. We use these details to reconcile account activity; wallet passwords and PINs should stay with your payment provider.

Cookies

Cookies and related storage can keep a session open, remember a device preference and support security checks. If you block them, sign-in or page settings may need to be repeated, while account records already held remain subject to this policy.

Security checks

We use phone verification, sign-in signals and account review steps to reduce mistaken access. If a request involves sensitive records, we may ask you to confirm account details before changing contact data or discussing a payment reference.

Retention periods

We keep records for the period needed to operate your account, resolve a payment question, investigate security events or meet a legal obligation. When a record is no longer needed for those purposes, our handling process moves it toward removal or de-identification.

Your requests

You can ask what account data we hold, request a correction, ask about processing or raise a deletion question. Send the request through account support with enough detail to locate it, and we may verify your identity before responding.

Privacy Policy Answers for citaru88

The questions below cover the account and payment situations that most often lead to a Privacy Policy request. Each answer points you toward a practical next step, whether you are checking a cookie setting, asking about a QRIS reference or seeking access to records linked with your phone verification. If local eligibility is relevant, access depends on local law.

It covers account details, phone verification, sign-in records, device signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. It also explains retention, security handling and ways to request access or correction.

Phone verification helps connect account access to the correct person and supports checks when login details or a device change looks unusual. We may use the verification result for account security, but you should not send your password, wallet PIN or one-time code in a support message.

When you use DANA or QRIS, we may retain the payment reference, status, time and account link needed to reconcile the cashier action. We do not need your wallet password. For a record question, provide the rail and receipt reference through account support.

Yes. Send a request through the account support path and state that you want to access records connected with your account. Include your registered phone number and the date or account step concerned. We may verify your identity before releasing account data.

Contact account support with the field that needs correction and the accurate replacement detail. A request involving your phone number, verification result or payment record may require an identity check. We will assess the change against account security and any applicable legal duty.

We retain records while they are needed for account operation, payment reconciliation, security review, dispute handling or a legal obligation. The period can differ by record type. When the purpose ends and no duty requires retention, the record moves toward removal or de-identification.

Yes. The policy applies when you reach the service from a phone, tablet or desktop. Device signals and cookies may support sign-in continuity and security checks, so blocking storage can require another login. Service access in Indonesia depends on local law.