Reference

raja700 Privacy Policy: How Your Account Data Is Handled

Our Privacy Policy explains how raja700 handles the details connected with your account, device, wallet status and lobby activity.

Account data explainedWallet records clarifiedMobile cookie choices

Explore Our Lobby Read FAQ

See Wallet Data Under Privacy Policy

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

This Privacy Policy covers data you provide when opening an account, confirming your phone, signing in, contacting support or checking a payment status. It can include your name, phone number, account credentials, selected wallet rail and records connected with DANA, OVO, GoPay, QRIS, bank transfer or

1
virtual account activity. We also receive technical details such as device type, browser settings, IP address, login time and pages opened, including Baccarat or Football Betting pages, when needed for security and service records. We use these details to provide account access, verify requests, maintain transaction
2
trails and respond to policy questions. Cookies can remember essential settings, while optional measurement cookies are handled through the available browser controls. We retain records only for operational, security or legal needs. Access to account services depends on local law, and this policy applies where local
3
law permits.

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

HELP DESK

Get Account Privacy Help Through Support

A clear support route helps when your Privacy Policy question concerns a phone check, wallet record or account detail.

Account data request Use the signed-in support path to ask what account details we hold, including your phone verification record and the account identifiers attached to your raja700 access.

Wallet record question Mention DANA, OVO, GoPay, QRIS, bank transfer or virtual account when asking about a payment record so our team can locate the relevant account entry.

Cookie assistance Tell us which mobile browser you use if cookie controls appear unclear. We can explain the available setting path without asking you to disclose your sign-in secret.

ACCOUNT SAFETY

Keep Wallet And Lobby Data Clear

We separate the data needed for account security from the activity used to keep pages working.

Data we collect

We collect account details, phone verification data, device signals, login records and selected payment rails. Pages such as Baccarat or Super Bingo may also create service activity records linked to your signed-in session.

Cookie choices

Essential cookies help maintain sign-in and policy settings on your phone. Optional cookies can support measurement, and you can manage browser permissions before continuing through the mobile lobby.

Account security

Keep your password private and complete phone verification before requesting account changes. We may ask for matching account details before discussing wallet status or releasing personal data.

Retention rules

We keep records for the period needed to operate the account, investigate security events, reconcile payment activity or meet legal duties. When a purpose ends, records are reviewed for removal or restriction.

Your requests

You can ask for a copy, correction or restriction of suitable personal data through support. Include the account phone number and request type, but never include your password or wallet PIN.

Policy contact

Our support route is the starting point for Privacy Policy questions, including cookie choices, stored account details, retention concerns and requests to change inaccurate personal data.

Privacy Policy Answers For Account Holders

These Privacy Policy answers cover the questions we expect when you check raja700 before opening an account or changing a wallet route. Read the relevant answer first, then use the signed-in support path if your request needs an account match or a record search.

It covers account details, phone verification, device and login records, cookies, payment references and requests to access or correct personal data connected with your raja700 account.

Yes. The Privacy Policy covers payment references linked with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity, but you should not send wallet PINs or passwords to support.

Phone verification helps us connect account requests to the correct account and reduce mistaken changes. We may use that record when handling access, correction, security or wallet-status questions.

Sign in, open the support area and ask for an account data copy. Include your account phone number and request details so we can complete an account protection check.

Yes. Send a correction request through support and identify the inaccurate field. We may ask for matching account details before changing phone, profile or payment-reference data.

Essential cookies support sign-in and saved policy settings. Optional measurement cookies can be managed through your mobile browser controls, and support can explain the setting route for your device.

We retain records while they serve account operation, security checks, payment reconciliation or legal duties. The Privacy Policy explains that records are reviewed when those purposes no longer apply.

raja700 Privacy Policy: How Your Account Data Is Handled

Get Account Privacy Help Through Support

Keep Wallet And Lobby Data Clear

Data we collect

Cookie choices

Account security

Retention rules

Your requests

Policy contact

Privacy Policy Answers For Account Holders

01 What does the raja700 Privacy Policy cover?

02 Does the Privacy Policy include DANA and QRIS data?

03 Why does raja700 need my phone verification record?

04 How can I request my personal data?

05 Can I ask raja700 to correct my data?

06 How does the Privacy Policy handle cookies on mobile?

07 How long does raja700 keep account records?

Related Pages