Reference

Privacy Policy for Your dewa688 Account

Our Privacy Policy explains how we collect, use, secure and retain the details connected with your dewa688 account.

Account clarityWallet recordsCookie choicesSecure access
dewa688 Privacy Policy for Your dewa688 Account
REQUEST A DATA CHECK

Where Your Privacy Questions Go

A direct request helps us resolve a data question without making you repeat the full account story.

Account request Ask us to locate the account details linked to your verified phone number. We use that account step to reduce mistaken matches, and you should not send a password, wallet PIN or full payment credential when requesting a Privacy Policy response.
Wallet question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, include the transaction reference and date. We can then check how the payment status is attached to your account without asking you to disclose a private wallet PIN.
Access correction If your name, phone detail or device record needs attention, tell us which field appears wrong and why. We may ask for an account check before making a change, so another person cannot alter your privacy or payment records.
INSIDE OUR HANDLING

What We Keep And Why

We keep the Privacy Policy practical by linking each data use to a visible account action. Registration and phone verification support account access; payment references support reconciliation; device signals help protect sessions…

Account data

We handle the details you enter during registration and the phone verification step used before account access. Keeping these records accurate helps us identify your account when you ask about a login issue, a Privacy Policy request or a payment reference.

Payment matching

DANA, OVO, GoPay and QRIS status can be linked to your account through a reference, while bank transfer and virtual account details help us reconcile a request. We use those records for account service and payment checks rather than unrelated messaging.

Device security

When you move between a mobile browser and desktop, we may record device, browser and session signals to identify unusual access. These signals help us ask for an account check when a login pattern does not match your normal activity.

Cookie controls

Cookies can remember a session choice or help us understand whether a policy page loads correctly. Your browser controls whether optional cookies remain active; changing them may affect saved preferences, but it does not erase account records by itself.

Retention period

We retain account, support and payment records only for the period needed for their stated purpose or a local requirement. A deletion request may therefore remove eligible details while records needed for a payment dispute or account protection remain restricted.

Your request

You can ask what personal details we hold, request a correction, or ask whether removal is available where local law permits. Send the request through your account support path and describe the exact record, such as a phone detail or QRIS reference.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the searches we expect from an Indonesian account holder before registration or a wallet request. Each answer points back to an account action, payment reference, device path or support request so you can decide what to send and what to expect. If your situation involves a location rule, access depends on local law.

The Privacy Policy covers account registration, phone verification, device and browser signals, cookies, support requests, and payment references for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. It also explains retention, security handling and the route for asking about your personal details.

We use your phone number to create and identify your account and to complete the verification step before account access. It can also help us distinguish your request from another account when you ask about a login, payment receipt or Privacy Policy data change.

Yes. The Privacy Policy explains how DANA and QRIS references can be connected to your account for payment matching and status checks. OVO, GoPay, bank transfer and virtual account references follow the same account-service purpose, and you should not send a wallet PIN.

We may use device, browser and session details to protect account access and identify unusual login activity. A mobile browser and a desktop session can produce different signals. If a pattern needs checking, we may ask you to confirm the account before discussing records.

Where local law permits, you can ask what eligible personal details we hold or request a correction. Use the account support path, identify the field or payment reference, and provide enough detail for us to locate it. We may verify account ownership first.

Retention depends on why the record exists and on applicable local requirements. Account, support and payment records may remain while needed for security, reconciliation or a dispute. A closure or removal request does not automatically erase records that must be restricted or retained.

Start through the support route connected to your account and state that your request concerns the Privacy Policy. Include your verified phone detail, the relevant record type and any payment reference, but never include your password, wallet PIN or full payment credential.