Reference

Privacy Policy for Your Account

Live Blackjack, Legend of Hou Yi and Rocket Crash sit behind an account flow that asks only for the details we need to keep your wallet, login and…

Account data scopeDANA and OVO contextGoPay and QRIS recordsCookie choices

Browse Lobby Read FAQ

How We Treat Privacy Requests

kilat128login Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Your privacy request starts with the account detail you can verify, such as your registered phone number, email address or latest wallet activity. We use that match to check whether the request belongs to you before we change, export or remove account data. This Privacy Policy

1
applies to account records, device logs, cookies, support chats and payment references created when you use kilat128login. Access, eligibility and some account actions depend on local law, so our team may ask for added confirmation before completing a change. We do not publish your private payment
2
reference, and we do not ask you to send card photos in open chat. If your request involves DANA, OVO, GoPay, QRIS or bank transfer history, we keep the transaction reference long enough to trace balance questions, fraud checks and payout disputes.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT PATHS

Privacy Help Through Real Channels

Privacy questions need a clear route, not a public comment thread.

DATA HANDLING

Blackjack Sessions and Wallet Records

We handle privacy around the actual account actions you take: logging in, entering Blackjack, checking League of Legends markets, opening slot rooms and moving funds through local rails.

Account details

At sign-up we collect the fields needed to create and protect your account, such as username, phone number and email. If you ask to change them, we confirm the request against your current login and wallet records.

Payment references

For DANA, OVO, GoPay, QRIS and bank transfer activity, we store transaction references rather than extra wallet secrets. These records let us trace balance questions, payout status and duplicate payment attempts without exposing your full private app data.

Device and login logs

When you move from mobile to desktop, we record device type, browser, IP range and session time. These logs help us spot account access that does not match your usual pattern and review privacy requests safely.

Cookies and preferences

Cookies remember session status, language choice and selected lobby filters, including live table or slot room views. You can clear them in your browser, but doing so may require a fresh login on your next visit.

Retention rules

We keep account and payment records only for practical service needs, including dispute checks, wallet reconciliation and security investigation. When a record is no longer needed for those purposes, we remove or anonymise it through our internal queue.

Correction requests

If your phone number, email or name spelling changes, contact us before your next withdrawal request. We verify the update through your current account session so the privacy change does not create a payout mismatch.

Your Policy Questions Answered

The answers here focus on the Privacy Policy choices you are most likely to check before opening an account or sending a data request. We cover what we collect, why payment references are kept, how device logs work and how to reach us when you need a correction, export or deletion check.

We collect the account fields needed to identify you, manage login access and connect wallet activity, such as username, phone number, email and payment references. We do not ask for extra personal documents unless a specific security check requires it.

We keep local payment references so we can trace deposits, withdrawals, balance questions and duplicate attempts. The record links your account to the payment event, but we do not store private app passwords or full wallet access.

Yes. Contact us from your registered email or live chat account session and explain the field that needs correction. We compare the request with recent login and wallet records before updating phone, email or spelling details.

Cookies keep your session active, remember language preference and reduce repeated login prompts. You can clear them through your browser settings, though the next visit may ask you to log in again and confirm account access.

We share only the service data needed to run game sessions, settle rounds and protect account access. Providers do not receive your DANA, OVO, GoPay or QRIS app password, and payment records stay within wallet checks.

We keep account, device and payment records for service needs such as payout tracing, dispute checks and security investigation. When those needs end, we remove or anonymise records through our internal retention process where local law permits.

Use live chat from your account menu between 09:00 and 23:00 WIB, or email us from your registered address. Include your username, device type and the payment rail involved if the concern relates to wallet activity.

Privacy Policy for Your Account

Privacy Help Through Real Channels

Blackjack Sessions and Wallet Records

Account details

Payment references

Device and login logs

Cookies and preferences

Retention rules

Correction requests

Your Policy Questions Answered

01 What personal data does kilat128login collect when I open an account?

02 Why do you keep DANA, OVO, GoPay or QRIS references?

03 Can I ask you to correct my account details?

04 How do cookies affect my privacy on mobile and desktop?

05 Do you share my private data with game providers?

06 How long do you keep privacy-related records?

07 How do I contact you about a privacy concern?

Related Pages