Reference

Privacy Policy for Your rajawd777 Account

Our Privacy Policy explains how we handle the details you provide when opening an account, checking wallet status or entering the lobby from an Indonesian phone or desktop.

Account dataWallet recordsCookie choicesAccess requests
rajawd777 Privacy Policy for Your rajawd777 Account
HELP WITH DATA

How to Ask About Your Privacy Policy

A clear contact path helps you resolve a privacy question without repeating your account story across several channels. Start from the support route beside the cashier or use the account-help path when login, phone verification or wallet status is involved. Include the email or phone linked to your account, the request you are making and any relevant reference, but do not send a password or full wallet credentials. We may ask for an account step to confirm that the request comes from you.

Team online

Account access

If you cannot sign in or complete phone verification, use the account-help path beside the cashier. We check the account reference and device details needed to locate your record, while asking you not to send a password, one-time code or complete DANA, OVO or GoPay credentials.

Payment records

For a QRIS, bank transfer or virtual account question, send the payment reference and approximate time through support. We use that reference to check the stored status without requesting your full bank login. E-Wallet Deposit Help may also point you to the relevant wallet record.

Privacy requests

For a copy, correction, restriction or eligible deletion request, state the exact action you want and the email or phone attached to your account. We may verify ownership before changing data, and we explain where a legal or security record must remain stored.

DATA HANDLING

Six Practical Privacy Controls We Use

Privacy protection works through ordinary account steps rather than a promise that data never exists. We separate access credentials from payment references, limit internal access to operational needs and use device signals…

Account collection

We collect details needed for account creation, such as contact information and phone verification status. The account step helps us connect your sign-in with the correct profile, while optional details should not be added unless they serve a clear account or support purpose.

Payment references

A DANA, OVO, GoPay or QRIS transaction can create a reference, amount, time and status record. Bank transfer and virtual account checks may add the relevant bank or reference detail. We use these records to reconcile an account action, not to request your banking password.

Cookies and devices

Cookies can remember a session, language choice or privacy selection on the browser you use. Clearing them may sign you out or ask for consent again. Your phone and desktop can therefore show separate settings until you update each device path.

Account security

Phone verification and sign-in checks help us confirm account access. We may review device or session signals when activity looks unusual. Never share a password or one-time code with support; a request for those details is not part of our privacy process.

Retention choices

We keep account, support and payment records for the period needed to operate the service, investigate security events or meet applicable legal duties. When a record no longer serves one of those purposes, our process removes it or changes it so it is no longer linked to you.

Changes and access

You can ask us for a copy of eligible personal data, request a correction or question a particular use. Send the request through the privacy contact path with your account identifier. We explain any identity check, legal exception or reason a requested change cannot be completed.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers focus on the account and wallet questions you are most likely to have before opening access. They explain what we collect, how device behaviour affects consent, what payment references mean and how to request a change. If your situation is not covered, use the support path beside the cashier and mention the exact account step or transaction reference.

It covers account creation, phone verification, sign-in activity, support conversations, cookies and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains retention, security checks and how you can request access or correction where local law permits.

Phone verification helps connect the person completing the account step with the correct account and helps protect access when a sign-in looks unusual. We use the verification status for account security and support handling. We do not ask you to send a one-time code through a support message.

No. A payment check may create a reference, time, amount and status for reconciliation, but we do not need your DANA password, QRIS credential or bank login to check that record. Keep those credentials inside the relevant payment service and share only the reference support requests.

Cookies can keep a session active and remember a privacy choice on the browser where you made it. Phone and desktop browsers store settings separately, so one device may ask again after you clear cookies. Clearing them can also sign you out or remove saved consent.

Yes, where local law permits. Use the privacy contact path and provide the email or phone connected to your account, the specific record you want copied or corrected and the requested change. We may verify ownership first, then explain the result or any legal reason for retaining a record.

We keep records for as long as they are needed for account operation, payment reconciliation, security investigation or applicable legal duties. The period can differ by record type. When the purpose ends, we remove the record or alter it so it is no longer linked to your account.

The policy is available for you to read, but account access and specific data rights depend on local law and eligibility. Where local law permits, you can ask about stored data, correction, restriction or deletion. We will explain any regional limit before handling the request.