Reference

Privacy Policy For Your Indonesia Account

Privacy Policy for antena 66 slot shows how we handle your account details, wallet references and device access before you open the lobby.

Clear data purposesWallet reference controlsAccount access requests
antena 66 slot Privacy Policy For Your Indonesia Account
CONTACT ROUTES

Ask About Your Account Data

A direct request helps us locate the correct account record without asking you to send unnecessary documents. Use the support route shown in your account area and include the email or phone detail attached to your account, plus the data question you want answered. We can then check identity, wallet references and device records in the right context.

Team online

Account message

Send a Privacy Policy question from the account contact route and state whether you need access, correction or deletion details. We use the account identifier you provide to avoid attaching a response to the wrong profile.

Wallet status query

For DANA, OVO, GoPay or QRIS records, include the transaction reference rather than your wallet password or full security code. We can investigate the stored payment reference and explain its purpose without requesting secret wallet credentials.

Access assistance

If the phone verification step blocks your account, tell us which device path you used and where the message appeared. We can explain the data check connected with access, while any eligibility decision depends on local law.

DATA PRACTICE

Data Handling And Account Security

We keep this policy practical by linking each data category to an account task you can recognise.

Account details

We use the contact details you submit to identify your profile, send account-related replies and complete the phone verification step before access. If your phone number or email changes, request a correction through the account contact route rather than opening a second profile.

Payment references

A DANA, OVO, GoPay or QRIS reference can appear in our records when you ask us to check payment status. Bank transfer and virtual account references serve the same checking purpose; we do not need your wallet password for this process.

Device records

When you move from login to the mobile lobby, limited device and connection details may help us recognise unusual access or diagnose a failed session. These records are used for account protection and technical support, not as a substitute for your identity details.

Cookies

Cookies and similar browser records can keep an account session working, remember a selected setting and help us understand an access error. You can manage browser permissions on your device, although changing them may affect login continuity or the way the lobby loads.

Retention

We retain account, support and payment-reference records only for as long as they serve an account, security, dispute or legal purpose. A retention request should identify the relevant account step, because different records may have different storage periods under local requirements.

Changes and requests

You can ask us to access, correct or explain personal data held about your account. We may first confirm that you control the profile, then tell you what action is available; requests involving eligibility or deletion depend on local law.

Privacy Policy Questions For Indonesia

These Privacy Policy answers address the account and payment questions we expect from Indonesian customers before they use antena 66 slot. Each answer points to a practical step: phone verification, wallet references, browser settings, data requests or the support route. If your situation is different, contact us with the account detail needed to locate the record.

It covers account details, phone verification, device access records, cookies, support messages and payment references linked with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, data requests and how we respond when you ask about a specific record.

Phone verification is an account access step, so the Privacy Policy explains the related data purpose. We may use the submitted number to identify your profile and protect access. If the check fails, contact us with the device path and the message shown.

Our Privacy Policy does not require your DANA, OVO, GoPay or QRIS password for a payment-status question. We use a transaction reference or related account detail instead. Never send a wallet password, security code or one-time code through a support message.

Yes, you can ask what personal data we hold about your account and why it is used. Send the request through the account contact route with your profile identifier. We may verify account control first, and the response depends on local law.

Cookies can support login continuity, selected settings and diagnosis of a failed mobile session. You can change cookie permissions in your browser or device settings. Limiting them may affect access flow, and our Privacy Policy explains the related purpose rather than treating cookies as account consent.

Use the account support route and identify the detail that needs correction, such as a phone number or email address. We may ask for an account-control check before changing it. Do not send wallet passwords or full payment security credentials with the request.

Send a retention question through the same support contact path and mention the record type, such as a QRIS reference, device session or account message. We can explain its purpose and applicable storage period; some retention duties depend on local law.