Reference

dewislot Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you create an account, sign in from a mobile browser, use DANA or QRIS, and contact support about wallet status.

Account dataWallet recordsCookie choicesContact rights
dewislot dewislot Privacy Policy for Your Account
CONTACT PATHS

Where Privacy Questions Go

A clear contact route helps when you want to ask about your Privacy Policy rights or a wallet record.

Account help Use the account help path for Privacy Policy questions, correction requests and access concerns.
Wallet records For a DANA, OVO, GoPay or QRIS query, send the transaction reference and date…
Security concern If you notice an unfamiliar sign-in or device, contact support through the account route…
CONTROL AND SECURITY

What We Do With Your Data

We keep the Privacy Policy practical: collect what an account task needs, use it for a stated purpose, and limit internal access.

Registration details

Your name, phone detail and verification status help us create the correct account path. We use them to confirm account ownership before discussing personal records or changing account data.

Device signals

Browser type, device signals and sign-in times can help us detect unusual access. These records support account protection when you move between a phone and desktop browser.

Cookie settings

Cookies can keep your session, language choice and policy prompt consistent. You can manage browser cookie controls, though disabling them may require another sign-in or affect account access.

Payment matching

We use transaction references, amounts and status results to match DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity with your account.

Retention periods

We keep records only as long as needed for account operation, security checks, dispute handling or legal duties. When a record is no longer needed, our process removes or anonymises it.

Change requests

Ask us to correct or access personal data through account help. Include the affected account detail, and we may verify ownership before applying a change or explaining a restriction.

Privacy Policy Answers for Indonesia

These Privacy Policy answers cover the searches we hear most often before account access. They explain why we request account and wallet details, how you can ask for a copy or correction, and what happens when you browse from a phone. If your question involves a particular record, use the account help route with its reference rather than sending a password.

The Privacy Policy covers account registration, phone verification, sign-in records, device signals, cookies, support messages and payment references connected with your dewislot account and its access.

We use phone verification to confirm account ownership, reduce mistaken account changes and respond to Privacy Policy access requests. We do not need your wallet password to check a request.

Yes. The Privacy Policy covers transaction references and status data for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity when linked to your account.

Open the account help path and ask for a copy of your personal data. Include your linked phone detail or email, then complete ownership checks before we disclose account records.

Yes. Send a correction request through account help and identify the record that needs changing. We may request phone verification before updating details or explaining why a field must remain.

Cookies can keep your mobile browser session and policy choices available between pages. If you block them, you may need to sign in again or complete another account check.

We retain selected records for account operation, security, disputes and legal duties, then remove or anonymise them when no longer needed. The period depends on the record and local law.