Reference

topi4d Privacy Policy For Your Account

Phone verification, wallet status and device access are the practical parts of our Privacy Policy.

Phone verificationWallet dataDevice choicesYour privacy rights
topi4d topi4d Privacy Policy For Your Account
PRIVACY HELP ROUTE

Privacy Help Beside Your Wallet Status

A privacy request should not get lost beside a payment question. From your account help path, tell us whether you need a copy of your account details, a correction, or clarification about…

Account access request Ask for the account details connected with your phone verification. We check ownership first, then explain the available response and any limits that depend on local law.
Wallet receipt question Send the payment reference when a DANA, OVO, GoPay or QRIS receipt needs checking. We use the reference and account status rather than asking for your wallet password.
Correction request If your phone, profile or device detail is inaccurate, use the account help path to request a correction. We may ask for a verification step before changing the record.
DATA HANDLING PRACTICE

How topi4d Handles Account And Device Data

We keep our privacy process close to the account actions that create each record. Login events, phone verification, wallet references and device signals are separated by purpose, so a support check does…

Account details

We use your phone number and verification status to create and protect account access. We do not treat a wallet password as part of the account record we need for payment matching.

Device signals

Browser, operating system and login-event details can help us spot an unfamiliar device. On mobile, these checks support the path from login to the lobby without reading unrelated device content.

Cookies

Cookies can keep a session working and help us understand security events. Your browser settings can control cookies, although changing them may affect account access or saved preferences.

Payment matching

For QRIS, DANA, OVO, GoPay, bank transfer and virtual account activity, we retain references and status needed to match a receipt. We do not ask for private wallet credentials.

Retention

We keep records only for the period needed for account support, security checks and legal duties. When a record is no longer needed, our handling follows the applicable retention process.

Your requests

You can ask who handles a record, request a copy, seek a correction or ask about removal. We verify account ownership and respond according to the rights available under local law.

Privacy Policy Answers For DANA And QRIS

These Privacy Policy answers focus on the account steps you are most likely to question before opening access. We cover phone verification, mobile browsing, wallet references, cookies, retention and the route for asking about your records. If a request concerns eligibility or access in Indonesia, the result depends on local law.

It covers account details, phone verification, login events, device signals, cookies, wallet references and support records created when you use the service where local law permits.

No. Our Privacy Policy describes retaining payment references and status for DANA or OVO matching, not your private wallet password. Never send wallet credentials through an account help request.

Phone verification helps us confirm account ownership before access or a privacy change. It also gives our support path a practical way to separate your request from another account.

We may handle browser type, operating system, approximate access time and security events. These details help identify unusual login activity when you move between a mobile device and desktop.

Yes. Use the account help path and describe the record you want copied or corrected. We verify ownership first, then handle the request within the rights and limits set by local law.

We retain the QRIS reference, amount status and related account link needed to check a receipt. This lets support investigate a stalled wallet status without requesting your QRIS credentials.

Retention depends on the purpose of the record, such as security, account support or a legal duty. Our Privacy Policy explains that records are removed or handled differently when no longer needed.