Reference

Privacy Policy for Your bejo33 Account

Baccarat tables, Dragon Hatch slots and Aviator sessions create account data the moment you open your account, so this Privacy Policy explains what we collect and why.

Account dataCookie choicesDANA recordsQRIS checks
bejo33 Privacy Policy for Your bejo33 Account
PRIVACY HELP

Contact Paths for Data Requests

Privacy questions should reach the team that can read account records, not a public comment box. We keep live chat open 24/7, and our privacy mailbox handles requests that need document checks or a longer written answer. When you contact us, share your registered mobile number, account username and the payment rail involved, such as QRIS or OVO, so we can match the request safely.

Team online

Live chat privacy queue

Open Help > Live Chat after login and choose Privacy Request. Our chat desk runs 24/7, checks your account session first, then asks only for details needed to locate the data record.

Email data request

Send privacy requests to [email protected] from the email linked to your account. Include your username, registered mobile number and whether the request concerns login data, cookies, DANA, OVO, GoPay or QRIS records.

Account inbox reply

For requests that need a written record, we may answer inside your account inbox. Check Account > Messages after you log in; sensitive replies stay behind your password and session checks.

DATA CONTROLS

Controls Around Cookies and Account Records

A privacy policy is useful only when you can see how it works inside the account. We separate login records, wallet records, game-session data and support files so each request goes to…

Registration data

When you create an account, we collect the details needed to identify you, set login credentials and contact you about account safety. We use those records for account access, support matching and payment verification.

Payment records

DANA, OVO, GoPay and QRIS activity creates receipts, timestamps and account-matching records. We keep those records to confirm deposits, process withdrawals, handle disputes and detect mismatched wallet names.

Cookie settings

Cookies help keep your session open, remember language choices and flag unusual sign-in attempts. You can clear them from your browser, though you may need to log in again and repeat security checks.

Device sessions

Your device type, IP signal and session time help us spot account access that does not match your usual pattern. Check Account > Security > Sessions to end a session you do not recognise.

Retention approach

We keep personal data only for account operation, payment checks, dispute records, technical logs and legal handling. Different record types have different retention periods because wallet receipts and chat logs serve different purposes.

Change requests

If your mobile number, email or name record is wrong, contact us before using DANA, OVO, GoPay or QRIS again. We may ask for a security step before changing account data.

Privacy Questions Before You Join

You should know how your data is handled before you add funds or open a table. These answers cover account data, wallet records, cookies, support access and correction requests. If your question involves a live wallet case, contact us from the registered account so we can verify the request before sharing any private details.

We collect account details such as username, contact data, login credentials and security signals from your device. We use them to create your account, protect access, answer support requests and connect wallet records to you.

Yes. When you use DANA, OVO, GoPay or QRIS, we keep transaction IDs, timestamps, wallet-matching details and status records. These help confirm deposits, process withdrawals, resolve disputes and trace unusual activity.

Yes. Contact live chat or [email protected] from your registered contact details and explain what needs changing. We may ask for an account security step before updating email, mobile number or name records.

Cookies keep you signed in, remember basic account settings and help us detect unusual access. If you clear cookies in your browser, you may need to log in again and complete another security check.

Only team members who need the case can access the conversation. We use your chat or email history to answer the request, confirm account ownership and keep a record of the privacy action taken.

You can ask us to close the account file and remove data that is no longer needed. Some payment, dispute or security records may stay stored for audit duties and legal handling where local law permits.

Log in and open Account > Security > Sessions. If you see a device or time you do not recognise, end that session, change your password and contact support so we can check related access logs.