Reference

Legal clarity for your top12 account

top12 Legal explains how account access, identity checks, wallet records and policy requests work before you enter the lobby.

Account accessData choicesPolicy contact
top12 Legal clarity for your top12 account
CONTACT PATHS

Get policy help beside your account

A clear contact route helps when a Legal question affects your account, phone check or wallet record. Start from the support path shown in your signed-in account and include the email or phone detail connected to your profile, without sending a password. We use the subject of your request to direct it to account access, data choices or payment-status handling. If you are in Denpasar or elsewhere in Indonesia, the same policy route applies, provided access is allowed where local law permits.

Team online

Account access

If your phone verification or account step stops before the lobby opens, contact us through the signed-in support route. Tell us the device type and the message shown, so we can address access without asking you to share a password.

Data requests

For a copy, correction or removal request, use the Legal contact path attached to your account. Include the email or phone detail used at registration and describe the requested change; we may verify ownership before making an account record adjustment.

Wallet records

When DANA, OVO, GoPay or QRIS status does not match your account record, send the payment reference through support rather than posting it publicly. We use that reference to check the relevant transaction and explain the next policy step.

DATA PRACTICES

See how we handle Legal requests

We keep Legal handling practical: account data is linked to the profile you create, policy requests are checked against that profile, and access records are retained only as needed for account administration…

Data use

We use account details to connect your sign-in, phone verification and policy requests to the correct profile. Payment references from DANA, QRIS and other available rails are handled for status checks and account records, not treated as public content.

Cookie choices

Cookies can keep your account session available and preserve device settings. You can change cookie controls in your browser. If a required cookie is blocked, login or the move from login to the lobby may require another verification step.

Account security

Keep your password private and complete phone verification only through the account path. We do not need your password in a support request. If your device changes, sign in through the browser and check the account details before continuing.

Record retention

We retain account, contact and payment-status records for the period needed to operate the account, resolve disputes and meet applicable duties. A retention question can be sent through the Legal contact route for a case-specific response.

Who to contact

Use the Legal support route for questions about access, cookies, account records or policy wording. Include the account email or phone detail, but remove passwords, one-time codes and wallet credentials before sending your message.

Change requests

You can ask us to correct account details or clarify how a record is used. We may confirm account ownership first, then explain whether the requested change can be made under the applicable policy and local-law position.

Answers about top12 Legal access

These Legal answers cover the questions we expect before an account is opened or a policy request is sent. They explain the access condition, the account checks, the treatment of records and the route for asking us to correct or clarify something. If your case depends on a specific jurisdiction, contact us through the account support path.

top12 Legal covers account access, phone verification, policy wording, data choices, cookies, payment-status records and contact requests. Availability depends on local law, so you should check the current page before opening or using an account where local law permits.

Access depends on local law and is provided only where local law permits. If access is available, you follow the account path, complete the requested phone verification and use the device browser route shown at sign-in.

Phone verification helps connect the person completing the account step with the correct profile and reduces confusion when access or a wallet record needs checking. Do not send one-time codes to support; complete verification only inside your account.

DANA and QRIS references may be used to match payment status with your account when a transaction question is raised. Send the reference through the Legal support path, remove private credentials, and we will explain the relevant account-record step.

Yes. Send a data request through the Legal contact route and identify the email or phone detail linked to your account. We may verify ownership before providing a copy, correcting a record or explaining why a change cannot be made.

You can change cookie controls in your browser settings and then return through the account login path. Some session or lobby functions may require another sign-in when cookies are blocked. For a policy question, use the Legal support route.

Use the account support route linked to Legal and describe the decision, date and account detail involved. Do not include your password or one-time code. We will check the applicable policy wording and local-law position before responding.