Reference

Privacy Policy For Your anekatoto Account

Our Privacy Policy explains how anekatoto handles the account details, wallet records and device signals connected with your access.

Account clarityWallet recordsDevice choicesPolicy contact
anekatoto Privacy Policy For Your anekatoto Account
HELP WITH PRIVACY

Where To Ask About Your Policy Rights

A clear support route matters when you want to understand or change personal data held with your account.

Account access If phone verification or a sign-in check leaves you unsure about your data, use the account help path. Tell us which device step you reached and we can explain the relevant Privacy Policy process without requesting your password.
Wallet status For a DANA, OVO, GoPay or QRIS record, bring the payment reference and visible status from your account. Our support route can clarify what was stored, why a receipt was matched, and which policy request fits your case.
Policy request To ask for access, correction or removal where available, use the privacy contact route in your account help area. We may ask you to confirm account ownership before discussing personal data or applying a requested change.
DATA HANDLING

What We Do With Account Data

We keep this policy practical by connecting each data practice to an account action you can recognise.

Account details

We use the details you provide to create and maintain your account, support phone verification and connect your account with the lobby. We do not need unrelated profile details for you to ask a Privacy Policy question or request a correction.

Payment records

A DANA, QRIS, bank transfer or virtual account action can create a reference, amount status and matching record. We keep those details for account support, reconciliation and security checks, while the Privacy Policy explains the purpose behind each category.

Cookies

Browser cookies can help remember a session and support account navigation between sign-in and the lobby. You can manage cookie behaviour through your browser settings; changing those settings may affect how the account path remembers your device.

Device security

We may use device and sign-in signals to spot unusual access, protect phone verification and investigate an account request. These signals are not a reason to collect unrelated content from your device, and we explain their role when you contact support.

Retention timing

We retain account and payment records only for the period needed for the stated account, security, support or legal purpose. Retention can differ by record type, so ask through the policy contact route if you need the timing for a specific receipt.

Your changes

You can ask us to access, correct or remove eligible personal data, subject to identity checks and any legal need to retain a record. Include your account reference and the requested change; we will explain the next step through our support path.

Privacy Policy Answers For anekatoto

These Privacy Policy answers focus on the searches we hear most often before an account is opened. They cover the data attached to sign-in, wallets, cookies and support requests, with local access wording for Indonesia. If your situation involves a particular receipt or device, use the account help route and include that specific detail.

It covers account details, phone verification, payment references, cookies, device security signals, support records and retention. The Privacy Policy also explains how to request access, correction or removal of eligible data, subject to identity checks and any legal duty to retain a record.

Phone verification happens before account access so we can connect the sign-in request with the right account and reduce mistaken or unauthorised access. We use the verification detail for that account and security purpose, as described in the Privacy Policy.

Yes. The Privacy Policy covers payment references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. These records help match a receipt to your account and support security or reconciliation questions.

Use the privacy contact route in the account help area and state that you want data access. Add your account reference and the record type, such as a phone verification or QRIS receipt. We may confirm ownership before sharing personal data.

You can request a correction through the support path, explaining which account detail is inaccurate and what should replace it. We may check your identity and the source record first. The Privacy Policy sets out when a correction can be applied.

Retention depends on the type of record and the account, security, support or legal purpose that requires it. A wallet status and a support message may follow different periods. Ask through the Privacy Policy contact route for a specific receipt.

It applies to the account and data activity covered by our service in Indonesia where local law permits. Access and eligibility depends on local law. If you are in Jakarta or elsewhere, contact support when a regional rule affects your account or data request.