Reference

What This Privacy Policy Covers

This Privacy Policy explains what we collect when you open an account, confirm a payment with DANA, OVO, GoPay, or QRIS, and use the site from an Android…

Account data onlyPayment referencesCookie controlLocal-law checks
estoto What This Privacy Policy Covers
CONTACT ROUTES

Where To Reach Our Team

A clear contact path matters when you want a privacy change, not a sales reply.

Live chat Start in the footer chat bubble and tell us which data point you want…
Email request Email us when you want a written record of the privacy request.
Account form Use the account form for correction or access requests tied to your profile.
DATA CONTROLS

Controls We Use For Data Care

We keep privacy work tied to the account itself, so each request has a clear owner and a clear reason.

Data minimisation

We collect the smallest set that still lets us verify your account, match DANA, OVO, GoPay, or QRIS entries, and keep your session stable. Extra details stay out unless you send them in a support request.

Cookies

Browser cookies help us remember language choice, login state, and device type. If you clear them, you may need to sign in again, but your privacy request history still stays linked to the account record.

Account security

Password protection and account-matching checks keep your data from being edited by the wrong person. If we add extra verification for a request, we ask for it before any sensitive change is processed.

Retention

We keep account records while your profile is active and for a limited period after that when local law, dispute handling, or fraud prevention requires it. After that, the relevant data is removed or anonymised.

Change requests

If your name, contact detail, or payment reference needs correction, send the request from the registered email or through chat. We compare it with your file first, then update only the fields that need changing.

Access and deletion

You can ask what we hold or request removal where local law allows it. We may refuse a request that conflicts with a legal duty or an active dispute, and we will explain why.

Questions About Privacy And Data

These answers focus on how your account data is handled day to day. If you change devices, use a new wallet route, or ask for a correction, we look at the same record first and then follow the local rule that applies. When a request touches deletion or access, the legal limit matters as much as the data itself.

We usually keep your contact detail, login record, device signals, and any payment reference needed to match the account. If a field is not needed for verification or support, we do not ask for it.

We keep the reference data needed to reconcile the wallet action with your account, such as status and time. We do not need your full wallet history, and we do not store more than the job requires.

Cookies help us remember that you are signed in, what language or device mode you used last, and whether the session is still active. Clearing them is fine, but you may need to sign in again.

Send the request from the registered email, live chat, or the account form, then tell us exactly which field is wrong. We verify ownership first, so the change lands on the correct record.

We keep active-account data while your profile is open and retain only what is required after that for legal, dispute, or fraud reasons. Once the retention period ends, we remove or anonymise the relevant record.

Yes, where local law allows it. After we confirm the account, we can tell you what we hold and check a deletion request, unless another legal duty or an active dispute requires us to keep it.

Use live chat or email us from the address linked to your account. We will point you to the latest version, explain what changed, and tell you whether the new terms affect your record.