Reference

Privacy Policy for Your duren Account

Our Privacy Policy explains how duren handles the account, wallet and device details connected with your access.

Account clarityWallet contextDevice-aware accessPolicy contact
duren Privacy Policy for Your duren Account
CONTACT PATHS

Privacy Policy Help When Questions Arise

A clear contact path matters when you want to understand or change personal data held with your account.

Account data request Ask us to confirm which account details we hold, why they are used and…
Wallet record question For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, send the…
Correction or deletion Tell us which personal detail appears wrong or which data request you want to…
HANDLING DETAILS

How duren Applies This Privacy Policy

We keep our privacy work close to the actions you take, so the data explanation matches the account journey.

Account information

We may handle the account identifier, verified phone number, sign-in history and account status needed to provide access. Phone verification is an account step, not permission for us to read your wallet balance or phone contents. We use these details to authenticate requests and keep account records connected.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account step can create a reference, amount, rail and status record. We use that information to match the account action with the cashier record. We do not ask you to place a wallet PIN or banking password in support messages.

Device and browser signals

When you sign in from a phone or desktop browser, we may record device type, browser details, language setting and access time. These signals help us investigate unusual access and explain why an account step may appear again. We do not treat a device signal as a substitute for phone verification.

Cookies and stored choices

Cookies or similar storage can keep a session active, remember a page choice and help us understand whether a policy page or account screen loads correctly. You can manage cookie settings through your browser. Turning some storage off may require another sign-in or prevent a preference from being retained.

Security and retention

We restrict account data access to the operational purpose that requires it and retain records only for the period connected with access, payment reconciliation, security checks or a lawful request. A transfer reference may remain after an account change when a record is needed for a dispute or legal duty.

Your policy request

Send an access, correction, deletion or use question through our account help path with enough detail to identify the record. We may verify ownership before responding. If access or eligibility is discussed, the outcome depends on local law, the account record and any required security or payment checks.

Privacy Policy Answers for duren Accounts

These Privacy Policy answers address the account and wallet questions we hear most often from people in Indonesia. They explain what information may appear in our records, what you can request and why a verification step can be necessary. If your situation involves a payment reference or access concern, use the account help path with limited, relevant details rather than sending a password or wallet PIN.

The duren Privacy Policy covers account creation, phone verification, sign-in activity, device and browser signals, support messages, lobby access records and payment references. It explains why we use those details, how retention works and how you can request access or correction where local law permits.

Phone verification helps us connect an account request to the person controlling that account and supports security checks when access changes. We use the verified phone detail for account operations and request handling. It does not give us access to your private phone content or wallet PIN.

Yes. The Privacy Policy explains how payment references from DANA, OVO, GoPay and QRIS may be connected with an account action. We may also record bank transfer or virtual account status. We use those references to reconcile a payment step, not to collect your secret wallet or banking credential.

You can send an access request through the account help path and identify your account with the verified phone number or account identifier. We may check ownership before responding. The records we can provide, the response process and any limits depend on local law and the nature of the request.

Tell us which detail is inaccurate and provide the account identifier linked to it. We may ask you to complete phone verification before making a change. If the detail belongs to a payment or security record, we may preserve the original record while adding the corrected account context.

Retention depends on why the record exists. Sign-in, device and support details may be kept for access and security handling, while DANA, QRIS, bank transfer and virtual account references may remain for reconciliation or disputes. The applicable period depends on local law and the record's operational purpose.

Use the account help path and mention whether your question concerns cookies, browser storage, phone access or desktop access. We can explain the relevant signal and its purpose. You can also adjust browser storage settings, although doing so may require another sign-in or remove saved page choices.