Reference

Privacy Policy for abatoto accounts

abatoto's Privacy Policy explains what we collect when you open an account, sign in on mobile, verify your phone, or use DANA and QRIS through the cashier.

Clear data purposesWallet activity explainedPhone access coveredPolicy contact route
abatoto Privacy Policy for abatoto accounts
PRIVACY HELP PATH

Where to ask about privacy changes

A direct privacy question should reach a clear account contact path, not disappear beside a wallet status message.

Account contact Use the support path inside your account when you want to ask about a…
Wallet query For a DANA, OVO, GoPay or QRIS privacy question, include the payment reference and…
Policy request When you request a copy, correction or removal of eligible data, write the request…
DATA HANDLING

How abatoto handles your account data

Privacy work is tied to practical account steps: phone verification before access, device checks during sign-in and transaction matching when a wallet reference is supplied.

Account details

We may hold the name, phone number and sign-in details you submit when opening an account. These records help us identify your profile, complete phone verification and respond to an access request made through the account area.

Device signals

Your browser, device type and sign-in signals can be recorded to protect account access and identify unusual attempts. The mobile path may show different session details from desktop, while the purpose remains account security.

Cookies

Cookies and similar browser storage can keep a session working, remember selected settings and help us understand whether a page loads correctly. You can manage browser controls, although changing them may affect sign-in continuity.

Payment records

A DANA, OVO, GoPay or QRIS reference may be linked with your account when you use the cashier. Bank transfer and virtual account records can be retained for matching, status checks and support replies.

Security controls

Phone verification, sign-in checks and limited access to account records help reduce exposure of your details. We ask you to keep your phone and account credentials private because our checks cannot replace careful device use.

Retention requests

We retain records only for the purposes described in the Privacy Policy and for periods needed to resolve account, security or transaction questions. Ask us to correct or remove eligible data through the policy contact route.

Privacy Policy questions for Indonesian accounts

These answers address the searches we hear most often before an account is opened or a wallet is connected. If your situation involves a specific phone verification, device session or payment reference, use the account support path so we can check the relevant record without exposing unrelated details.

It covers account details, phone verification, device and browser signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains access, retention, security and requests to correct or remove eligible data.

Your phone number helps us identify the account you are opening, complete the phone verification step and respond to access questions. We may use it to connect your support request with the correct profile, but you should not send your verification code to anyone.

Yes. The Privacy Policy covers device type, browser details and sign-in signals used to keep an account session working and help identify unusual access. Mobile and desktop may produce different technical records because each device handles sessions and storage differently.

When you use DANA or QRIS, we may retain the payment reference, time and related account status to match a cashier event and answer a receipt question. The reference helps us check the transaction without requiring broad access to unrelated profile details.

You can contact us through the signed-in account support path and state whether you want a copy, correction or removal of eligible data. Include your linked phone number and the specific record concerned; we may verify account ownership before making a change.

Retention depends on why the record was created and whether it is needed for account security, transaction matching or a support question. Our Privacy Policy explains the applicable purpose, and you can ask the policy contact route about a particular record.

Account access and related data handling are available where local law permits. If a local rule affects eligibility or a request, we apply that requirement and explain the available path through support. The Privacy Policy remains the place to check the applicable terms.