Reference

lotus dewa Privacy Policy for Your Account

lotus dewa keeps its Privacy Policy close to the account path, so you can see how we handle your phone number, wallet records and device signals before opening…

Account dataWallet recordsDevice signalsCookie choices
lotus dewa lotus dewa Privacy Policy for Your Account
REQUEST HELP DIRECTLY

Get Privacy Policy Help With Your Account

A clear contact path helps when you want to ask about a record rather than a game or payment result. Use the support route shown on our site and include your account phone number, the request type and any relevant receipt reference. We use those details to locate the right record without asking you to send a password or full wallet credentials.

Team online

Account data request

Ask us to confirm which account details we hold, including your phone verification record and recent sign-in activity. We may ask for an account step to confirm that the request comes from you.

Wallet record question

For DANA, OVO, GoPay or QRIS questions, share the transaction reference and date shown in your receipt. We can check the linked status without requesting your wallet PIN.

Correction or deletion

Tell us which field should change or which record you want removed. We explain any retention reason that prevents immediate deletion where local law permits continued storage.

HOW WE HANDLE RECORDS

Privacy Choices That Stay Near Your Login

Privacy work is tied to practical account events, not hidden behind a separate process. We check the identity attached to a request, separate payment references from wallet credentials, and use device signals…

Account details

We use your phone number and verification result to connect you with the correct account. We do not need your password in a privacy request, and you should never include it in a support message.

Device and sign-in data

Browser type, device details, network signals and login time can help us recognise unusual access. These records support account protection and may be retained for security or legal needs.

Cookie controls

Cookies can keep your session active and remember selected settings on the mobile browser path. You can adjust browser cookie controls, although some account functions may then require another sign-in.

Payment separation

A DANA, OVO, GoPay or QRIS reference helps us match a receipt to an account, while wallet PINs remain with the payment provider. Bank transfer and virtual account references follow the same separation.

Retention approach

We keep account, support and transaction records only for the period needed for service administration, security checks, disputes and legal duties. A deletion request does not erase records we must retain.

Request route

For access, correction or deletion questions, use the contact path displayed on our site and identify your account phone number. We may request verification before changing or disclosing personal records.

Privacy Policy Answers Before Account Access

These Privacy Policy answers cover the questions we expect you to ask before opening an account or sending a data request. They explain the records connected with login, mobile browsing, local wallets and support, while the full policy remains the controlling text where local law permits.

We may collect account contact details, phone verification results, sign-in events, device and browser signals, support messages, cookie settings and payment references connected with DANA, OVO, GoPay, QRIS or bank transfer.

Your phone number links you to the correct account and supports the verification step before account access. We use it to locate your records when you request help, correction or a copy of data.

Yes. The policy covers the mobile browser path as well as other website access. It describes session cookies, device signals and login events created when you move from sign-in to the lobby.

We use payment references, status details and receipt data to match an account transaction. We do not need your wallet PIN, and the payment provider remains responsible for credentials held in its wallet.

Yes. Use our displayed support route, identify your account phone number and state whether you want access or correction. We may verify account ownership before sending records or changing a field.

You can request deletion where local law permits. We first check whether records must remain for security, dispute handling, transaction reconciliation or legal duties, then explain the result through the contact path.

Retention depends on the type of record and the reason it exists. We keep information for account administration, security, support, disputes and legal duties only for the period those needs require.