Reference

desabet Privacy Policy for Indonesia

Your account, DANA, OVO, GoPay and QRIS details receive a clear Privacy Policy path at desabet.

Account clarityWallet detailCookie choicesPolicy requests

How DANA and QRIS Data Fits

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

Our Privacy Policy describes the account details needed before access, including your contact information and phone verification status. When you choose DANA, OVO, GoPay or QRIS, we use payment reference details to match a transaction with your account; we do not need your wallet password. Bank

1
transfer and virtual account records may show a reference, amount and status, including rails connected with BCA, BRI, Mandiri or BNI. We use these records to confirm account activity, investigate a missing receipt and meet applicable legal duties. The policy also covers device signals used to
2
keep sessions consistent, cookies that remember selected settings and retention periods for account records. Access depends on local law, and our processing applies where local law permits. Read the full policy before opening an account, and contact us if a section does not match your question.

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

POLICY HELP ROUTE

Get Privacy Policy Help Near Wallet Support

A clear contact path matters when a Privacy Policy question concerns a wallet reference, a phone check or a device session. Open the support route from your account area and include the email or phone linked to your account, the relevant payment rail and a short description of your request. We use those details to locate the right record without asking for your wallet password.

Team online

Account contact

Use the support route attached to your account when you want to ask about the Privacy Policy, request a copy of your details or clarify why a phone verification record is held.

Wallet reference

For DANA, OVO, GoPay, QRIS or bank transfer questions, include the payment reference and date. Never send a wallet PIN or password; our team only needs matching details.

Device session

If a mobile session looks unfamiliar, tell us the device type, approximate time and account contact. We can examine the session record and explain the related Privacy Policy step.

DATA CONTROL CHECK

What Our Privacy Process Covers

We keep the Privacy Policy practical by connecting each data purpose to an account action you can recognise.

Account data

We may hold your account contact, phone verification result and sign-in history so we can connect requests to the correct account. The Privacy Policy explains the purpose of each record.

Cookie settings

Cookies can retain a selected setting or help keep a session connected. You can manage cookie behaviour through your browser, although changing it may affect account access steps.

Session safety

Device and session signals help us identify unusual sign-in activity. If your phone or browser changes, contact support through your account path rather than sharing a password.

Retention timing

We retain account, payment reference and support records only for the periods needed for account operation, dispute handling and legal duties described in the Privacy Policy.

Correction request

If your contact detail or account record is inaccurate, send a request through the account support path. Include the affected field so we can check the correct record.

Deletion enquiry

You may ask whether a record can be removed. We will assess the request against account, payment reconciliation and legal retention needs, then explain the available Privacy Policy outcome.

Privacy Policy Questions About desabet

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening an account. They cover data access, cookies, payment references, device sessions and requests for correction or removal. Where a legal condition affects your request, the outcome depends on local law and the applicable rules for Indonesia.

It covers account contact details, phone verification, device sessions, cookies, DANA, OVO, GoPay and QRIS payment references, retention, security checks and the ways you can contact us.

We use the verification status to connect account access with the correct contact detail and to examine sign-in questions. The Privacy Policy explains its purpose and retention context.

Yes. It explains how we use a DANA or QRIS reference, status and related account detail to match a transaction. We do not need your wallet PIN or password.

Open the support route in your account area and ask for a copy of the data connected with your account. Include your linked contact detail so we can verify the request.

Yes. Send a correction request through the account support path and identify the inaccurate field. We will check the record and respond according to the Privacy Policy and applicable rules.

Cookies may remember settings or help maintain a browser session. You can adjust them in your browser, but some account access steps may change when cookies are restricted.

You can ask us to assess removal. We may need to retain account, payment or support records for reconciliation, disputes or legal duties, where local law permits.

desabet Privacy Policy for Indonesia

Get Privacy Policy Help Near Wallet Support

Account contact

Wallet reference

Device session

What Our Privacy Process Covers

Account data

Cookie settings

Session safety

Retention timing

Correction request

Deletion enquiry

Privacy Policy Questions About desabet

01 What does the desabet Privacy Policy cover?

02 Why does desabet need my phone verification record?

03 Does the Privacy Policy include DANA and QRIS transactions?

04 How can I request my desabet account data?

05 Can I ask desabet to correct my personal data?

06 How do cookies affect the Privacy Policy?

07 Can I request removal of my desabet data?

Related Pages