Reference

delimajitu Privacy Policy For Your Account

Your DANA, OVO, GoPay and QRIS choices stay connected to the account details needed for access, and our Privacy Policy explains how we handle each record.

Account dataWallet recordsCookie choicesRequest a change
delimajitu delimajitu Privacy Policy For Your Account
PRIVACY HELP

Get Help With A Policy Request

A clear support path matters when a privacy question sits beside a login or wallet issue.

Account request Use the support link inside your account to ask for a copy, correction or…
Wallet question For a DANA, OVO, GoPay or QRIS record, mention the receipt reference and date…
Access difficulty If login stalls, contact support through the available account path and describe your device…
DATA HANDLING

What We Do With Your Account Data

We keep the policy practical by linking each data use to an account action you recognise.

Account creation

When you open an account, we record the details needed to create your profile and complete phone verification before account access is provided.

Device signals

Browser type, device details and login time can help us recognise an unusual session when you move from mobile access to a desktop browser.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a cashier event to your account without storing secret wallet credentials.

Cookie settings

Cookies may remember sign-in preferences or support security checks. You can manage browser cookie settings, though changing them may affect account access.

Retention approach

We retain account, support and transaction records for the period needed for stated service, security and legal purposes, then assess whether continued storage is needed.

Change request

Ask us to correct account data, explain a use or discuss deletion by using the support path after login and identifying the record you want checked.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the questions we expect before you open an account or connect a local wallet. We explain what data is collected, how device and payment records are used, what you can request, and how to reach us when account access is unavailable. Where access or eligibility is discussed, it depends on local law.

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

Phone verification helps connect the correct person to an account and supports security checks before access. We use the result for account handling rather than unrelated purposes.

Yes. The policy covers device and browser signals such as type, session timing and login context when those details help maintain access or investigate unusual account activity.

We use payment references to match a wallet or cashier event with your account, check its status and answer receipt questions. We do not ask you to send secret wallet credentials.

Yes. Use the support path inside your account, identify the record or account detail involved, and ask for a copy, correction or explanation. We may need to verify your identity first.

You can adjust cookie controls in your browser and contact support if you need clarification about a cookie setting. Blocking some cookies may affect login or security checks.

Use the available support route and provide the account phone or email, device type and the step where access stopped. Do not include your password, wallet PIN or full payment credentials.