Reference

akai123 Privacy Policy: Clear Data Choices

Our Privacy Policy explains how akai123 handles your account details, wallet records and device signals when you access Live Roulette, Egypt Book of Mystery or other lobby areas.

Account dataWallet recordsCookie choicesAccess requests
akai123 akai123 Privacy Policy: Clear Data Choices
HELP WITH PRIVACY

Get Answers About Your Policy Request

A privacy question should not disappear inside a payment query. Use the support route shown in your account to ask about stored data, a wallet record or a correction request, and include the account phone number without sending a password. We can connect the request to the right account trail while keeping the conversation focused on this Privacy Policy.

Team online

Account data request

Ask us to identify the account data connected with your phone verification, login history or saved preferences. We will explain the request path before handling any change.

Wallet record question

For DANA, OVO, GoPay or QRIS records, share the transaction reference shown in your cashier history. Do not send wallet passwords, PINs or full security credentials.

Access and correction

If your account details look wrong or a device prompt blocks access, contact our support route from the account area. We will confirm identity before discussing private records.

DATA HANDLING

Your Data Choices Across Devices

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

Account details

We use your account identifiers and phone verification result to establish that the person requesting access is connected with the account. This reduces accidental disclosure during support conversations.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records help us match a wallet event with the correct account. We use status and reference details for this purpose.

Device signals

Browser type, device signals and login timing can help us notice an unfamiliar session. These checks support account protection and do not replace your phone verification step.

Cookies

Cookies can remember a session choice or help us understand whether a policy page was opened. You can manage browser cookie settings, although some account steps may then need repeating.

Retention periods

We keep account, payment and security records for the period needed for their stated purpose, account queries or legal duties. Ask support which category applies to your request.

Policy requests

To request access, correction or deletion, contact us through the account support path with enough detail to locate your record. We verify the request before making a change.

Privacy Policy Questions Before Account Access

These Privacy Policy answers cover the questions we expect before you open an account or ask about a wallet record. We keep each answer tied to a practical step, from phone verification and cookie settings to a request for correction. If your case is unusual, use the support path connected with your account.

It covers account details, phone verification, device signals, cookies, payment references, security records, retention and requests to access, correct or delete data connected with your account.

Yes. The Privacy Policy covers the status and reference details needed to match DANA, QRIS, OVO, GoPay, bank transfer or virtual account activity with your account.

Phone verification helps connect an access request with the correct account and supports recovery checks. We confirm identity before discussing private account records or changing account details.

Yes. Contact support through the account route and request access to your stored data. Include your account phone number, but never send a password, wallet PIN or full security credential.

Send a correction request through the account support path and describe the field that is wrong. We verify your identity, check the relevant record and confirm the next step.

You can ask about deletion through support. We assess the request against active account needs, security records and legal retention duties, then explain which data can be removed and why.

The policy is written for Indonesia, while access and eligibility depends on local law. We apply the stated handling rules where local law permits and explain location-specific limits when asked.