Reference

rajarungkat Privacy Policy For Your Account

The rajarungkat Privacy Policy explains what we collect when you open an account, use the lobby, or check DANA and QRIS status.

Account clarityWallet recordsCookie choicesSecurity steps
rajarungkat rajarungkat Privacy Policy For Your Account
CONTACT ROUTES

Ask About Privacy Policy Access

A clear contact route helps when you want to understand, correct, or question information linked to your account.

Account desk Use the account support path for a copy of personal data, a correction request, or a question about phone verification. We may ask you to confirm account ownership before discussing records, so another person cannot obtain details linked to your profile.
Wallet desk For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference, contact support from the cashier path. We use the transaction reference and account check to locate the relevant record without asking you to share a wallet PIN.
Security desk If a sign-in, device, or account event looks unfamiliar, send the time, device type, and account contact through support. We can review the security record, explain the next account step, and request additional verification where local law permits.
DATA PRACTICE

How We Handle Account Privacy

Privacy work is tied to practical account events rather than vague statements. We separate contact details, wallet references, device signals, and support messages so each request can be handled for its actual…

Data collection

We collect details needed for account creation, phone verification, sign-in protection, support replies, and payment reconciliation. When you open Live Blackjack Salon or another lobby area, technical session data may record the request, device, and time to keep access secure.

Cookie choices

Cookies can remember a session, support account security, and help us understand whether a page loads correctly on your device. You can manage available browser controls, although restricting essential cookies may require another sign-in before reaching the lobby.

Account security

We use phone verification and device-related security signals to reduce unauthorised account access. If your session changes while you move from mobile to desktop, the account may ask for another check before showing wallet status or personal account details.

Payment records

A payment record can contain a method label, reference, amount, status, and timing for DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity. These fields help us match a cashier event and respond when a status needs checking.

Retention period

We keep personal and transaction records for the period needed to operate the account, resolve disputes, protect against misuse, or meet an applicable legal duty. When that period ends, we delete, anonymise, or restrict the record where the process allows.

Change requests

You can ask us to access, correct, restrict, or assess removal of eligible personal data through support. Include your account contact and the exact request; we may verify ownership first, and the result depends on local law and required record duties.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account questions you are most likely to have before opening or using rajarungkat. They explain access requests, payment references, cookies, security checks, retention, and contact steps in plain language. If your situation involves a legal restriction or a record needed for a dispute, our response may depend on local law. Use the account support route when you need a case-specific answer.

The rajarungkat Privacy Policy covers data used for account creation, phone verification, sign-in security, lobby sessions, payment references, cookies, and support messages. It also explains retention and your request options. The policy applies to processing connected with your account where local law permits.

Yes. Send an access request through the account support path and identify the phone or email attached to your profile. We may verify ownership before releasing details. The response can include eligible account, device, support, and payment-reference records, subject to local law.

Our Privacy Policy covers the payment references needed to match DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity. We may record method, reference, status, amount, and time. We do not need your wallet PIN for a support status check.

Contact support with the field that needs correction and the account contact used for phone verification. We may ask for an ownership check before changing it. If the record is tied to a transaction or legal duty, we explain any restriction under the applicable local rule.

Yes. The Privacy Policy describes cookies used for sessions, security, and page performance. Browser controls can restrict optional cookies, while essential settings may be needed to keep your account signed in. If a device change causes another check, complete phone verification before access.

We retain personal, security, support, and payment-reference records for the period needed for account operation, dispute handling, security work, or an applicable legal duty. After that period, we delete, anonymise, or restrict records where possible. Exact handling depends on local law.

Use the account support route and state whether you need access, correction, restriction, deletion assessment, or an explanation of a security or wallet record. Include your account contact and relevant reference. We may verify ownership before responding to a Privacy Policy request.