Reference

alksitoto Privacy Policy for Your Account

alksitoto Privacy Policy explains what we collect when you open an account, sign in from a phone, browse Auto Roulette or Book of Dead, and use DANA or…

Account dataWallet recordsDevice choicesPrivacy requests
alksitoto alksitoto Privacy Policy for Your Account
CONTACT ROUTES

Ask About Privacy Through Your Account

A clear contact path helps you act on the Privacy Policy without searching through unrelated pages. We handle requests about stored data, account access and wallet references through the support contact shown after sign-in. Include your account identifier and the exact request, while keeping passwords, one-time codes and full payment credentials out of the message.

Team online

Data access request

Use the signed-in support contact to ask which account details we hold. We may request an account step or phone verification so the response reaches the right person, not a stranger.

Wallet record question

For DANA, OVO, GoPay or QRIS records, send the payment date, rail name and visible reference. We use those details to locate the transaction without asking you to share a password.

Correction request

If your phone, email or account detail needs changing, contact us from your account area and describe the correction. We check the request before updating records linked to account access.

DATA PRACTICE

Browse How alksitoto Handles Privacy

Privacy work is tied to practical account events rather than broad promises. We separate sign-in details from payment references where possible, limit access to staff who need it for a stated task…

Data collection

We collect details you provide during account opening, including contact data and phone verification, plus sign-in and transaction references. Browsing Auto Roulette, Bingo or Mega Fishing may create activity records used for account operation.

Cookie choices

Cookies and similar device storage can keep a session active, remember selected settings and help us detect unusual sign-in patterns. You can manage browser permissions, though some account access steps may then need repeating.

Account security

Phone verification helps connect an account request to its owner. We do not ask for your password or one-time code through a privacy message, and you should end a session when using a shared phone.

Retention periods

We keep account, payment and support records for the period needed to operate the account, resolve disputes, meet legal duties or protect against misuse. When a record is no longer needed, our process removes or separates it.

Who receives data

Access is limited to service workers and payment or security processes that need a particular record. A DANA reference, for example, is used to match wallet status rather than expose unrelated game activity.

Requesting changes

You can ask us to access, correct or clarify personal data through the signed-in support route. State the request plainly, mention the affected account step and expect identity checks before any change is made.

Find Privacy Policy Answers Quickly

These Privacy Policy answers focus on the questions that arise before account access or during a wallet check. If your situation is not covered, use the support route visible in your signed-in account and describe the exact data or device event involved.

It covers account details, phone verification, sign-in events, cookies, device data, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

Phone verification helps us connect an account request to the correct account holder, reduce mistaken access and investigate sign-in questions. We use it as an account check, not as permission to request your private code.

Yes. The policy covers session details, browser settings, device signals and cookie choices used during mobile access. These details can help keep a casino session active or flag an unusual sign-in.

We record the reference and status needed to match a DANA or QRIS payment with your account. We do not need your wallet password, and you should not place one-time codes in a support request.

Yes. Send an access or correction request through the signed-in support contact, identify the affected account detail and complete any identity check. We use the check to prevent another person changing your records.

We retain records while needed for account operation, payment matching, dispute handling, security or legal duties. Once a record is no longer needed, our process removes it or separates it from active account use.

The policy is available for account questions, but access or eligibility depends on local law. If a local rule affects your account or data request, contact us through the signed-in support path.