Reference

Open top1to Privacy Policy Clearly

top1to Privacy Policy explains how we collect, use, protect and retain details connected with your account, device access and wallet activity.

Account dataWallet recordsDevice accessPolicy requests
Explore Our Lobby Read FAQ
top1to Open top1to Privacy Policy Clearly
CONTACT ROUTES

Check Privacy Questions Through Support

A clear contact route helps you ask what we hold, why we use it and how a correction should be handled.

Account request Use the account support path to ask for a copy, correction or explanation of personal details connected with your top1to account. Include your registered phone or email, and we will use an account check before discussing records or changing the information attached to access.
Wallet record For a privacy question involving DANA, OVO, GoPay or QRIS, provide the relevant payment reference rather than sending a full wallet password or security code. We can review the transaction trail, explain its purpose and keep sensitive credentials out of the request.
Access concern If a phone verification step, browser session or device sign-in raises a privacy concern, tell us which step appeared and when. Our support route can review the access event, confirm the account path and explain what security data was used.
DATA PRACTICE

Explore How We Handle Account Data

The practical side of privacy sits inside ordinary account operations: a phone check before access, a session record when you sign in, and a payment reference when a wallet status needs checking.

Account collection

We collect the contact and verification details needed to create your account and confirm that the sign-in request belongs to you. A phone verification step can connect access with the correct account, while basic session records help us investigate failed or unusual entry attempts.

Device signals

Your browser or mobile device may provide session, language, time and security signals when you open the account path. We use these details to keep the session working, identify access problems and check unusual activity, not to treat your device as a separate account.

Cookie use

Cookies and related storage can remember an active session and help the account path load correctly when you move from sign-in to a lobby page. You can manage browser controls, although limiting these tools may interrupt access checks or require another sign-in.

Payment records

A DANA, OVO, GoPay or QRIS reference lets us match a wallet event with the correct account without asking you to share a wallet password. Bank transfer and virtual account references serve the same checking purpose when a payment status needs investigation.

Retention approach

We retain account, security and transaction records for the period needed for account operation, dispute handling, security checks and legal duties that apply where access is provided. The applicable retention reason is part of our policy response when you ask about a specific record.

Change request

Ask us to correct an inaccurate detail or explain how a record is used through the account support route. We may verify your phone or email first, then confirm the request, explain any required retention and tell you what action can be taken.

Find Privacy Policy Answers For top1to

These Privacy Policy answers address the questions that usually arise before account access: what data is collected, how wallet references are handled, what a device contributes, how long records remain and where to send a request. We keep each answer tied to the account process rather than describing unrelated lobby features. If your situation involves local eligibility, access depends on local law, and our support route can explain which account step applies.

The top1to Privacy Policy covers account details, phone verification, device and session signals, cookies, payment references, security events and support requests. It explains why we use each category, how it supports account access and payment checks, how records are retained, and how you can ask about or correct your data.

We do not need your wallet password or security code to check a payment status. We use the account and transaction reference supplied through the payment path, such as a DANA, OVO, GoPay or QRIS reference, so a support request can be matched without exposing wallet credentials.

The Privacy Policy covers practical device and browser signals such as session timing, browser context, language and security events. These details help preserve sign-in, identify an unusual access attempt and diagnose a failed mobile path. They do not replace the account details used for phone verification.

Use the account support path and identify the phone number or email connected with your account. State whether you want a copy, correction or explanation, and include a payment reference only when relevant. We may verify account ownership before discussing records or applying a change.

Retention depends on the reason for the record, including account operation, security review, payment reconciliation, dispute handling and legal duties that apply where access is provided. Ask support about a specific account or wallet record, and we will explain the applicable purpose and retention position.

Yes. Phone verification helps connect an access request with the account details supplied during registration and can protect against an unfamiliar sign-in. Send the question through support with the affected step and approximate time. We can explain the data used for that check without requesting your security code.

The Privacy Policy applies to the account and data activity connected with supported Indonesia access, while eligibility depends on local law. If you are in Jakarta, Surabaya or another location and need clarification, contact support with your account route so we can address the relevant access and data question.

Related Pages

top1to Indonesia top1to Casino Live Blackjack Royal FAQ Account information