Reference

dewa1000 Privacy Policy for Your Account

Our Privacy Policy explains how dewa1000 handles the details you provide before account access, during wallet checks and when you browse titles such as VIP Baccarat or Asgardian…

Account dataWallet recordsCookie choicesDevice access
dewa1000 dewa1000 Privacy Policy for Your Account
ASK ABOUT DATA

Get Policy Help Before Account Access

A clear contact path helps when you want to understand a Privacy Policy request before opening or using your account.

Account questions Ask how phone verification, sign-in records or a device session relate to our Privacy Policy. Include your registered contact detail so we can identify the account without asking for a password.
Wallet questions For DANA, OVO, GoPay or QRIS records, share the transaction reference and date rather than wallet credentials. We use those details to locate the relevant status and explain the data held.
Correction requests If your account detail appears wrong, contact us with the field that needs attention and a safe way to reach you. We will explain the checks needed before changing a record.
DATA CONTROL

What Our Privacy Policy Keeps Clear

We keep the Privacy Policy close to the account path so you can read it before completing phone verification.

Data collected

We may receive your phone number, account identifiers, device signals, session events and payment references. These details help connect a verified account with a requested action without exposing your wallet PIN.

Cookie choices

Cookies can support sign-in continuity, language settings and page security. Your browser lets you clear or restrict them, although changing those settings may require another account check on the next visit.

Account security

Phone verification is an account step before access. We use session and device signals to investigate unusual sign-ins, and we will not ask for your DANA, OVO, GoPay or QRIS PIN.

Record retention

We retain account and payment references for the period needed for security, service records and legal duties. When a record is no longer needed for those purposes, our handling process addresses its removal.

Policy changes

When this Privacy Policy changes, we update the page so you can compare the current wording with your next account visit. The effective wording is the version shown on this page.

Your request route

You can ask about access, correction, deletion eligibility or the reason for a data use. Send the request through our account support path with enough detail for us to locate your record.

Privacy Policy Answers for dewa1000

These Privacy Policy answers address the searches we hear most often from Indonesian customers. They explain what happens around account opening, mobile access, cookies and local wallet records without asking you to reveal confidential credentials. If your situation involves a specific account or payment reference, use the support path above so we can check the relevant record.

The dewa1000 Privacy Policy covers account details, phone verification, device and session signals, cookies, payment references, retention and requests about access or correction where local law permits.

We use your phone number to support account verification, sign-in checks and account-related contact. It helps us distinguish your account from another session without requesting your wallet PIN.

Yes. Our Privacy Policy includes references connected with DANA, OVO, GoPay and QRIS requests, such as status, date and transaction reference. Wallet credentials are not requested through support.

Cookies may keep a session, language setting or security preference available when you use a mobile browser. You can restrict them in your browser, but a later sign-in may need another check.

You can request a correction by identifying the account detail that appears wrong and providing a safe contact route. We may ask for verification before changing information linked to your account.

We keep payment references for the time needed for security, account records and legal duties. The applicable period can depend on the record and local requirements described in the Privacy Policy.

You can ask what personal data we hold, why it is used and whether access, correction or removal is available. Such requests are handled after account checks and depends on local law.