Reference

antiktoto Terms & Conditions for Account Access

One clear account path covers phone verification, wallet records and access to the casino, sportsbook and lobby rules in our Terms & Conditions.

Clear acceptance stepsPhone check before accessIndonesia policy contextLocal-law access wording
antiktoto antiktoto Terms & Conditions for Account Access
POLICY HELP ROUTES

Three Ways To Resolve Policy Questions

A clear support path helps when a Terms & Conditions question affects login, wallet status or an account change.

Account access Use the support path when phone verification or login does not match your account record. Tell us the device path you used, such as mobile browser to lobby, so we can locate the policy step.
Wallet status For DANA, OVO, GoPay or QRIS questions, send the payment reference and the wording shown beside the cashier. We use those records to explain whether a transaction is pending, rejected or awaiting confirmation.
Policy changes If you want to question a rule or request an account correction, contact us through the site support route. Include your registered phone detail and the specific Terms & Conditions clause you mean.
ACCOUNT CONTROL

Six Controls Behind Our Account Policy

We keep the policy practical by connecting each rule to an account action you can recognise. Phone verification comes before account access, wallet references stay tied to the relevant record, and changes…

Data handling

We use the account details you submit to operate access checks, payment matching and support replies. Our Terms & Conditions explain why those details are needed and how they relate to your account activity.

Cookies

Cookies can preserve session settings and help connect your browser to the correct account path. The policy explains their role, so you can understand what changes when cookies are cleared.

Account security

Keep your phone access and account credentials private. If another person uses your device or login, tell support promptly; the Terms & Conditions describe checks we may make before changing account details.

Record retention

Payment references, verification events and support exchanges may be retained for the period needed to administer the account and apply the policy. We describe this handling without assigning an invented fixed period.

Who to contact

The site support route is the correct contact for questions about acceptance, access, wallet matching or account corrections. A focused message helps us connect your request with the right policy clause.

Change requests

To request a correction, state the account detail you want changed and why it is inaccurate. We may ask for phone verification before applying an update under the Terms & Conditions.

Terms & Conditions Questions You May Search

Before you open an account, these Terms & Conditions answers cover the practical points most likely to affect access in Indonesia. We keep the route direct: read the clause, complete the requested account step and contact support if your record or payment reference needs checking.

They cover account opening, phone verification, access rules, payment records, account security, cookies, data handling, support requests and policy changes. Access depends on local law and the location connected to your account.

Yes. You review and accept the Terms & Conditions during the account path before access is enabled. We may require phone verification first, including when you use a mobile browser.

DANA and QRIS are listed local payment rails, alongside OVO, GoPay, bank transfer and virtual account. The relevant rule is that your payment reference and account details must match.

Phone verification connects the account to a contact detail you control and supports account-security checks. We may request it before access, a correction or a payment-related account action.

Contact support through the site route and identify the inaccurate field. We may ask you to confirm the registered phone detail before changing the record under the Terms & Conditions.

The rules remain tied to your account, but browser cookies and session status can affect the access path. If mobile login differs from desktop access, support can check the relevant session record.

Send support the clause or wording you mean, plus the account step where it appeared. We can explain the policy context and tell you what account or payment record is needed.