Reference

Legal terms for your depo62 account

depo62 sets out Legal terms for account access, wallet checks, personal data and contact in one place, so you can understand the account step before entering the lobby.

Account accessData and cookiesPayment checksContact routes
depo62 Legal terms for your depo62 account
HELP WITH TERMS

Get a direct answer on Legal

A clear contact path matters when a policy question affects your account.

Account access If you cannot enter your account, contact support through the sign-in help route and…
Payment status For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account query, send the…
Policy request To ask about personal data, cookies, retention or a change to your details, use…
DATA AND CONTROL

How we handle your policy requests

Legal is also about what happens after you open an account. We keep account records connected to the phone verification and payment checks needed for account operation, protect access with controlled sign-in…

Personal data

We use the account details you submit for access, verification, payment-status checks and support handling. Keep your phone details current, and contact us if a record is inaccurate or no longer reflects your account.

Cookies

Cookies may keep essential sign-in and page settings working on your device. You can check browser controls when available, but changing them may affect account access or the way policy pages load.

Account security

Never share your password, wallet PIN or verification code. If your phone or sign-in details change, use the account contact route so we can explain the required security check before making an update.

Payment records

A receipt reference, wallet status and transfer time help us trace a payment question. DANA, OVO, GoPay, QRIS and bank records may require matching details before we can discuss a transaction.

Retention

We retain records only for the account, security, payment and legal purposes that apply to the request. The period can differ by record type, so ask support about the specific item rather than assuming one period.

Change requests

Send a correction, access or deletion request through the account contact path. We may verify your identity first, then explain what can be changed and whether local law requires a record to remain available.

Answers before you open an account

These Legal answers cover the questions that usually arise before account creation or during a wallet-status enquiry. They explain the practical path without replacing the wording shown on the current policy page. If your case involves a specific transaction, include its reference and use the contact route connected to your account. Access depends on local law, and the checks applied to your account can vary with the payment method, device and request.

Legal access depends on local law, your account details and the eligibility checks shown during account creation. We may require phone verification before account access. If the route is unavailable for your location, contact support through the sign-in path for clarification.

We use submitted account data for sign-in, phone verification, payment-status checks, security and support. We do not need your wallet PIN or password to trace a receipt. Ask through the account contact route if you need a correction or access request.

Yes, send the request through the account contact path and identify the detail you want changed. We may confirm your identity before editing it. Where local law permits, we will explain the available action and any record that must remain.

A DANA or QRIS payment may need a receipt reference, transaction time and matching account details before its status can be discussed. The same approach can apply to OVO, GoPay, bank transfer and virtual account payments.

Cookies can retain essential sign-in and page settings on your device. Browser controls may let you change them, but disabling required cookies can affect account access or page functions. Contact support if a policy page does not load correctly.

Retention depends on the record type, account purpose, security needs, payment tracing and applicable legal requirements. We do not assign one period to every record. Ask support about a named record and include the account contact route for verification.

Use the support or account contact route shown after sign-in, and describe whether the matter concerns access, data, cookies, security or payment status. Include a transaction reference when relevant, but never send a password, PIN or verification code.