Reference

Privacy Policy for Your ratu lotre Account

Our Privacy Policy explains how ratu lotre handles the details needed for your account, including phone verification and wallet checks for DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record controlsPhone verification contextPolicy request path
ratu lotre Privacy Policy for Your ratu lotre Account
REQUEST HELP CLEARLY

Get Privacy Help Beside Account Support

A clear request helps us find the right record without asking you to send unnecessary wallet details. Use the account help route for questions about the Privacy Policy, phone verification, a DANA Wallet Topup reference or a QRIS status record. We may ask you to confirm the account email or phone number before discussing private data. If you cannot sign in, describe the issue through the support route and we will explain the next identity check.

Team online

Policy request

Ask about the Privacy Policy through account help and state whether your request concerns access, correction, deletion or a question about how we use your account record.

Wallet record

For DANA, OVO, GoPay or QRIS questions, include the transaction reference and date rather than sharing a password, full wallet PIN or unrelated private details.

Sign-in issue

If phone verification blocks account access, use the support path linked to the sign-in screen. We first confirm account ownership before discussing stored contact details.

CONTROL YOUR RECORDS

What Our Privacy Process Covers

We keep the Privacy Policy practical by tying each data category to an account action. Login details support access, wallet references support reconciliation, and device signals help us spot unusual sign-in behaviour.

Account details

We use your contact and verification details to create, protect and restore your account. A clear phone verification step helps us distinguish an account owner from an unauthorised sign-in attempt.

Payment references

DANA, OVO, GoPay and QRIS references let us match a wallet action with its status. Bank transfer and virtual account references serve the same reconciliation purpose without requiring your banking password.

Device signals

A mobile browser may send device and session signals linked to sign-in safety. We use these signals to examine unusual access patterns, not to read unrelated files or messages on your device.

Cookies

Session cookies can keep your account path working between the sign-in screen and the lobby. You can manage browser cookie settings, although disabling them may interrupt verification or policy-request forms.

Retention period

We retain account and payment records only while they serve access, reconciliation, dispute handling or legal duties. When a record no longer has a valid purpose, we delete or anonymise it through our data review process.

Change requests

To request access, correction or deletion, contact us through account help with the relevant account identifier. We may verify ownership, explain any lawful retention and confirm the action taken on your request.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the questions we expect before you open an account or check a wallet record. They explain what we collect, how a mobile session works, which account step protects your request and how to contact us. If your situation is not listed, use the policy request path and include only the details needed to identify the matter.

The Privacy Policy covers account contact details, phone verification, device and session signals, cookies, payment references and support requests. It also explains retention, account-security checks and the ways you can ask for access, correction or deletion of eligible records.

Phone verification helps connect an account request to the person who controls the registered contact number. We use the result to protect sign-in and privacy requests, and we may repeat an ownership check before discussing account details.

Yes. The Privacy Policy covers the reference, status and timing details needed to reconcile DANA and QRIS actions. It also applies to OVO, GoPay, bank transfer and virtual account references, but never requires you to share a wallet PIN.

We may receive session, browser and device signals that help protect account access. The Privacy Policy does not give us access to unrelated photos, messages or files. Browser cookie settings can affect the sign-in and verification path.

Use account help and identify the account with its registered email or phone number. State that you want access under the Privacy Policy. We verify ownership first, then explain the records available, the delivery method and any lawful limits.

You can request correction or deletion through the same policy contact route. We assess the request against active account access, payment reconciliation, disputes and legal duties. If a record must remain, we explain why and remove it when that purpose ends.

Yes. Account access and the handling of certain requests depends on local law. Where local law permits, we apply the rights and request steps described here. If a local rule changes the response, we explain the applicable reason through support.