Reference

raja5d Privacy Policy for Your Account Data

The raja5d Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or connect DANA, OVO, GoPay and QRIS for account…

Account detailsDevice and cookiesWallet activityPrivacy requests

Explore Our Lobby Read FAQ

How Wallet Data Is Used in Indonesia

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

Our Privacy Policy covers the account details you provide during phone verification, the device signals created when you sign in, and records connected with wallet activity. When you select DANA, OVO, GoPay or QRIS, we may retain the payment reference and status needed to match an

1
account action without storing more payment detail than the process requires. Bank transfer and virtual account references can also appear in account records. We use access logs to investigate sign-in issues, receipt mismatches and requests to change personal details. Where local law permits, we provide the
2
service and handle these records under the policy; otherwise, eligibility depends on local law. Read the policy before opening an account, and contact us through the account help path if a section is unclear.

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

PRIVACY HELP DESK

Privacy Questions Through Your Account Path

A clear account route helps us answer privacy requests without asking you to send sensitive details through an unverified channel. Start from account help, describe the record or device concern, and include the email or phone detail linked to your account. We can then check the request against the relevant sign-in, wallet or cookie record. If your question follows a QRIS receipt or DANA status issue, mention that reference rather than sharing a password or full wallet credentials.

Team online

Account help

Use the account help route when you want to ask which personal details are linked to your raja5d access. We may ask you to confirm the phone or email already attached to the account before discussing records, so another person cannot request changes in your name.

Receipt checks

For a privacy question connected with DANA, OVO, GoPay or QRIS, send the payment reference shown in your account rather than a password or wallet PIN. This lets us trace the status record while reducing the payment detail included in your support message.

Access concerns

If a new phone, browser cookie or sign-in attempt appears unfamiliar, tell us through account support and pause further access until we respond. We use the account path to compare device activity and help separate a genuine privacy concern from a routine login change.

DATA CONTROL LAYER

Cookies and Security Around Your Lobby Access

We keep the Privacy Policy practical by tying each data category to an account action you can recognise.

Account details

We use the phone or email attached to your account to verify access, respond to privacy requests and connect a requested correction with the right record. Please keep those details current; changing them through the account path helps us avoid editing another person’s account.

Cookie choices

Cookies can remember sign-in preferences, language settings and the point where you left the lobby. You can clear them from your browser settings, although doing so may require another account check. Our Privacy Policy explains which cookies support access and which are used for basic measurement.

Device signals

When you move from a mobile browser to desktop, the service may record device and session signals connected with that access. We use them to investigate unexpected sign-ins and account protection questions, not to ask you for a password in a support message.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create a reference, amount status or matching record. We use that information to identify the account action and resolve a receipt question, while you should never send wallet PINs or full credentials.

Retention period

Records remain available only as long as needed for account operation, security checks, dispute handling or a legal requirement described by the Privacy Policy. When a record is no longer needed, we remove it or separate it from direct account identification where the process allows.

Change requests

You can ask us to correct account details, explain a stored record or consider removal through the account help path. Include the specific field or activity, confirm your linked phone or email, and we will assess the request under local law before making a change.

Privacy Policy Questions for raja5d Accounts

These Privacy Policy answers address the account, device and wallet questions you are most likely to have before opening access. Each answer points you toward a practical next step, whether you want to understand cookies, correct a phone detail or ask about a DANA, OVO, GoPay or QRIS record. Where local law permits, we handle requests through the account support path.

The raja5d Privacy Policy covers account details, phone verification, device and session records, cookies, support messages and payment references linked with DANA, OVO, GoPay or QRIS. It also explains retention, security checks and how to request access, correction or removal where local law permits.

Yes. The Privacy Policy covers payment references and status records created when your account uses DANA or QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. We use those records to match an account action or check a receipt, not to request your wallet PIN.

We use phone verification to connect account access with the phone detail you provide and to help prevent another person from changing your records. If that detail is no longer correct, contact account help and confirm the linked account information before asking for an update.

You can request a correction through the account help path. State which field is wrong, such as your phone or email detail, and confirm the account connection. We assess the request under the Privacy Policy and local law before changing the stored record.

Clear cookies through your browser settings on mobile or desktop, then sign in again if access asks for a fresh check. The Privacy Policy explains the cookie categories involved. Clearing them can remove saved preferences and may not erase account records held for security or legal needs.

We keep account, device and wallet-related records for the period needed for service operation, security checks, dispute handling or a legal requirement described in the Privacy Policy. When continued retention is not needed, we remove the record or reduce its link to your account where possible.

Send your Privacy Policy request through account help so we can verify the linked phone or email without exposing your details in an unverified channel. Describe the record involved, such as a cookie, device sign-in or QRIS reference, and do not include passwords or wallet credentials.

raja5d Privacy Policy for Your Account Data

Privacy Questions Through Your Account Path

Account help

Receipt checks

Access concerns

Cookies and Security Around Your Lobby Access

Account details

Cookie choices

Device signals

Wallet references

Retention period

Change requests

Privacy Policy Questions for raja5d Accounts

01 What does the raja5d Privacy Policy cover?

02 Does the Privacy Policy cover DANA and QRIS records?

03 How does raja5d use my phone verification data?

04 Can I ask raja5d to correct my personal details?

05 How can I clear cookies used for my account?

06 How long does raja5d keep account and device data?

07 Where can I send a Privacy Policy request?

Related Pages