Reference

dewi39 Privacy Policy for Your Account

Our dewi39 Privacy Policy explains what account details we collect, why wallet records from DANA, OVO, GoPay and QRIS may appear in our systems, and how you can…

Clear data purposesWallet record contextAccount request pathLocal-law wording

Browse Our Lobby Read FAQ

How Privacy Policy Applies to Wallet Data

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

This Privacy Policy covers details you provide when opening an account, completing phone verification, signing in, and contacting our account support channel. It also explains technical data created when your device reaches the lobby, such as browser type, session time and security events. Payment records can

1
include a selected rail, transaction reference and status for DANA, OVO, GoPay, QRIS, bank transfer or virtual account; we use those details to match account activity and resolve status questions. We do not describe access as universal: eligibility depends on local law, and any account or
2
wallet activity is handled where local law permits. The policy applies to dewi39 pages and account flows that link back to this page. If a payment partner or bank handles part of a transaction, its own privacy terms may also apply. You can ask us which
3
category of data relates to your account and why it was retained.

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

DIRECT HELP PATH

Privacy Questions Reach Our Account Team

A clear contact route matters when you want to understand a record rather than guess from a wallet screen.

SIX DATA CONTROLS

Six Practical Controls Behind This Policy

We keep the Privacy Policy practical by linking each promise to a handling step you can recognise.

Purpose-based collection

We collect account and phone-verification details for access, security, support and transaction matching. We use the stated purpose to decide which records are relevant when you ask about your data.

Payment references

A DANA, OVO, GoPay or QRIS transaction may create a reference, amount status and time record. Bank transfer and virtual account entries can be matched in the same way for account support.

Cookie choices

Cookies can help keep a signed-in session, remember device preferences and detect unusual access. You can manage browser cookie settings, although changing them may affect login continuity or policy-page access.

Account security

Phone verification helps us check account ownership before access or sensitive requests. Never send a PIN or password through support; we use account details and verification steps instead.

Retention review

We retain records only for the operational, security or legal reason described in the Privacy Policy. When that reason ends, records are reviewed for removal, restriction or continued protection.

Change requests

You can request access, correction or clarification through the support path linked to your account. Tell us which record concerns you, and we may confirm identity before making a change.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers address the searches we hear most often before account access. They cover payment records, cookies, verification, requests and the local-law boundary, so you know what to expect before contacting our account team.

It covers account details, phone verification, device cookies, security events, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Use the support path inside your account and ask for a copy or explanation of your stored details. Include your registered phone detail, then complete any identity check we request.

We do not ask you to send a wallet PIN or password through support. Our records may show a payment reference, rail, time and status, while sensitive wallet credentials stay outside that request.

Cookies can maintain a login session, remember device settings and help identify unusual access. Browser controls let you change cookie behaviour, but some account functions may not continue normally afterward.

Yes, request a correction through the account support route and identify the detail that needs attention. We may verify your phone or account ownership before changing personal or payment-linked records.

Retention depends on the purpose, security need and legal requirement described in the Privacy Policy. We review records when those reasons end, while protecting any detail that must remain available.

Yes. Account eligibility and related handling depend on local law, and access is provided where local law permits. Contact support if you need the policy applied to your specific account situation.

dewi39 Privacy Policy for Your Account

Privacy Questions Reach Our Account Team

Six Practical Controls Behind This Policy

Purpose-based collection

Payment references

Cookie choices

Account security

Retention review

Change requests

Privacy Policy Answers for Indonesian Accounts

01 What does the dewi39 Privacy Policy cover?

02 How can I request my data under the Privacy Policy?

03 Does dewi39 store my DANA or QRIS PIN?

04 Why does the Privacy Policy mention cookies?

05 Can I correct details held on my account?

06 How long does dewi39 keep account and payment data?

07 Does access to my account depend on local law?

Related Pages