Reference

Privacy Policy for raja15 Accounts

Our Privacy Policy explains how raja15 handles the details you provide when opening an account, checking DANA or QRIS status, and accessing the lobby from your phone or…

Account clarityWallet recordsCookie choicesAccess requests
Explore Our Lobby Read FAQ
raja15 Privacy Policy for raja15 Accounts
CONTACT THE TEAM

Privacy Help Beside Your Account Path

A clear contact route matters when a privacy question is connected to login or wallet status. We ask you to send enough detail for us to locate the account without placing sensitive credentials in a message. Use the account support route shown in the raja15 help area, and keep a payment reference available when your question concerns DANA, OVO, GoPay, QRIS or a bank transfer. We will use the details you provide only to assess the request and respond.

Team online

Account access

For a request about phone verification, sign-in records or an unfamiliar device, use the account help route. Tell us the registered contact detail and the approximate access time, but never send your password or one-time verification code.

Wallet records

If your privacy question concerns DANA, OVO, GoPay or QRIS activity, include the transaction reference and date shown by your wallet. For bank transfer or virtual account questions, add the bank name, such as BCA, BRI, Mandiri or BNI.

Policy requests

To ask for a copy, correction or deletion assessment, describe the request plainly through our support path. We may ask for account verification before changing records, so that another person cannot act on your account.

DATA CONTROL POINTS

What Our Privacy Process Covers

This Privacy Policy applies across the account journey, including the phone check before access, wallet status checks and the device session used to reach the lobby.

Data we receive

We may receive your name or contact detail, phone verification result, sign-in activity, device and browser signals, support messages and payment references. A DANA, OVO, GoPay or QRIS reference helps us match account activity without asking you to disclose a wallet password.

Why records matter

Account data supports access and security checks, while transaction data helps us investigate a pending or mismatched status. We use the smallest practical set for the request, such as a date and reference when checking a QRIS payment.

Cookies and sessions

Our site may store session information so your account remains connected while you move from login to the lobby. Browser settings let you clear or restrict cookies; after that, you may need to verify the device again.

Account security

Phone verification and device signals help us assess account access. If you see an unfamiliar session, change your account credentials through the available account path and contact support with the time and device detail so we can assess the event.

Retention approach

We keep account, security and payment records only for the period needed for account operation, dispute checks, security assessment and applicable legal duties. When a record is no longer needed, we remove it or separate it from direct account identification where practical.

Your change request

You can ask us to access, correct or assess deletion of personal details through support. Include the account contact detail and the specific record involved. We verify the requester first, then explain any reason a record must remain.

Common Privacy Policy Searches

The questions below address the points Indonesian account holders commonly need before opening access or contacting us about a record. Each answer relates to the raja15 Privacy Policy, including wallet references, phone verification, cookies, device activity and requests concerning personal data. Where access or eligibility is discussed, it depends on local law.

The raja15 Privacy Policy covers account details, phone verification, sign-in and device activity, cookies, support messages and payment references. It explains why we use those details, how retention works and how you can contact us about access, correction or a deletion assessment.

Yes. The Privacy Policy includes references connected with DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account checks. We use a reference, date or status to investigate account activity and do not ask for your wallet password.

Phone verification helps connect the account to the contact detail you provided and reduces unauthorised access. We may use the verification result with device and session signals when assessing a sign-in. Keep one-time codes private and never send them to support.

You can contact us through the account support path and identify the detail that needs correction. We may verify your account before changing it. For a payment record, include the relevant DANA, QRIS, bank transfer or virtual account reference so we assess the right entry.

Cookies and session storage can keep your sign-in path and selected settings available while you move between account pages. You can restrict them in your browser, but clearing them may end the session or require phone verification again when you return from a mobile device.

The Privacy Policy describes a retention approach based on operational need, security checks, transaction disputes and applicable legal duties. When a record is no longer needed, we remove it or separate it from direct account identification where practical. Contact us for a request about a specific record.

Use the support route shown in your account help area and state whether you want access, correction or a deletion assessment. Provide your registered contact detail and relevant dates, but not your password or verification code. We verify the requester before discussing account records.

Related Pages

raja15 Indonesia Access guide Account information About Us raja15 Casino