Reference

rajacuan slot Privacy Policy, Made Clear

Your account, device and wallet details receive a clear explanation in the rajacuan slot Privacy Policy.

Account dataWallet referencesDevice choicesPrivacy requests

How We Use DANA And QRIS Data

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

We use account details to create and protect your access, including your phone number, login records and verification status. When you select DANA, OVO, GoPay or QRIS, we may receive payment references and status details needed to match an account action with the correct wallet or

1
transfer record; we do not need your wallet PIN for that purpose. Device type, browser settings, IP address and sign-in time can help us detect unusual access and keep sessions working on mobile or desktop. Cookies may remember essential choices and support page functions. We retain
2
records only for operational, security or legal needs, then remove or anonymise them when they are no longer required. You can ask about your data, request a correction, or ask us to explain a processing purpose through the account support path. Access remains where local law
3
permits, and this policy applies to the service pages connected with your rajacuan slot account.

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

CONTACT PATHS

Get Privacy Help Beside Account Support

A direct account support route helps when a privacy question appears beside a login or wallet record. Start from the support area connected to your account and describe the request clearly, such as correcting a phone detail or asking why a payment reference appears. We use the account context to locate the relevant record without asking you to post sensitive credentials publicly.

Team online

Account access

If phone verification or a sign-in record looks wrong, use the account support path and include the affected step, device type and approximate sign-in time.

Wallet records

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account data, identify the payment rail and reference status so we can locate the matching record.

Privacy requests

Ask for access, correction or removal through the same support route. We may request account details to confirm that the request comes from the account holder.

SECURITY PRACTICE

What Your Privacy Choices Cover

Our privacy process follows the activity that creates each record, from phone verification through a mobile sign-in or a wallet status check.

Account details

We may store your registration details, phone verification status, sign-in history and account settings so access checks and privacy requests can be handled against the correct record.

Cookies and devices

Essential cookies and device signals can support session continuity, fraud checks and mobile display behaviour. You can manage browser cookie controls, though some account functions may then need another sign-in.

Security checks

We use sign-in time, device information and account events to identify unusual access. Never send a password, wallet PIN or verification code through a support message.

Retention period

Records remain available while needed for account operation, payment matching, security checks or legal duties. When a purpose ends, we remove or anonymise data according to our process.

Your requests

You can ask what account data we hold, request a correction, question a processing purpose or ask about removal through the privacy contact path linked to your account.

Policy changes

If this Privacy Policy changes, we place the updated wording on this page and may connect it to your next account visit so you can check the new terms before continuing.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the records you create through account access, device sessions and Indonesian wallet rails. They also explain how to reach us when a detail needs checking, without turning a privacy request into a general service question.

It covers account details, phone verification, device and browser signals, cookies, payment references, retention, security checks and the requests you can send about your personal data.

We use phone verification to connect the correct person with an account access step and to protect sign-ins. We record its status rather than asking you to share verification codes with support.

Yes. It explains how we handle payment references and status details linked to DANA, OVO, GoPay and QRIS, plus bank transfer or virtual account records used for account matching.

You can ask for access to account data or request a correction through the account support path. Include the relevant account step, and we may verify your account before responding.

Essential cookies can keep a mobile session working and remember necessary settings. Browser controls can remove or block them, but you may need to sign in again or lose some page functions.

We keep records while they support account operation, payment matching, security checks or legal duties. After the relevant purpose ends, we remove or anonymise them through our retention process.

Use the privacy contact route in the account support area. Describe the data or policy point clearly, and do not include your password, wallet PIN or one-time verification code.

rajacuan slot Privacy Policy, Made Clear

Get Privacy Help Beside Account Support

Account access

Wallet records

Privacy requests

What Your Privacy Choices Cover

Account details

Cookies and devices

Security checks

Retention period

Your requests

Policy changes

Privacy Policy Answers For Your Account

01 What does the rajacuan slot Privacy Policy cover?

02 Why does rajacuan slot need phone verification data?

03 Does the Privacy Policy cover DANA and QRIS payments?

04 Can I request a copy or correction of my data?

05 How does the Privacy Policy handle cookies on mobile?

06 How long does rajacuan slot keep account records?

07 Where do I send a privacy question?

Related Pages