Reference

Privacy Policy for Your bejo888 Account

Your bejo888 Privacy Policy explains how we handle profile details, DANA, OVO, GoPay and QRIS wallet records, cookies, and device sessions before you open an account.

Account data explainedDANA, OVO, GoPay, QRISCookie controlsPrivacy contact paths
bejo888 Privacy Policy for Your bejo888 Account
CONTACT PATHS

Contact Us About Your Privacy

Privacy questions deserve a direct path, not a generic inbox. You can reach us through live chat from 09:00 to 23:00 WIB, email us at privacy@bejo888.

Live chat privacy help Use live chat between 09:00 and 23:00 WIB for short privacy questions, such as…
Email request channel Send longer requests to [email protected] when you need a written record.
Account form path After login, go to Profile, then Help, then Privacy Request.
DATA CARE

How We Handle Privacy Requests

We treat privacy work as part of daily account operations. Wallet matching, cookie checks, device session checks, and data changes are handled by trained account staff, with escalation when a request touches…

Account setup data

When you open an account, we collect the details needed to identify your profile, secure login access, and respond to support messages. We avoid asking for data that has no account purpose.

Wallet record checks

DANA, OVO, GoPay and QRIS records are matched against your account name, amount, receipt time, and transaction reference. This helps us trace wallet questions without exposing your payment data in chat.

Cookie choices

Cookies help keep you signed in, remember language choices, and measure whether pages load correctly. You can clear them through your browser settings, but some account checks may require a fresh login.

Device sessions

We record device type, IP signal, browser version, and session time to spot unusual access. Check Account, Security, Active Sessions if you need to close a phone or desktop session.

Retention handling

Some records stay longer when they relate to wallet reconciliation, account disputes, or security events. When retention is no longer needed, we remove or reduce data in active account systems.

Change requests

If your email, phone number, or profile detail is wrong, send a privacy request before editing payment details. We may ask for account signals, not your password, to confirm the request.

Privacy Questions Before You Join

These answers focus on the Privacy Policy only: account data, wallet records, cookies, access logs, and how you contact us about changes. Read them before you open an account so you know what data we collect, why we keep it, and which support path fits your request.

We collect the details needed to create your profile, secure login access, contact you about account matters, and connect wallet records. This can include username, email, phone number, device signals, and account activity.

We use local wallet records to match deposits, withdrawals, receipts, timing, and account ownership. The Privacy Policy limits this use to account operation, wallet reconciliation, dispute checks, and security review.

Yes. Use Profile, Help, then Privacy Request after login, or email [email protected]. Tell us which field is wrong, and we will confirm the account before changing anything sensitive.

Cookies can remember login status, language settings, and page performance. If you open Lightning Roulette, Aviator, or Tennis Betting, activity logs may show account use, but cookies are not sold as separate profiles.

Open Account, then Security, then Active Sessions on mobile or desktop. You can review recent device entries, close sessions you do not recognise, and contact us if an access record looks unfamiliar.

Retention depends on the record type. Wallet receipts, account disputes, and security logs may stay longer than chat messages because they help resolve account questions and protect access where local law permits.

Use live chat from 09:00 to 23:00 WIB for quick questions, or email [email protected] for written requests. Never send your password; we verify requests through account signals instead.