Reference

Open the raja 404 Privacy Policy

raja 404 Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity in Indonesia.

Account dataWallet recordsDevice controlsCookie choices
Explore Our Lobby Read FAQ
raja 404 Open the raja 404 Privacy Policy
CONTACT ROUTES

Find help for a Privacy Policy request

A clear contact route helps you ask what we hold, why we use it or how to correct an account detail. When your request concerns Privacy Policy, include the account contact used for access and the subject of your request so we can locate the relevant record without asking you to send wallet credentials. We can also use the account support path when a receipt, phone check or wallet reference needs to be connected to the right account.

Team online

Account privacy request

Send your Privacy Policy question through the support path connected with your account. Tell us whether you need access, correction or deletion help, and include the contact detail already attached to the account. Do not send your password, wallet PIN or full payment credentials.

Wallet record check

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, give us the date, rail name and transaction reference. We use those details to check the payment record while keeping the wallet password and one-time verification code out of the request.

Access concern

If your phone verification or account access changes unexpectedly, contact us through the same account support route before opening another account. That lets us compare the sign-in record, device event and requested change without mixing two separate identity trails.

DATA PRACTICE

Explore the controls behind this policy

Privacy Policy is practical at the account level: we separate sign-in details, payment references and device events so each request can be checked against the right record.

Account details

We use the contact details and phone verification step attached to your account to support sign-in, confirm requested changes and…

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us trace payment status without needing your wallet…

Device events

When you sign in from a mobile browser or desktop, we may record device and connection events used to spot…

Cookie choices

Cookies can help keep an account session active, remember a preference and measure which policy page path was opened.

Retention timing

We retain account, payment and security records only for the period needed for the purpose that created them, or where…

Policy changes

When we change this Privacy Policy, we place the revised wording on this page and update its effective context.

Browse Privacy Policy answers first

These Privacy Policy answers focus on the account, wallet and device questions that matter before you open access. If your situation is specific, use the account support path and identify the record you want us to check. Access and eligibility depends on local law, including where local rules restrict a requested account action.

The raja 404 Privacy Policy covers account details, phone verification, sign-in events, device data, cookies and payment references. It also explains how we use these records for account access, wallet reconciliation, security checks, policy requests and retention where local law permits.

Phone verification helps connect an account access request or account change with the correct record. We use its status for sign-in protection and support checks, not as a reason to request your phone passcode. Keep the contact detail current if you need a correction.

Yes. The Privacy Policy covers payment references from DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use a reference, date and account match to check status or a receipt. We do not need your wallet password or one-time code.

Use the account support path and ask for a Privacy Policy access request. Include the contact detail attached to your account and describe the records you want checked, such as sign-in, device or payment references. We may need to confirm account ownership before responding.

You can request a correction when an account detail, phone verification status or payment reference is inaccurate. Send the request through account support with the affected field and a clear replacement. We check the account context first so one account is not changed by mistake.

Ask through the account support path and state that your request concerns deletion under the Privacy Policy. We assess the request against active account needs, payment reconciliation and legal duties. Where local law permits, we remove or anonymise records that no longer need retention.

Yes. The policy applies when you use a mobile browser or desktop browser to sign in, view account settings or open the lobby. Device events and cookies may support session security. You can adjust cookie controls in your browser, subject to sign-in functions that need them.

Related Pages

raja 404 Indonesia Account information raja 404 Casino Liga 1 Mix Parlay FAQ