Reference

dewa86 Privacy Policy For Your Account

Our Privacy Policy explains how dewa86 handles the details connected with your account, including phone verification, device access and payment status for DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice accessPolicy requests
dewa86 dewa86 Privacy Policy For Your Account
REQUEST A RESPONSE

Where To Ask About Privacy

A clear contact route helps you act on this Privacy Policy without guessing which team to reach. Start from your signed-in account help path and include the account phone number, the subject of your request and the relevant wallet or device detail. We use only the details needed to locate the record, then respond through the support route available to you. For Yogyakarta account access, the same policy request process applies as it does for Jakarta access, where local law permits.

Team online

Account help path

Use the help route connected to your signed-in account when you need to ask about stored data, phone verification or a device sign-in. Include a clear subject so we can match your request with the correct account record.

Cashier status query

If your question concerns a DANA, OVO, GoPay or QRIS record, send the payment reference and status shown beside the cashier entry. We use those details to locate the transaction without asking you to repeat unrelated account data.

Policy change request

For access, correction or deletion questions, identify the exact data you want us to check and the account phone number linked to it. We may ask for an account step that confirms you are making the request for your own record.

INSIDE OUR HANDLING

What We Do With Your Data

Privacy depends on practical controls, not broad promises. We separate account details from the payment status needed to trace a cashier request, use device signals to identify unusual sign-ins and keep access…

Account details

We use your submitted account details to create access, verify the phone linked to your account and answer account requests. If you ask us to correct a detail, we compare the request with the existing account record before making a change.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account entry can retain a reference, selected rail and status. These details let us check whether a cashier request matches your account without treating every wallet record as general profile data.

Cookies and browser storage

Cookies or similar browser storage may keep a sign-in session, language choice or security preference on the device you use. You can clear browser storage through your device settings, although doing so may require another account sign-in.

Device and sign-in checks

When you sign in from a phone or desktop browser, we may use technical signals such as browser type, session time and device context to spot unusual access. These checks help us direct a suspicious sign-in to account verification.

Retention and deletion

We retain account, security and payment records only for the operational, dispute or legal period that applies to the record. You can ask what remains connected with your account and request deletion where that request is available under local law.

Your privacy contact

Use the account help path to ask for access, correction, deletion or a purpose explanation. Include your account phone number and a precise request; we may confirm account ownership before disclosing or changing personal data.

Privacy Policy Questions About dewa86

These Privacy Policy answers cover the searches we hear most often before an account is opened or a wallet request is made. We keep the wording practical: what data is involved, which account step may be required and where local law affects access. If your situation is different, use the account help path with the smallest useful set of details.

The dewa86 Privacy Policy covers account details, phone verification, device and browser signals, cookies, payment records and support requests. It also explains retention, access, correction and deletion requests, with service access handled where local law permits.

We use the phone number linked to your account to create access, complete the required verification step and help match a privacy request with the correct record. If you ask for changes, we may use that step to confirm account ownership.

Yes. The Privacy Policy covers records created when you select DANA, OVO, GoPay, QRIS, bank transfer or virtual account. A record can include the selected rail, reference, status and account link needed to trace a cashier request.

When you sign in through a mobile browser or desktop browser, we may receive technical details such as browser type, session time and device context. We use these signals for session operation and unusual-access checks, not as a replacement for your account details.

Use the signed-in account help path and state whether you want access to a record or correction of a specific detail. Add your account phone number and the exact item to check. We may confirm ownership before sending or changing data.

Retention depends on the type of record and the operational, dispute or legal need connected with it. Account, security and payment entries may therefore follow different periods. You can ask which records remain linked to your account and request deletion where available.

You can submit a deletion request through the account help path and identify the records involved. We assess the request against account security, unresolved payment checks and applicable local law. Where deletion is available, we explain the next account step.