Reference

depo62 Privacy Policy For Your Account

depo62 Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, and use DANA, OVO, GoPay or QRIS.

Clear data purposesWallet record detailCookie choicesAccount contact path
depo62 depo62 Privacy Policy For Your Account
CONTACT YOUR WAY

Get Privacy Policy Help Before Access

A clear contact path helps when you want to ask about the Privacy Policy, correct an account detail or understand a wallet record.

Account questions Ask us which personal details are linked to your depo62 account and why a…
Wallet records For DANA, OVO, GoPay or QRIS questions, send the payment date, amount reference and…
Security concerns If a phone, browser or sign-in event looks unfamiliar, contact us through the account…
DATA HANDLING

What Our Privacy Policy Covers

We keep the Privacy Policy practical by tying each data use to an account action: sign-in, wallet matching, security screening or a support request.

Account data

We may hold your account contact details, sign-in history and verification status because those records support access control. When you ask us to correct a name, phone detail or email address, we compare the request with the account record before making a change.

Cookies and sessions

Cookies can keep a signed-in session active, remember a selected language or help us identify a failed page request. Your browser controls can block or delete them, although removing session cookies may require you to sign in again before reaching account pages.

Wallet matching

A DANA, OVO, GoPay or QRIS reference is used to connect a receipt with the correct account status. Bank transfer and virtual account records serve the same narrow purpose, so support can compare the receipt without requesting your wallet login credentials.

Account security

We record device and sign-in signals to identify unusual access, especially when a new phone or desktop browser is used. If a check appears, we may ask you to confirm account ownership before changing contact details or discussing a payment record.

Retention choices

We retain records only for the period needed for account security, payment matching, support history or a legal requirement that applies where local law permits. You can ask which category applies to a record and whether deletion or reduced retention is available.

Change requests

To request access, correction or removal, contact support with your account reference and a clear description of the request. We may verify ownership first, then confirm what we changed, what must remain and when the Privacy Policy request was completed.

Privacy Policy Questions For depo62

These Privacy Policy answers address the questions we hear before an account is opened or a wallet is connected. We explain the practical path for account data, cookies, payment references, correction requests and local access. If your situation involves a specific receipt or sign-in event, include that context when contacting us so our response can focus on the relevant record.

The depo62 Privacy Policy covers account details, sign-in and device records, cookies, payment references, support messages and security checks. It explains why we use each category, how we protect account access and how you can request access, correction or removal where local law permits.

We collect the details needed to create and protect your account, confirm ownership and respond to support requests. A contact detail can also help us match a DANA, OVO, GoPay or QRIS receipt with the correct account without asking for your wallet password.

Yes. The Privacy Policy covers technical records from the mobile browser or desktop browser you use, including session activity, device type and security signals. These records help us identify unusual sign-ins and keep the account path consistent when you move between devices.

Contact our support route with your account reference and the exact detail that needs correction, such as a phone number or email address. We verify account ownership before changing it, then confirm the result and explain any record that must remain for security or legal reasons.

We use wallet references and receipt details to match a payment event with your account status, investigate a missing update and answer a support request. We do not need your wallet password. For a query, share the date and reference while covering unnecessary sensitive codes.

You can ask us to close the account or remove eligible personal data through support. We first confirm ownership, identify the records covered by your request and explain what may need to stay for payment matching, account security or a legal requirement where local law permits.

Yes. Account access and eligibility depends on local law. Our Privacy Policy describes how we handle data for supported Indonesian access where local law permits, while a location or account check may limit what we can provide or which records we can process.