Reference

Privacy Policy For Your dewa11 Account

Our dewa11 Privacy Policy explains what account, device and payment details we collect, why we use them and how you can ask for changes.

Account clarityPayment recordsCookie choicesRequest support

Explore Our Lobby Read FAQ

How Privacy Policy Covers DANA And QRIS

dewa11 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy sets out how we collect and use details linked to your account, including your contact details, phone verification result, sign-in activity, device signals and transaction references. When you select DANA, OVO, GoPay or QRIS, we use the payment status and receipt details needed

1
to match your request, resolve a missing update and protect account access; we do not need your wallet password. Bank transfer and virtual account records may also be checked against the account step that created them. We use cookies and similar device data to keep a
2
session open, remember selected settings and detect unusual sign-in patterns. Access and eligibility depends on local law, and this policy applies where local law permits. We may update this page when our data practices change, with the current version displayed here.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Privacy Help Beside Your Account Path

A clear contact route helps you act on this Privacy Policy without searching through unrelated pages. Start from the support chat linked in your account area and tell us whether your request concerns access, a wallet record, a device cookie or a correction. We may ask for account details that let us verify the request, but we will not ask for your wallet password. Where access depends on local law, we explain the applicable step before making a change.

Team online

Privacy request

Use the support chat from your account area to ask what personal details we hold, why a field is used or how to request a correction. Include the phone number linked to your account so we can match the request without asking for your DANA, OVO or GoPay password.

Access concern

If phone verification blocks account access, contact support through the account help route and describe the device path you used. We check the sign-in record and verification state before responding, while keeping the request tied to your account rather than discussing private details in an open chat.

Payment record

For a QRIS, DANA, OVO, GoPay, bank transfer or virtual account query, send the receipt reference through the support chat. We use that reference to locate the payment event and explain its privacy handling without requesting a wallet PIN or unrelated account data.

DATA PRACTICE

Six Ways We Handle Your Details

We keep this Privacy Policy practical by describing the points at which data enters an account journey and the checks that follow.

Account details

We collect details you provide when opening or updating an account, such as your contact route and verification result. These fields support account access and policy requests. If a detail changes, use the support chat so we can check the account step before updating the record.

Payment matching

A DANA, OVO, GoPay or QRIS event can create a reference, amount and status record connected to your account request. Bank transfer and virtual account steps may create similar records. We use these entries to trace the event, not to collect your wallet password.

Cookies and devices

Cookies and device signals help keep your sign-in session working and identify unusual access patterns. The path can differ between an Android browser, iPhone browser and desktop browser. Clearing cookies may end your session, so sign in again before requesting account or policy changes.

Account protection

Phone verification gives us an account step to check before discussing private details. We may compare the verification state with sign-in activity when a request arrives. This helps prevent one person from receiving another person’s account data through the support chat.

Retention choices

We keep account and transaction records only for as long as needed for the purpose described in this Privacy Policy, account servicing and required operational records. When you ask about removal or correction, we explain which records can change and which must remain for a stated purpose.

Change requests

To request access, correction or deletion of eligible details, contact us through the support chat connected to your account. State the request clearly and provide the relevant phone verification route. We may need to confirm identity before sending account-specific details or applying a change.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the searches we hear most often from people opening an account in Indonesia. They cover the data connected to phone verification, wallet records, cookies, device access and requests made through support chat. If your situation involves a payment reference or an access rule, give us the exact account step so we can respond to the right record. Eligibility depends on local law and where local law permits.

The dewa11 Privacy Policy covers account details, phone verification, sign-in activity, device and cookie records, payment references and support requests. It explains why we use each category, how long records may be retained and how you can request access, correction or deletion where that request is available.

No. Our Privacy Policy distinguishes wallet credentials from payment references. When you use DANA, OVO, GoPay or QRIS, we may receive a transaction reference, status and receipt detail needed to match the account request. Your wallet password or PIN should remain with the payment service.

Phone verification gives us a direct account check before we discuss private details or process a policy request. We use the verification result with sign-in activity to reduce mistaken disclosure. If the check fails, contact support chat from the account route and describe the device you used.

Open the support chat linked to your account and ask for access or correction under the Privacy Policy. Mention the phone number connected to the account and the specific field or record. We verify the request first, then explain what can be supplied or changed.

On an Android browser, iPhone browser or desktop browser, cookies may keep a session open, remember settings and help identify unusual access. Clearing them can sign you out. Our Privacy Policy explains these purposes, and support can help if a cookie change affects your account route.

We retain records for the operational purpose described in the Privacy Policy, including account servicing, payment matching and required transaction history. A deletion request does not automatically remove every record. We explain the applicable retention reason and any eligible change after verifying your account request.

Yes. Use the support chat shown in your account area and label the request as a Privacy Policy matter. You can ask about account data, device records or a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference. Access depends on local law.

Privacy Policy For Your dewa11 Account

Privacy Help Beside Your Account Path

Privacy request

Access concern

Payment record

Six Ways We Handle Your Details

Account details

Payment matching

Cookies and devices

Account protection

Retention choices

Change requests

Privacy Policy Answers For Indonesia

01 What does the dewa11 Privacy Policy cover?

02 Does dewa11 store my DANA, OVO, GoPay or QRIS password?

03 Why does dewa11 need phone verification before access?

04 How can I request a copy or correction of my data?

05 How does the Privacy Policy handle cookies on mobile?

06 How long does dewa11 keep payment and account records?

07 Can I contact dewa11 about a privacy issue from Indonesia?

Related Pages