Reference

top1top Privacy Policy For Your Account

Our Privacy Policy explains how top1top handles the account details you provide before you enter the lobby, including phone verification, wallet status and device access.

Clear data purposesPhone verification contextIndonesia access rulesAccount contact path
top1top top1top Privacy Policy For Your Account
PRIVACY HELP DESK

Where To Ask About Your Data

A direct support route helps when you need to understand an account record rather than guess which team handles it. Contact us through the account support channel for a data question, include the phone number linked to your account, and describe whether the issue concerns login, wallet status, cookies or a correction request. We use the details you send to locate the right record without asking you to post private data publicly.

Team online

Account support

Use the signed-in support path for a Privacy Policy question about your phone verification, login record or account details. Include the relevant date and the phone number linked to your account so we can identify the request with fewer follow-up messages.

Wallet status

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the transaction reference through support rather than sharing a screenshot in an open channel. We can check the account match and explain which record needs correction.

Access questions

For a request from outside your usual device, tell us the device type, approximate login time and account phone number. We can explain the security check, access wording and next step while keeping the request tied to your own account.

DATA HANDLING

What Our Privacy Process Covers

We apply this Privacy Policy to the practical moments where your account creates data: opening access, confirming a phone number, signing in from mobile, contacting support and checking a wallet reference.

Account details

We collect details such as your phone number and account identifiers to create access, complete phone verification and respond to account questions. We use those details for the stated account purpose rather than treating every piece of data as open-ended platform content.

Device signals

A mobile or desktop login can create device and session records, including timing and security signals. We use them to recognise an unusual access pattern, investigate a login problem and help protect your account without asking you to repeat the full account process.

Cookies

Cookies and related session tools help keep your account path working between login and the lobby. You can ask support which cookie or session purpose applies to your question, and our Privacy Policy explains how these tools relate to access and preferences.

Wallet records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create reference or status data linked to your account. We use the minimum transaction context needed to match a request, check a stalled status or address a payment record question.

Retention

Different records may remain for different periods because account security, transaction matching and support handling do not require the same timeframe. You can ask us which category applies to your request and why a particular record may still be retained.

Change requests

To request a correction, access copy or deletion review of your personal data, contact account support from your linked account where possible. State the request clearly, and we may ask for account verification before making a change or disclosing records.

Privacy Policy Answers For top1top

These Privacy Policy answers address the searches we hear most often about account records, device access and local wallet references. If your question is specific to your account, use the support path with your linked phone number and a short description of the record you want us to check.

The top1top Privacy Policy covers account details, phone verification, login and device records, cookies, support messages and payment references. It explains why we use each category, how we protect access, how retention works and how you can ask about a record or request a correction.

We use your phone number to create and identify your account, complete the phone verification step and connect support requests to the correct account. If you believe the number is wrong or no longer belongs to you, contact support from your account and request a correction.

Yes. The Privacy Policy covers account-linked payment references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We use this context to match an account action, investigate a stalled status and answer a specific record question.

Device and cookie data can maintain your session and help us identify unusual login activity. We use these signals for account access, security checks and session preferences. The Privacy Policy describes the purposes, and support can clarify which device or cookie record relates to your request.

Contact account support through the linked account where possible and state whether you want access, correction or deletion of a particular record. Include the relevant date or reference, but do not post private details in an open channel. We may verify account ownership before responding.

Retention depends on the type of record and its operational or security purpose. Account, support and transaction references may not share one timeframe. Ask support which category applies to your request and we will explain the reason a record may remain available.

Access and eligibility depends on local law. Use the service where local law permits, and contact support if you need the policy wording for your account situation. We can explain the access process and data question path without asking you to share private details publicly.