Reference

akslot Privacy Policy For Your Account

akslot Privacy Policy explains how we collect, use and protect the details needed for your account, including phone verification, device access and wallet status.

Clear data purposesWallet status contextCookie choices
Explore Our Lobby Read FAQ
akslot akslot Privacy Policy For Your Account
POLICY HELP PATH

Get Privacy Policy Help From Your Account

A clear support route matters when you want to understand a data field, correct an account detail or ask about a payment reference.

Account questions Use the account help path when your Privacy Policy question concerns phone verification, sign-in records or a detail shown in your profile. We use the account context to locate the relevant record, while you should keep passwords, one-time codes and complete wallet credentials out of your message.
Wallet references If your question involves DANA, OVO, GoPay or QRIS, share the date, amount reference and visible status rather than private wallet credentials. Our support path uses those limited details to check whether the issue concerns an account record, a receipt match or a pending status.
Access requests For a copy, correction or removal request under the Privacy Policy, state the account phone number and the specific data action you want. We may ask for an account check before making changes, so another person cannot request control of your account information.
DATA HANDLING DETAILS

How akslot Handles Privacy Requests

We keep our data handling practical: account details support access, device signals help protect sign-in activity, and payment references help us reconcile wallet status.

Account records

We use the phone number and verification result connected with your account to support sign-in and account recovery. Keeping these records together helps us distinguish your request from another account. If a detail is wrong, ask us to correct it through the account help path.

Device activity

A mobile sign-in can create device and session signals used to detect unusual access and protect your account. These signals are not a reason to collect unrelated content from your phone. Your browser and device settings remain the place to manage local permissions.

Cookie controls

Necessary cookies can keep your session and policy choices working between pages. Where optional cookies are used, your browser controls can clear or restrict them. Clearing storage may sign you out or remove a saved preference, so check the Privacy Policy again after changing settings.

Payment matching

DANA, OVO, GoPay and QRIS references help us connect a receipt or status check to the correct account activity. We do not need your wallet password for that task. Bank transfer and virtual account references are handled for the same account-matching purpose.

Retention logic

We retain account and security records only as long as they support the stated purpose or a continuing legal, dispute or security need. The exact period can depend on the record type and local requirements. Ask through support if you need the retention basis for a specific record.

Change requests

You can ask us to access, correct or delete eligible personal data by naming the account detail and requested action. We verify ownership before responding. Some records may remain when needed for security, dispute handling or a requirement that depends on local law.

Privacy Policy Questions About akslot

These Privacy Policy answers address the account questions you may have before opening access or while checking your profile. We keep the wording tied to actual account steps, mobile sessions and Indonesian wallet references. If your situation is not covered, use the account support path and describe the record or request clearly. We will confirm what can be handled and whether any restriction depends on local law.

The akslot Privacy Policy explains how we collect and use account, phone verification, device, cookie and payment-reference data. It also covers security handling, retention, your access or correction requests and the way we respond when a request concerns DANA, QRIS or another supported payment rail.

We use your phone number to create the account connection, complete phone verification and support sign-in checks. It helps us identify the correct account when you request a correction or ask about a wallet status. Do not send your password or one-time code in a support message.

Yes. The Privacy Policy covers payment references and status details connected with DANA, OVO, GoPay and QRIS. We use those details to match receipts and account activity, not to request wallet passwords. Bank transfer and virtual account references may be handled for the same matching purpose.

Use the account help path and state whether you want access to a record or correction of a specific detail. Include your linked phone number and enough context to locate the record. We verify account ownership first, then explain the response and any restriction that depends on local law.

You can ask us to delete eligible account data through the support path. We first check that the request comes from the account holder. Some information may need to remain for account security, dispute handling or a continuing legal need, and we will explain that basis when it applies.

Necessary cookies can keep your session and policy settings available as you move between account pages. Browser controls can clear or restrict optional cookies. After clearing storage, you may need to sign in again or make a policy choice again before checking your account.

Yes. Some access, retention or deletion outcomes depend on local law and the type of record involved. We assess your request against the account context and applicable requirement, then explain what we can provide. Service access or eligibility also depends on local law where relevant.

Related Pages

akslot Indonesia Badminton Malaysia Open Bet Live Blackjack Diamond About Us Account information