Reference

citrabet77 Privacy Policy for Your Account

citrabet77 Privacy Policy explains what we collect when you open an account, sign in from a mobile device, browse VIP Baccarat Circle or use a local wallet.

Account dataCookie choicesWallet checksRequest access
citrabet77 citrabet77 Privacy Policy for Your Account
REQUEST SUPPORT

Get Privacy Help Near Account Access

A clear support route matters when you cannot tell whether a message concerns your account or a wallet reference. We ask you to use the account-help path shown on the site and include the email or phone detail linked to your account, the device you used and a short description of the Privacy Policy request. For a DANA or QRIS status question, include the receipt reference rather than sending a wallet password or full banking credential.

Team online

Account data request

Use the account-help path to ask what personal data we hold or to request a copy. We may ask you to confirm the account step and contact detail already attached to citrabet77 before releasing account-related data.

Correction request

If your contact detail or account record is inaccurate, tell us which field needs changing and why. We compare the request with the signed-in account and may ask for a verification step before making the correction.

Wallet reference check

When a payment reference needs clarification, send the date, rail name and receipt code through the support path. DANA, OVO, GoPay and QRIS details help us locate the status without asking you to share a wallet password.

DATA HANDLING

What You Can Expect From Our Privacy Work

Privacy choices should be practical, not hidden behind broad wording. We explain the account data used for access, the device behaviour that helps protect a sign-in and the cookie controls available in…

Account details

We may handle the contact details and verification data you provide while opening or securing an account. This helps us match a Privacy Policy request to the correct record, including when you sign in on a phone and later continue on desktop.

Cookies and browser use

Cookies can remember a session, support page settings and help us understand whether a sign-in flow is working. You can manage cookie choices through your browser controls; changing them may affect how the account-help path behaves.

Device security

A new phone, browser or unusual sign-in pattern may create a security check before account access continues. We use those signals to protect your record, not to read private files on your device or collect unrelated content.

Payment references

For QRIS Quick Deposit, DANA or bank transfer activity, we handle the reference needed to match a status with your account. We do not need your wallet password to review whether the recorded payment step is pending or complete.

Retention choices

We assess stored details by purpose rather than keeping everything indefinitely. Account, security, support and legal needs can require different retention periods, and we remove or de-identify data when the relevant purpose has ended.

Change or removal request

You can ask us to correct, access or remove eligible personal data through the account-help route. We explain any limit that applies, verify the requester and provide the next step where local law permits the request.

Privacy Policy Answers for Your Account

These Privacy Policy answers focus on the searches we expect from someone deciding whether to open a citrabet77 account in Indonesia. They cover the data behind sign-in, mobile browsing, wallet references, cookies and personal-data requests. If your situation is not listed, use the account-help path and describe the exact record or Privacy Policy concern you want us to check.

It covers personal details linked to your account, sign-in and device signals, cookie use, support messages, payment references and requests about your data. It also explains why we use those details, how we protect them and when retention may end.

Yes, where local law permits. Send an access request through the account-help path using the contact detail attached to your account. We may verify the request first, then explain which account records can be supplied and how the response will be delivered.

Yes. We may handle a DANA, OVO, GoPay or QRIS reference so we can match a wallet action with your account and check its status. The reference is different from your wallet password, which you should never send through support.

A phone, browser change or unusual sign-in pattern can trigger a security check. The purpose is to reduce unauthorised account access and confirm that the person continuing the account step is connected to the right record, without reading unrelated device files.

Use the account-help route and identify the field that needs correction, such as a contact detail. We compare the request with the account record and may ask for verification before changing it. This process helps prevent another person from altering your data.

You may ask for removal where local law permits, but some records can remain for account security, support history or legal needs. We assess the request by purpose, explain any limit and remove or de-identify eligible data when retention is no longer needed.

Use the account-help path shown on the site and state that your request concerns the Privacy Policy. Include the account contact detail, device path if relevant and any DANA, QRIS or bank-transfer reference, while leaving out passwords and unrelated sensitive credentials.