Reference

Privacy Policy for your wallet data

Your account details, device sessions, and wallet records for DANA, OVO, GoPay, and QRIS are covered by one Privacy Policy before you open an account.

DANA record contextOVO wallet checksAccount > Security09:00-23:00 WIB support
234slot Privacy Policy for your wallet data
CONTACT ROUTES

Privacy questions reach a real desk

A privacy question should not get lost in a game chat. Use live chat daily from 09:00 to 23:00 WIB, email [email protected], or send your account phone number through WhatsApp when our team asks for identity confirmation. If you are in Bandung and switch from mobile data to Wi-Fi, include the approximate login time so we can locate the right device session.

Team online

Live chat

Open live chat from the account footer between 09:00 and 23:00 WIB. Tell us the privacy request type first, such as cookie choice, active session, or wallet record, so we route the request correctly.

Email desk

Email [email protected] from the address on your account. We ask for your username and last login month, not your password, then reply with the next privacy step.

WhatsApp check

When WhatsApp is needed, we ask you to confirm the account phone number and a recent DANA, OVO, GoPay, or QRIS reference. Share only the reference code, not PINs.

ACCOUNT CARE

Data controls inside your 234slot account

Privacy handling sits beside your normal account flow, not outside it. You can reach Account > Security > Active Sessions to see recent device access, and Account > Wallet > History to…

Account details

When you create an account we collect your phone number, email, username, password hash, and device signals. We use them to create your account, protect sign-in, and respond when you ask for correction or removal.

Wallet records

Wallet logs store transaction references, amount, time, status, and method for DANA, OVO, GoPay, or QRIS. They help us match deposits and withdrawal checks, and they support privacy access requests.

Cookie choices

Cookies keep you signed in, remember language, and measure page errors across mobile and computer access. You can clear them in your browser, then sign in again if the lobby asks for a fresh session.

Active sessions

Go to Account > Security > Active Sessions to check device names and recent login times. If something looks unfamiliar, contact support first so we can freeze risky access while checking the privacy log.

Retention handling

We keep records only as long as operational, security, accounting, or local-law needs require. When retention no longer applies, we delete, anonymise, or separate data from your visible account profile.

Profile changes

To update your phone, email, or name spelling, start in Account > Profile and then message support if the field is locked. We log the request so the change has a clear privacy trail.

Privacy Policy questions you may search

These answers focus on the Privacy Policy only: what data we collect, how payment references are handled, and how you can reach us. They do not replace the policy text, but they explain the account steps you are likely to use before you open an account or when you return from mobile. For anything tied to eligibility, availability depends on local law and only applies where local law permits.

When you open an account, we collect details such as phone number, email, username, password hash, device type, IP range, and cookie choices. We use them for sign-in, security checks, wallet matching, and privacy support.

Yes. The policy covers wallet references from DANA, OVO, GoPay, and QRIS, including time, status, method, and transaction code. We use those records to reconcile deposits, verify withdrawals, and answer account data requests.

Go to Account > Profile first and edit any field that is open to you. If a field is locked, contact live chat or [email protected] with your username and the correction you need.

Yes. Open Account > Security > Active Sessions to view recent device names, login times, and session status. If a session looks wrong, contact us before changing details so we can preserve the security record.

We keep account, wallet, cookie, and security records for as long as operational, accounting, dispute, or local-law needs require. After that, we delete, anonymise, or separate data from your visible profile.

You can ask us to remove data we no longer need for account, security, accounting, or local-law reasons. Send the request through email or live chat, and we will explain which records can be changed.

Only team members who need the request for support, security, wallet reconciliation, or compliance checks can access it. We do not ask for your password, payment PIN, or full device access code.