Reference

Privacy Policy for Your betbery Account

Account creation, DANA, OVO, GoPay, QRIS wallet checks, and live-table session logs each create data we handle under this Privacy Policy.

Indonesia account dataDANA and OVO contextGoPay and QRIS checksCookie control paths
betbery Privacy Policy for Your betbery Account
CONTACT ROUTES

3 Ways to Reach Privacy Support

Privacy requests need clear routes, not guesswork. We keep account, wallet, and device questions in the same support queue so you do not need to repeat…

Live chat Use live chat from the account menu for quick privacy questions about login records…
Email requests Send account data access, correction, or deletion requests to our privacy mailbox listed in…
Account page Open Account, then Security, then Privacy Request to ask for a data check without…
DATA HANDLING

6 Controls Behind This Policy

We treat privacy as an account operation, not a slogan. Each control below explains how we handle data you create while registering, signing in, changing security settings, using…

Collection limits

We collect details needed to create and protect your account: contact data, login records, device type, IP data, payment references…

Payment context

DANA, OVO, GoPay and QRIS records are used to match deposits, withdrawal checks, failed transactions, and support questions.

Cookie choices

Cookies help keep you signed in, remember language settings, measure page errors, and protect sessions.

Access security

When you reset a password or open a new session, we compare account signals such as device, location pattern, and…

Retention timing

We keep account and transaction records while your account is active and for periods needed for payment handling, dispute checks…

Change requests

You can ask us to update incorrect profile data, provide a copy of key account records, or remove data where…

Privacy Questions Before You Join

Use these answers to understand how your data is handled before you open an account or add a wallet method. We keep the wording plain because privacy choices should be easy to act on. If your question involves a live account, contact us from the registered email or the account page so we can verify you safely.

We collect the details needed to create your account, contact you, protect sign-ins, and handle payments. That can include your name, mobile number, email, username, device data, IP data, and payment references.

We keep payment references so deposits, withdrawals, failed transactions, and wallet support questions can be matched to your account. We store transaction context such as time, status, and method, not your full wallet login.

Yes. Send a request from Account, Security, then Privacy Request, or email us from your registered address. We may ask for account confirmation before sharing data so the records go to the right person.

Start in your account settings for editable fields such as contact details. If a locked field needs correction, contact support with your username, registered mobile number, and a clear note on what should change.

Cookies can record session timing, device details, login state, and page performance while you use areas such as Live Roulette or Crash Games. They help protect access and fix errors, not expose your private wallet credentials.

We keep records while needed for account service, payment handling, support history, security checks, and legal duties. When those reasons no longer apply, we delete, anonymise, or restrict records where our systems allow.

Use live chat from 09:00-23:00 WIB for initial help, or send a written request to the privacy mailbox. For account-specific matters, contact us from your registered email so we can verify ownership.