Reference

How we protect your privacy at rajajp

Your account security and data protection are built into everything we do. We collect only what we need to verify your identity, process your deposits and withdrawals through…

Account verificationPayment transparencyData retention clarity
rajajp How we protect your privacy at rajajp
REACH OUR TEAM

Privacy questions and data access requests

If you want to review your personal data, request deletion, or have privacy concerns, our support team is available to help you submit a formal request.

Live chat Open your account, go to the Help menu and select Live Chat.
Email support Send your data-access request to [email protected] with your account number and verified email.
Account settings Log in to rajajp, navigate to Settings > Privacy & Data and you can…
HOW WE HANDLE IT

Data security and your account rights

Your account login uses encryption to prevent unauthorized access. We store payment details only long enough to complete your transaction; DANA, OVO, GoPay and QRIS processes are handled by their own secure…

Encryption

All logins and payment submissions use 256-bit SSL encryption. Your password is hashed and never stored in plain text.

Payment security

DANA, OVO, GoPay and QRIS transactions are processed by their own secure payment networks. We never hold your card or wallet data.

Cookie control

Session cookies remember your login. Analytical cookies help us see how the lobby performs. You can clear cookies anytime via your browser settings.

Account recovery

If your account is compromised, contact support immediately. We verify your identity and reset your password in under two hours during business hours.

Data retention

We keep transaction records for three years for audit purposes. Personal data is deleted one year after account closure unless local law requires longer retention.

Your rights

You can request a copy of your data, correct inaccuracies, and ask us to delete records where local law permits. Email [email protected] to start the process.

Privacy policy questions answered

Players in Jakarta, Surabaya and across Indonesia often ask how their data flows once they join. Below are the questions we hear most about account privacy, payment records and data access.

Your personal information is retained for one year after closure to handle disputes, refunds and regulatory compliance. After one year, we delete your data unless local law requires us to keep records longer. You can request early deletion where local law permits by contacting our support team.

We keep transaction history for three years for accounting and audit purposes. This includes deposits via DANA, OVO, GoPay and QRIS, as well as withdrawal requests and payouts. You can view your complete transaction log anytime in your account history.

Yes. Log into rajajp, go to Settings > Privacy & Data and select Download My Data. You'll receive a file with your account details, contact information and complete transaction history within 24 hours.

We do not sell your data. We share only what's necessary with payment processors you authorize—DANA, OVO, GoPay and QRIS—to complete your transactions. We may disclose data to law enforcement where local law requires it.

Cookies are small files your browser stores to remember your login and language settings. Most are session cookies that clear when you log out. You can disable all cookies in your browser settings, though this may affect login speed. Analytical cookies help us see lobby performance; you can opt out in Settings > Privacy.

Send a data-deletion request to [email protected] with your account number and verified email. We confirm within 24 hours and process where local law permits, usually within seven working days. You can also submit requests through Settings > Privacy & Data.

No. Each time you deposit, you authorize a one-time transaction with your payment provider. We do not store your payment credentials. You can use different payment methods on each deposit, and your payment provider controls whether to link your account or treat each transaction separately.