Reference

antri bet Privacy Policy for Your Account

Your antri bet Privacy Policy explains how we handle account details connected with Live Blackjack Diamond, DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record contextAccount contact pathCookie choices
antri bet antri bet Privacy Policy for Your Account
CONTACT ROUTES

Three Ways to Ask About Privacy

A clear contact route matters when your account record or wallet status needs checking. We keep privacy questions separate from game or payment troubleshooting so your request reaches the right internal path.

Privacy request Ask us to explain the personal data connected with your account, including phone verification records, sign-in events and payment references. We will use the account contact detail you provide to locate the correct record before replying.
Correction request If your account name, phone detail or contact record is inaccurate, tell us what needs changing and why. We may compare the request with your existing account step before applying an update or asking for more evidence.
Access concern When a login, QRIS receipt or wallet status appears on the wrong account, contact us through the available support path with the reference and time. We can investigate the record while limiting disclosure until your identity is checked.
DATA PRACTICES

How We Handle Six Privacy Points

Our privacy process follows the same account path you use: phone verification, sign-in, wallet activity and support contact.

Account details

We may store your registration contact, phone verification result and account status so we can recognise your account during sign-in. We use these details for access, support and security checks rather than treating every device session as a new account.

Payment references

DANA, OVO, GoPay and QRIS may appear as transaction references connected with your account. Bank transfer and virtual account records can also be retained for reconciliation, receipt checks and questions about a payment status.

Device signals

Browser type, operating system, language setting and session timing can help us identify failed access or unusual activity. We do not need to inspect unrelated files on your phone, and mobile access does not require a separate app.

Cookies

Cookies can keep a sign-in session, remember basic preferences and support page security. You can clear or block them in your browser settings, although doing so may remove saved session details and require another account sign-in.

Retention

We retain account, support and payment records for as long as needed for their stated purpose, security checks, dispute handling or a lawful obligation. When a record is no longer needed, our process is to delete or limit it where practical.

Your request

You can ask what personal data we hold, request a correction or ask about deletion where applicable. Send the request through our privacy contact path with your account detail; we may verify ownership before taking action.

Privacy Policy Questions From Indonesia

These answers address the privacy searches we expect before an account is opened or a wallet record is checked. They explain how the antri bet Privacy Policy relates to account steps, mobile access, payment references and contact requests. If your situation is not covered, use the privacy contact path and include enough detail for us to identify the relevant record.

It covers account registration details, phone verification, sign-in activity, device signals, cookies, support messages and payment references. DANA, OVO, GoPay, QRIS, bank transfer and virtual account records may be connected with your account when needed for status checks or reconciliation.

Phone verification helps us connect the correct person with an account and reduce unauthorised access. We may use the verification result during sign-in, privacy requests or a correction request. Account access depends on local law and the applicable eligibility conditions.

Yes. The Privacy Policy includes browser type, operating system, language setting, session timing and cookies when those details help maintain access or investigate a failed sign-in. We do not need to inspect unrelated files on your phone, and no separate app is required.

We use DANA and QRIS references to match an account with a payment status, investigate a receipt question and identify unusual activity. We may handle OVO, GoPay, bank transfer and virtual account references in the same operational way, limited to the stated privacy purposes.

Yes. Contact us with the account detail connected to the record, explain what is inaccurate and provide the corrected value. We may verify account ownership before changing a phone, name or contact record, which helps prevent another person from altering your details.

We keep information for as long as it serves the purpose described in this Privacy Policy, supports account security, resolves a dispute or meets a lawful obligation. When retention is no longer needed, we aim to delete or restrict the record where practical.

Use our privacy contact path and include the account contact detail, request type and relevant date or reference. We can help with access, correction, deletion where applicable and questions about cookies. We may request an account step before disclosing personal records.