Reference

Open your Privacy Policy before account setup

Your account data, device checks, cookie choices, and DANA, OVO, GoPay, or QRIS wallet records are covered by this Privacy Policy before you open an account with okeslot.

DANA recordsOVO checksGoPay receiptsQRIS logsDevice controls
okeslot Open your Privacy Policy before account setup
CONTACT ROUTES

Switch to direct privacy support paths

Fast privacy help matters when you want to correct account details or ask what we hold about you.

Live chat Use live chat from 09:00 to 01:00 WIB for privacy questions tied to login…
WhatsApp support Message our WhatsApp team when you cannot access the account area and need help…
Email request Send email when you need a written privacy request, such as data access, correction…
ACCOUNT SAFETY

Browse how we handle your data

Privacy controls are built into account flow, not added after the fact. We keep registration fields separate from wallet checks, record login devices for security review, and limit staff access by role.

Account data

We collect the phone number, email, username, and verification details you provide during account setup. Those fields help us run login, handle password resets, and connect support requests to the correct account.

Wallet records

DANA, OVO, GoPay, and QRIS references are stored as transaction records, not as open wallet access. We use them to match deposits, check withdrawal requests, and answer payment-related privacy questions.

Device signals

We record browser type, IP range, login time, and device markers when you access the lobby. These signals help us spot account takeover attempts and show active sessions under Profile > Security > Active Devices.

Cookie choices

Cookies keep your session active, remember basic display settings, and help us measure page errors. You can clear them in Chrome through Settings > Privacy and security > Clear browsing data.

Game-session records

When you open Speed Baccarat, Royal Fishing, Bingo, Rocket Crash, or sportsbook markets, we log session IDs and result references. Those records support account history checks and dispute handling without exposing your password.

Retention requests

We keep account and wallet records only for operational, security, and legal needs. If you ask for deletion or correction, we verify identity, check pending wallet matters, then confirm what can be changed.

Check answers about your privacy rights

Your privacy questions usually come up at practical moments: during registration, after a device change, when a wallet record looks unfamiliar, or when you want to close an account. We answer those requests through the same support routes listed above, and we keep the process tied to identity checks so account data is not shared with the wrong person.

We collect the details you enter, such as username, registered phone or email, password security markers, and verification records. We also record device and login data so we can protect the account from unusual access.

We use wallet references to match deposits, verify withdrawal ownership, and answer transaction questions. We do not take open control of your DANA, OVO, GoPay, or QRIS wallet; we keep transaction markers linked to your account.

Yes. Contact live chat, WhatsApp, or email with your registered contact and the field you want changed. We confirm identity first, then update details that can be changed under account and legal requirements.

Open Profile > Security > Active Devices after logging in. You can remove sessions you do not recognise, then contact support if the session involved a wallet action or a game record you did not make.

We use session cookies for login, display cookies for page preferences, and measurement cookies for error tracking. On Chrome mobile, you can clear them through Settings > Privacy and security > Clear browsing data.

You can request deletion through email or support chat. We verify identity, check pending wallet records, and explain which data can be deleted and which records must stay for operational or legal reasons.

Only staff assigned to support, wallet checks, or security handling can access the case. We limit each case to the data needed, such as account contact, device record, payment rail, or related session ID.