Reference

rejeki bet Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open an account, why wallet records from DANA, OVO, GoPay or QRIS may be checked, and how you can…

Clear data purposesWallet record controlsAccount request path
rejeki bet rejeki bet Privacy Policy for Your Account
REQUEST SUPPORT

Privacy Questions Have A Clear Path

If a Privacy Policy question concerns your account, start from the support path shown after sign-in so we can match the request to the correct account record. Include the phone number used for access and a short description of the issue. For a wallet receipt, attach the DANA, OVO, GoPay or QRIS reference only when requested.

Team online

Account privacy request

Use the account support path to ask what personal details are held, why they are used, or which account step created a particular record.

Wallet record question

Send the payment reference through the support route when a DANA, OVO, GoPay or QRIS record appears unclear, so we can trace its status.

Data change request

Ask us to correct an account detail through the privacy contact path. We may request phone verification before changing information linked to account access.

DATA PRACTICES

What We Do With Your Account Data

A useful Privacy Policy should tell you what happens after each account action, not merely list broad principles.

Account data

We may hold your phone number, verification details and account messages to create access, confirm ownership and respond to requests tied to your account.

Device records

A mobile browser or desktop session can create device and connection records. We use them to identify unusual sign-in activity and protect the account.

Cookies

Cookies can remember session settings and help the account area load correctly. You can manage browser cookie controls, although some access steps may then need repeating.

Account security

Before discussing or changing sensitive account data, we may ask for phone verification. This helps prevent another person from taking over your account request.

Retention

We retain records only for the operational, security or legal purpose connected with them. Ask through the privacy path if you need the reason for a record.

Policy changes

When this Privacy Policy changes, we update the policy page and identify the relevant change. Contact us if you need an earlier wording for a past account action.

Privacy Policy Answers for Indonesia

These Privacy Policy answers focus on the account steps, wallet records and contact requests that matter when you use rejeki bet from Indonesia. If your situation is not listed, send the account-specific question through the support path so we can check the relevant record.

It covers account details, phone verification, device records, cookies, payment references, support messages, security use and retention. It also explains how to ask about, correct or access eligible personal data.

DANA and QRIS references can identify a wallet request or receipt connected with your account. We use those records to check status and resolve payment questions, not to collect unrelated personal details.

Yes. The Privacy Policy covers OVO and GoPay status or reference details supplied during an account request. We may need the reference to trace a wallet issue through the support path.

Contact us through the privacy request path after sign-in and describe the records you need. We may ask for phone verification before confirming ownership or sharing account-linked data.

Yes. Send a correction request through account support, identify the inaccurate detail and explain the requested change. We may verify your phone number before updating information used for account access.

On a mobile browser, cookies can keep your session and account settings available between pages. Browser controls can remove them, but you may need to complete the sign-in step again.

Yes, where local law permits. Use the privacy contact path for access, correction or retention questions, and include the account phone number so we can route the request correctly.