Reference

divalotre Privacy Policy for Your Account

Our Privacy Policy explains how divalotre handles the details connected with your account, device, wallet status and support requests.

Account clarityWallet recordsDevice safeguardsPolicy access
divalotre divalotre Privacy Policy for Your Account
CONTACT DATA HELP

Where To Ask About Privacy Policy

A clear contact path helps you resolve a privacy question without repeating your account story.

Account privacy request Ask us to explain, correct or remove eligible account data through the support path connected with your login. Include your registered phone detail so we can match the request safely.
Wallet record question For DANA, OVO, GoPay or QRIS records, provide the relevant receipt reference and date. We can then check the stored payment status without asking for your wallet password.
Access concern If a phone verification step or device sign-in looks unfamiliar, contact support from the account route before changing payment details. We may request account identifiers to confirm ownership.
HANDLING YOUR RECORDS

What Our Privacy Process Covers

Privacy controls work best when each record has a clear purpose and a practical account action behind it.

Account details

We use your chosen account identifier, phone verification result and sign-in history to create access, detect unusual entry and respond to a request about your own records.

Wallet references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a cashier event with your account. It is handled as a transaction record, not a wallet password.

Cookies and browser signals

Cookies and device signals can remember a session, language choice or security event. You can clear browser data, although doing so may require another phone verification before account access.

Account security

We compare sign-in details with account activity and may pause a sensitive request when the device or phone pattern changes. This helps protect your lobby access and payment history.

Storage and retention

We retain account and transaction records only for operational, security or legal purposes that apply to the request. When a record is no longer needed, our process removes or separates it.

Changes and requests

You can ask what personal data we hold, request a correction or question its use through support. We verify account ownership first, then explain the available action under local law.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account actions you are most likely to take from Indonesia. We explain what to send, how wallet records are matched and what happens when you use a phone, tablet or desktop browser. For any access question, eligibility depends on local law.

It covers account details, phone verification, sign-in events, device signals, cookies, wallet references, support messages and records connected with account activity. It also explains storage, security and requests for changes.

We use your phone number to create or verify account access, identify a support request and help detect unusual sign-ins. The verification step can appear again after browser data or device details change.

No. Our Privacy Policy describes storing payment references and status details for DANA, OVO, GoPay and QRIS, not your wallet password. A receipt reference helps us reconcile the account event.

Use the support route connected with your account and state which detail needs correction. Include your registered phone or email identifier; we verify ownership before changing personal data.

Yes. Ask through the account support path for the device and sign-in records connected with your account. We can explain the relevant entries and the available action where local law permits.

Cookies can keep a browser session, remember a language choice and support security checks. Clearing them may sign you out and trigger phone verification when you next access the account.

Retention depends on the record's operational, security or legal purpose. We keep transaction references such as QRIS or bank transfer details only as long as that purpose applies.