Reference

Open the dewa888 Privacy Policy

The dewa888 Privacy Policy explains how we collect, use and protect the details connected with your account, including phone verification, login activity and wallet status.

Clear data purposesWallet activity contextAccount request pathIndonesia access terms
dewa888 Open the dewa888 Privacy Policy
REQUEST A RESPONSE

Reach us about your Privacy Policy

A clear request helps us locate the right account record without asking you to repeat the same issue.

Account questions Use the account support path when you want to ask what personal details are linked to your login or why phone verification is needed before account access. We will use the details you provide to locate the correct record and keep the request tied to your account.
Wallet records For a DANA, OVO, GoPay or QRIS data question, share the transaction reference and approximate date shown in your receipt. We can check the payment status connected with your account without asking you to disclose a wallet password or private security code.
Correction requests If your account details need correction, tell us which field is inaccurate and provide the account identifier used during login. We may ask for a phone verification step before changing the record, so the request is linked to the person who controls the account.
DATA HANDLING

Explore the safeguards behind this policy

We apply this Privacy Policy to the account path rather than treating every device visit as the same record.

Collection purpose

We collect account details to create and maintain your login, complete the phone verification step and connect support replies with the right record. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account are used to check transaction status rather than to request private wallet credentials.

Cookie choices

Cookies can keep an account session working, remember a page setting or help us understand whether a policy page loads correctly. You can manage cookies through your browser settings, although turning them off may require you to repeat login steps or may affect account access.

Device signals

We may use device, browser and session signals to identify unusual login activity and protect the account path. A phone and desktop can appear as separate access contexts, so we may ask you to complete phone verification when a new device does not match the recent account pattern.

Account security

Keep your password and verification details private, and contact us if a login or wallet status looks unfamiliar. We do not need your full DANA, OVO, GoPay or QRIS security code for a Privacy Policy request, payment receipt check or account correction question.

Retention period

We retain account, security and transaction records only for the period needed for the purpose described in this Privacy Policy, account support and applicable legal duties. When a record is no longer needed, we remove it or handle it in a way that no longer identifies your account where practical.

Your request route

You can ask which personal details we hold, request a correction or raise a concern about how data is used through the account support path. Include your account identifier and a precise request; we may confirm phone ownership before sharing or changing account-linked data.

Ask about dewa888 Privacy Policy

These Privacy Policy answers cover the questions you are most likely to have before opening an account or sending a data request. We focus on the account phone number, device access, cookies and local payment references because those details commonly appear when you check login or wallet status. If your situation is not covered, use the account support path and describe the exact record or transaction you want us to check.

The dewa888 Privacy Policy covers account details, phone verification, login and device signals, cookies, payment references, support requests, security checks and retention. It explains why we use each category and how you can ask about, correct or raise a concern about data linked with your account.

We may collect details needed for an account, such as your phone number, login record, device or session signals and support messages. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account can also be used to match a receipt with the correct account.

Phone verification helps us confirm that the person requesting account access or a data change controls the phone linked with that account. It also helps us respond to correction requests without exposing account details to someone who only has a transaction reference.

Cookies may keep your account session active, remember a setting or show whether the Privacy Policy page works correctly on your browser. You can manage them in browser settings. If you disable necessary cookies, you may need to repeat login steps or lose some account-path functions.

Yes, you can send a request through the account support path asking what account-linked data we hold or which field needs correction. Include your account identifier and a clear description. We may complete a phone verification step before sharing or changing personal details.

We keep payment references, login records and security details only for the period needed for the stated account purpose, support handling and applicable legal duties. A DANA, OVO, GoPay or QRIS reference may remain while a receipt or status question is being resolved.

The policy is provided to explain our data handling, but account eligibility and access depends on local law. If you are in Indonesia, read the Privacy Policy before submitting account details, and contact us through the support path if a local access question remains.