Reference

rajapoker99 Privacy Policy Explained

The rajapoker99 Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesSupport requests
rajapoker99 rajapoker99 Privacy Policy Explained
CONTACT ROUTES

Privacy Questions Reach Our Support

A clear contact trail helps us handle privacy requests without exposing your account to the wrong person. Use the support channel shown on rajapoker99 and include the phone number or email attached to your account, but never include your password or full wallet credentials. If your question concerns a DANA receipt, QRIS reference or login device, describe the issue and provide only the reference needed for us to find it. We will use the account step and security checks needed to confirm that the request comes from you.

Team online

Account access

If you cannot reach your account, contact support through the listed channel and mention the affected device, approximate login time and phone verification status. We use those details to separate a genuine access request from an unfamiliar session without asking you to reveal your password.

Wallet records

For a privacy question linked to DANA, OVO, GoPay or QRIS, send the transaction reference rather than a wallet password. Our team can match the reference with the account record, explain what was stored and direct any correction request to the right account step.

Data requests

You can ask what account or device records we hold, request a correction, or ask how a cookie is used. Include your registered contact detail and the subject of the request so we can verify ownership before discussing private account material.

HANDLING DETAILS

How We Handle Your Account Data

Privacy depends on practical controls, so we describe the account actions behind this policy. Phone verification is used before account access, wallet references are connected to the matching profile, and unfamiliar device…

Account creation

When you open an account, we collect the details needed to create your profile and complete phone verification. The verified contact helps us send account replies and identify the correct record when you ask to access, correct or remove personal data.

Mobile sessions

A mobile browser may create a session cookie, device identifier or security log when you sign in and move from the account page to the lobby. These records help keep the session connected to your account and flag unusual access patterns.

Wallet matching

DANA, OVO, GoPay and QRIS references can appear in account records when you use those rails. Bank transfer and virtual account references may also be retained so support can trace a receipt, reconcile a status or investigate a dispute.

Game activity

Our records may show the account, device and time connected with a lobby action such as opening No Commission Baccarat, Crash Countdown Round or Samarinda Lucky Slots. This helps us diagnose access issues without needing unrelated personal details.

Security checks

We may compare phone verification, login time, browser signals and wallet references when an account request looks unusual. These checks protect your records from unauthorised access, and support may ask for a limited account detail before making a change.

Changes and retention

To request a correction, ask about stored data or question a retention period, contact us through the listed support route. Tell us which record concerns you, such as a phone detail or QRIS reference, and we will explain the next verification step.

Privacy Policy Questions Answered

These Privacy Policy answers address the account and device questions you may have before opening an account with rajapoker99. We keep the scope practical: what is collected, why wallet references appear, how cookies work, how requests are verified and where local access rules apply. If your case needs a record check, use the support path rather than posting private details in a public message.

It covers account details, phone verification, login and device records, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It explains why we use each category, how long records may remain and how you can contact us.

Phone verification helps us confirm the account holder before account access and before discussing private records. It also gives support a matching contact when you request a correction or ask about a login issue. We do not need your password in a support message.

Yes. The Privacy Policy covers references connected with DANA, QRIS, OVO and GoPay, as well as bank transfer and virtual account records. We use a reference, account match and status detail to trace a receipt or resolve a wallet question without requesting secret wallet credentials.

We may use session cookies to keep your mobile or desktop sign-in connected while you move between account pages and the lobby. Security cookies or device signals can help identify unusual access. You can manage browser cookie settings, though some account functions may then require another sign-in.

Yes. Contact support through the route displayed on the site, identify the account contact detail and describe the record that needs correction. We may verify ownership before changing it. For a wallet issue, provide a limited DANA, OVO, GoPay or QRIS reference rather than a password.

We keep account, security and transaction records for as long as needed to operate access, investigate disputes, protect accounts and meet applicable legal duties. When a record is no longer needed for those purposes, we aim to remove or anonymise it, subject to required retention.

Your ability to access the account and related services depends on local law. If you are in Bandung, Surabaya or elsewhere in Indonesia and have a privacy question, use the listed support route. We will verify your account before discussing records tied to your device or wallet.