Reference

rajaking Privacy Policy for Your Account

Our Privacy Policy shows how rajaking handles the details linked to your account, device and payment records before you open Baccarat from Semarang or elsewhere in Indonesia.

Account dataWallet recordsDevice choicesPrivacy requests

Browse Our Lobby Read FAQ

What Our Policy Covers in Indonesia

rajaking Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy applies when you create, access or maintain a rajaking account through a phone or desktop browser. We may handle contact details, phone verification results, login events, device identifiers, browser settings, support messages and payment references needed to match an account activity with DANA,

1
OVO, GoPay, QRIS, bank transfer or virtual account records. We use these details to provide account access, check unusual login behaviour, reconcile a payment status and respond to a privacy request. We do not need your wallet PIN or bank password for these checks. Access and
2
eligibility depends on local law, and this policy does not change any local requirement. If you use a BCA, BRI, Mandiri or BNI transfer route, the bank reference may remain visible in transaction records even when the full account credential is never shared with us.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP WITH RECORDS

Three Ways to Ask About Privacy

A clear support path helps when a login record, wallet reference or account detail needs attention.

SIX DATA CONTROLS

Six Controls Behind Your Data

Our handling process is designed around the account steps you actually take: phone verification, browser login, wallet selection and support contact.

Collection

We collect details you enter during account creation, plus phone verification results, login events and browser data generated when you access the lobby from a mobile phone or desktop.

Payment separation

DANA, OVO, GoPay, QRIS and bank transfer references help us match payment status. We do not ask for wallet PINs, online banking passwords or full authentication secrets.

Cookie purpose

Cookies can keep your session active, remember essential settings and help us identify repeated login issues. Your browser controls can limit cookies, although some account functions may then need another check.

Device security

We may record device type, browser signals and access time to spot an unusual sign-in. If a device path changes unexpectedly, we can request phone verification before account details are shown.

Retention

We keep account, payment-reference and support records only for as long as needed for the stated account, security, dispute or legal purpose, then assess them for removal or restriction.

Your request

Ask our support route for a copy, correction or clarification of your data. Include your account phone detail and the specific record; we verify the request before making any change.

Privacy Policy Questions You May Search

These Privacy Policy answers cover the account and payment questions we hear most often from Indonesia. If your situation is not listed, use the support path with the relevant phone verification or payment reference. We will first confirm that you control the account, then address the specific data record where local law permits.

The rajaking Privacy Policy covers account details, phone verification, login and device events, cookies, support messages, payment references and the process for requesting access or correction.

No. Our Privacy Policy distinguishes payment references from secret credentials. We may retain a DANA or QRIS transaction reference for status checks, but you should never send us a wallet PIN.

Phone verification links an account request to the correct account holder and helps us protect personal data during access or support requests. It may also be required when device activity changes.

Yes, where local law permits. Contact support with the phone-linked account detail and specify the records you want, such as login history, wallet references or support messages. We verify ownership first.

Send a correction request through the account support path and identify the inaccurate field. We may request account checks, compare the record with your submitted details and explain the result.

Our Privacy Policy covers cookies used for session continuity, essential settings and login troubleshooting. You can adjust cookie controls in your mobile browser, but restricted cookies may trigger another account check.

Yes. Access and eligibility depends on local law. A request may require identity checks, limited disclosure or a different response when a local legal obligation affects the requested account record.

rajaking Privacy Policy for Your Account

Three Ways to Ask About Privacy

Six Controls Behind Your Data

Collection

Payment separation

Cookie purpose

Device security

Retention

Your request

Privacy Policy Questions You May Search

01 What does the rajaking Privacy Policy cover?

02 Does the Privacy Policy store my DANA or QRIS PIN?

03 Why does rajaking need phone verification?

04 Can I ask for a copy of my account data?

05 How can I correct an inaccurate Privacy Policy record?

06 How are cookies handled on my mobile device?

07 Does local law affect account data access?

Related Pages