Reference

eshatoto Privacy Policy for Your Account

Our Privacy Policy explains what eshatoto collects when you open an account, sign in, use DANA or QRIS, and contact support.

Account dataWallet recordsCookie choicesSecurity steps
eshatoto eshatoto Privacy Policy for Your Account
CONTACT OUR TEAM

Get Privacy Policy Help Near Cashier

A clear contact path matters when you want to ask what data we hold or why a wallet record appears in your account. Open the support area after signing in and include the email or phone linked to your account. We use those details to locate the right record without asking you to send a wallet password or full payment credential.

Team online

Account support

Use the signed-in support path for Privacy Policy questions, access requests and corrections. Include your account contact detail so we can check the right record before responding.

Payment status

For a DANA, OVO, GoPay or QRIS question, share the transaction reference and date. We use that receipt detail to trace the wallet status without requesting your private wallet login.

Access concerns

If a new device or phone verification blocks account access, tell us through support. We may ask account security questions before discussing personal data or changing contact details.

DATA CONTROL POINTS

Your Account Data Across Mobile Wallets

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

Collection

We collect account contact details, verification results, device signals, session events and messages you send to support. The purpose is to provide access, check account safety and answer your request.

Wallet records

DANA, OVO, GoPay and QRIS may return a reference, amount status and processing result. We use those fields to match your account activity, while wallet credentials remain with the wallet service.

Cookies

Session cookies help keep your signed-in path working between the account page and cashier area. You can adjust browser cookie controls, although restricting them may affect sign-in continuity.

Account security

We use phone verification, sign-in signals and device checks to reduce unauthorised account access. Never send a password, one-time code or wallet PIN in a support message.

Retention

We retain account, transaction and support records only for the operational, dispute and legal periods that apply to the record. When a period ends, deletion or de-identification may follow.

Your request

You can ask what personal data we hold, request a correction or ask about removal through account support. We may verify your identity first, and the outcome depends on local law.

Privacy Policy Answers For Your Account

These Privacy Policy answers cover the searches we hear most often before an account is opened or a wallet is connected. If your situation involves a specific receipt, device or verification step, send the relevant reference through signed-in support so we can handle the request accurately.

It covers account details, phone verification, device and sign-in signals, cookies, support messages, wallet status records, retention, security practices and requests to access or correct your personal data.

Phone verification helps us confirm that the account contact belongs to you before access or a personal-data change. We use the result for account security, and handling depends on local law.

Yes. We explain how DANA, OVO, GoPay and QRIS references and payment statuses may be linked to your account. We do not ask for your wallet password or PIN.

You can send an access request through signed-in account support. Include the contact detail linked to your account; we verify the request before sharing records, where local law permits.

Contact support from the account connected to the detail you want changed. Explain whether the issue concerns your phone, email, verification result or receipt reference, and we will assess the correction request.

Retention depends on the type of record and the operational, dispute or legal period that applies. Account activity, wallet references and support messages may therefore have different retention periods.

Use the signed-in support path and mention the device change without sending a password or one-time code. We may ask security questions before discussing account data or changing access details.