Reference

jeruk bet Privacy Policy For Your Account

The jeruk bet Privacy Policy explains what we collect when you open an account, check Speed Baccarat or manage DANA and QRIS activity, and how we use each…

Account dataWallet recordsCookie choicesSecurity requests
jeruk bet jeruk bet Privacy Policy For Your Account
CONTACT ROUTES

Get Privacy Help Beside Account Support

A clear contact path helps you ask about the Privacy Policy without sending sensitive details to the wrong place. Start with our support chat when you need a copy request, correction, deletion question or explanation of a wallet record. We may ask you to confirm the account email or phone route before discussing personal data. For someone in Bandung or elsewhere in Indonesia, the same account support path applies where local law permits.

Team online

Account data request

Use support chat to ask what personal data is linked to your account. We may confirm your email or phone details first, then explain the available access route under the Privacy Policy and local rules.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference appears unfamiliar, send the receipt reference through the account support path. We check the relevant record without asking you to post wallet credentials in an open message.

Security concern

Tell us through support chat if your login session or device access looks unusual. We can direct you through account verification and explain which security records may be retained for the Privacy Policy process.

DATA HANDLING

See How jeruk bet Handles Privacy

We handle privacy through ordinary account controls rather than vague promises. Sign-in activity, wallet references and device signals help us protect your account and investigate a disputed record.

Account collection

When you create an account, we collect the details needed to identify the account and provide access. A clear phone verification step may be required before account access, helping us connect requests to the correct account holder.

Cookie controls

Cookies and similar browser signals can keep a session open, remember selected settings and help us detect unusual sign-in patterns. You can adjust browser cookie controls, though some account pages may not work as intended afterward.

Device sessions

We may record device type, browser details and sign-in time when you move from a mobile login to the lobby. These signals help identify a session linked to Speed Baccarat or wallet activity without storing your device contents.

Wallet protection

Payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account can be used to match a receipt with the correct account. We do not need your wallet password or one-time security code for that check.

Retention choices

We retain account, support and transaction-related records for as long as they serve account operation, security, dispute handling or legal requirements. When a record no longer has a valid purpose, our process assesses removal or further restriction.

Change requests

You can contact support to request access, correction or removal of personal data connected with your account. Include the account route and a short description; we may verify ownership before making a change or sharing records.

Find Answers About Privacy Policy

These Privacy Policy answers address the account questions we hear most often from Indonesian customers. They explain what happens around sign-in, local wallet references, cookies, device records and requests sent to support. If your situation is different, contact us through the account support route and describe the record you want us to check. Access depends on local law, including the handling of requests from a particular location.

It covers account details, phone verification, browser cookies, device session signals, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains why we use, retain and protect those records.

Phone verification helps us connect an account request to the correct person and reduce mistaken or unauthorised access. The verification result can become part of the account security record. We do not ask you to send a one-time code through public support messages.

Yes. The Privacy Policy covers payment references and status details that help us match DANA or QRIS activity with your account. It can also cover OVO, GoPay, bank transfer and virtual account references, while wallet passwords and security codes remain private to you.

You can contact support chat with the email or phone route connected to your account and ask for an access request. We may verify ownership before responding. The records we can provide, and the timing or form of the response, depend on local law.

Send support chat a clear request naming the account record that needs correction or removal. We check the request, confirm account ownership and assess whether the record must remain for security, dispute handling or legal reasons. Where local law permits, we explain the result.

Cookies or similar browser signals may support sign-in sessions, saved settings and security checks when you use a phone browser. They do not give us access to your device contents. You can change browser settings, although some Privacy Policy and account functions may be affected.

We keep personal data while it supports account operation, security, payment reconciliation, support handling or a legal requirement. Retention is assessed by record type and purpose rather than kept without reason. You can ask support how a particular account or wallet record is handled.