Reference

raya999 Privacy Policy for Your Account

Our Privacy Policy explains how raya999 handles the details you provide when opening an account, confirming your phone, signing in on mobile or desktop, and checking wallet status.

Account dataWallet recordsDevice accessPolicy requests

Explore Our Lobby Read FAQ

How Wallet Data Fits Our Policy

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

This Privacy Policy covers details connected with your raya999 account, including your contact details, phone verification status, sign-in records, device signals, support messages and transaction references. When you choose DANA, OVO, GoPay or QRIS, we receive the payment status and reference needed to match an account

1
action; we do not ask you to send wallet passwords through support. A bank transfer or virtual account may create a bank reference that helps us check a payment record. We use these details for account access, payment reconciliation, security checks, policy requests and required retention.
2
Access or eligibility depends on local law, and our handling may change when a legal requirement applies. If you believe a record is inaccurate, contact us through the account support path and include the relevant date, wallet rail and account phone number.

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

CONTACT ROUTES

Contact Routes for Account Data

A direct support path helps you ask about the Privacy Policy without exposing account details in a public message.

DATA PRACTICE

Six Data Practices Behind Your Account

We keep the Privacy Policy practical by linking each data use to an account task you can recognise.

Account data use

We use your account details to create access, confirm phone ownership, respond to support and connect an authorised payment reference. We do not need wallet passwords to check whether DANA, OVO, GoPay or QRIS shows a completed status.

Cookies and sessions

Cookies and session records help keep your signed-in path working across the mobile browser or desktop browser. They can remember security settings and page activity, while you can manage cookie controls through your browser settings.

Account security

We may compare a new sign-in with your phone verification and recent device activity before discussing account data. If a sign-in looks unusual, support may request an ownership check before changing contact or access details.

Retention periods

We retain account, support and payment-reference records only for the period needed for account operations, security checks, dispute handling or a legal requirement. When a record is no longer needed, our handling follows the applicable retention process.

Who receives data

Access is limited to the teams and service partners that need a record for account support, security or payment reconciliation. A DANA, OVO, GoPay or QRIS reference is handled for its stated account purpose rather than shared as public profile data.

Requests to change

You can ask us to correct account details, explain a data use, or remove a detail where the law allows. Send the request through account support with your phone verification context, and we will confirm the next step.

Privacy Policy Questions for raya999

These Privacy Policy answers address the account and wallet questions we expect you to ask before opening access. They cover what we collect, how mobile sign-in works, which payment references appear in our records, and how to request a correction. Where a legal right or access condition applies, the answer depends on local law.

The raya999 Privacy Policy covers account details, phone verification, device sign-in records, support messages, cookies and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect you with the correct account and supports recovery when access is challenged. It also gives support a practical ownership check before discussing personal data or changing account contact details.

Yes. The Privacy Policy covers records created when you sign in through a mobile browser or desktop browser, including session and device signals used to maintain access and investigate unusual account activity.

We may receive a payment status and reference linked to DANA, OVO, GoPay or QRIS, along with bank transfer or virtual account references. We do not ask you to send wallet passwords through support.

Use the signed-in account support route and describe the detail that needs correction. Include your verified phone context and the relevant record date; we will confirm ownership before making an approved change.

You can ask us to remove or restrict a detail where local law permits. Some account, security or payment records may need retention for a legal requirement, dispute check or account-safety process.

Open the support contact route from your account, or use login help if access is blocked. State that your request concerns the Privacy Policy and include only the account details needed to identify the issue.

raya999 Privacy Policy for Your Account

Contact Routes for Account Data

Six Data Practices Behind Your Account

Account data use

Cookies and sessions

Account security

Retention periods

Who receives data

Requests to change

Privacy Policy Questions for raya999

01 What does the raya999 Privacy Policy cover?

02 Why does raya999 need my phone verification?

03 Does the Privacy Policy cover mobile browser access?

04 What wallet details does raya999 receive?

05 How can I correct my raya999 account data?

06 Can I request removal of personal data?

07 How do I contact raya999 about the Privacy Policy?

Related Pages