Reference

Privacy Policy For Your top12 Account

Our Privacy Policy explains which account, device and payment details we use when you open top12 in Indonesia.

Account dataWallet recordsCookie choicesPrivacy requests
top12 Privacy Policy For Your top12 Account
HELP WITH PRIVACY

Get Clear Answers About Your Data

A privacy question should have a clear route, especially when it involves a wallet receipt or a phone verification step. Use the account support path beside the cashier area and describe the record you want us to locate. We can match a request using your account details, payment reference or device session without asking you to send a password. If your question concerns a QRIS receipt from Yogyakarta, include its date and reference so we can narrow the search.

Team online

Account request

Send a privacy request from the account support path beside the cashier area. Include your registered phone number and the specific record you want checked, such as a login event or phone verification entry. We use those details to identify the correct account without requesting your password.

Wallet record

For DANA, OVO, GoPay or QRIS questions, attach the payment reference rather than a wallet password. We use the reference to locate a status or receipt record, then explain what was retained and why. Bank transfer and virtual account requests follow the same account-matching step.

Access concern

If a privacy request is blocked by a sign-in or phone verification issue, mention that in the support path. We can separate an account-access problem from a data request and ask only for the details needed to confirm the account holder before responding.

DATA HANDLING

How top12 Handles Privacy Requests

We handle privacy through practical account controls rather than vague promises. Session data helps us recognise the device path from phone login to the lobby, while payment references help us reconcile a…

Account records

When you open an account, we keep the details needed to create your profile and complete phone verification. A correction request should identify the field that is wrong. We can then compare the request with the account record and explain which changes are available under this Privacy Policy.

Device signals

A phone or desktop session may produce device and browser signals linked to login activity. We use them to recognise unusual access and protect the account, not to request your device password. Clearing cookies can require a fresh sign-in and another phone verification check.

Cookie choices

Cookies help keep a signed-in path available and remember selected account settings. If you remove them in your browser, some privacy and account preferences may need to be selected again. The policy contact path can explain which cookie category relates to your request.

Payment references

DANA, OVO, GoPay and QRIS status may be connected to a payment reference, while bank transfer and virtual account records can carry their own reference. We use those identifiers for matching and reconciliation; send the reference when asking us to locate a receipt.

Retention request

You can ask why a particular account, login or payment record remains stored. We assess the request against active account needs, security checks and local requirements, then explain whether the record can be corrected, restricted or removed.

Contact changes

To request a copy, correction or deletion of eligible data, use the account support path and state the action clearly. We may ask you to confirm the registered phone number before making a change, so another person cannot alter your privacy record.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we expect before you open or use a top12 account in Indonesia. They explain the records connected to login, phone verification, cookies and local payment references without turning the page into a general lobby description. For a personal request, use the support path and identify the account record, device event or receipt you want us to check.

The top12 Privacy Policy covers account details, phone verification, device and browser signals, cookies, support requests, payment references and security records. It explains why we use each category, how retention is assessed and how you can ask for correction, a copy or removal where the request is eligible.

We do not ask for your wallet password through a privacy request. The account may retain a payment reference, status or receipt detail for DANA, OVO, GoPay or QRIS so we can match a transaction question. Send the reference, never a password, when contacting support.

Phone and browser signals help connect a session to the correct account and identify unusual login activity. They can also affect cookies when you move between a phone and desktop. Clearing browser data may require another sign-in or phone verification before account access continues.

Use the account support path and state whether you want a copy or a correction. Include your registered phone number and the specific account field, login event or receipt reference. We may confirm account ownership before responding so the request stays connected to your record.

Retention depends on the purpose of the record, including account operation, security checks, payment reconciliation and an open privacy request. We assess deletion or restriction requests against those needs and local requirements, then explain why an eligible record can or cannot be removed.

You can remove cookies through your browser settings and ask us which account preference or session record relates to your request. Removing cookies may sign you out or require phone verification again. Some records connected to security or an active request may remain separately from browser cookies.

Yes. Account availability, privacy handling and any access or eligibility decision depends on local law. If you contact us from Indonesia about a data request, we use the account and payment details needed to assess it and explain the applicable path without asking for your wallet password.