Reference

Privacy Policy For Your top4top Account

Our Privacy Policy explains how top4top handles the details you provide when you open an account, verify your phone and move between the lobby and wallet screen.

Clear data purposesPhone check detailsWallet record contextCookie choices
top4top Privacy Policy For Your top4top Account
CONTACT PATHS

Privacy Help Near Your Account

A clear contact path helps when you need to ask about personal data rather than a lobby title.

Account support Use the support route attached to your signed-in account for a Privacy Policy question. Tell us whether your request concerns phone verification, a mobile browser session or a stored account detail, and we can direct it to the right handling path.
Wallet record check When your question involves DANA, OVO, GoPay or QRIS, mention the payment rail and the account step that produced the record. We use that context to locate the relevant reference without asking you to send an unnecessary wallet password or full payment credential.
Account ownership Before we disclose, correct or remove personal data, we may ask you to complete the same phone verification step used for account access. This protects your records when a request arrives from a new device or an unrecognised session.
DATA PRACTICE

How We Handle Your Privacy Requests

We keep this Privacy Policy practical by connecting each data use to an account event you can recognise.

Account details

We use the account details you submit to create and maintain your sign-in record, connect a verified phone number and respond to requests made through account support. If a detail changes, ask us to correct it after confirming ownership of the account.

Phone verification

The phone verification step links access to the account holder and helps us distinguish an authorised sign-in from an unfamiliar request. We may retain the verification result and related event time so a later privacy request can be checked properly.

Device sessions

When you move from login to the lobby on a mobile browser, we may process device, browser and session signals. These details help us investigate access questions, identify an active session and respond when you report a sign-in you do not recognise.

Cookies

Cookies may keep a session active, remember a browser preference or help us understand whether a page request belongs to the same visit. You can manage cookies through your browser controls, although changing them may affect account access or saved session choices.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can be used to match a wallet question to the right account event. We ask for the reference needed for that check, not an unnecessary password or complete card credential.

Retention and requests

We retain records for the period needed to support account access, resolve a payment-status question, protect the service and meet applicable legal duties. Contact us through account support to ask what we hold, request a change or ask about deletion limits.

Privacy Policy Answers For top4top

These Privacy Policy answers address the account questions you are most likely to have before opening an account or contacting support. They explain the practical records behind phone verification, mobile access, cookies, wallet references and data requests. Our response can depend on the account details available and on where local law permits access.

The top4top Privacy Policy covers details you submit for account creation, phone verification and support. It also addresses device session signals, cookie records and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account checks.

Phone verification connects the account with a confirmed contact route and helps us assess whether an access or privacy request comes from the account holder. We may keep the result and event time so later requests can be checked against the original account step.

Yes. The Privacy Policy covers device, browser and session signals created when you sign in through a mobile browser and move toward the lobby. These records help us investigate unfamiliar access and do not replace the account details required for ownership checks.

We use a payment reference or status detail to connect a support question with the correct account event. The Privacy Policy does not ask you to send a wallet password. Share only the rail name and reference needed to examine a DANA, OVO, GoPay or QRIS question.

Yes. Send a correction request through the account support path and explain which account detail is wrong. We may ask you to complete phone verification or another ownership check before changing the record, especially when the request comes from a new device.

We keep records for as long as needed to support account access, examine a wallet-status request, protect account security and meet applicable legal duties. The period can vary by record type. Ask through account support for details about a particular data category.

Use the support route connected to your account and describe the privacy issue clearly, such as cookies, phone verification, a device session or a QRIS reference. We may need account ownership details before discussing personal records, and access depends on local law.