Reference

Privacy Policy for Your beo4d Account

Your account data, wallet activity and device signals are handled under this Privacy Policy before you enter Andar Bahar, Galactic Gems or the sportsbook lobby.

DANA data contextOVO account checksGoPay wallet recordsQRIS payment trail
beo4d Privacy Policy for Your beo4d Account
CONTACT ROUTES

Three Ways to Ask About Data

Fast answers matter when the question is about your account record, not a general lobby issue. Our privacy contact paths are kept inside the same support desk that handles wallet checks, so you can reference a DANA, OVO, GoPay or QRIS transaction without moving between teams. We respond every day from 09:00 to 23:00 WIB and may ask you to confirm the account step involved, such as Profile, Wallet, or Security.

Team online

Live chat privacy desk

Use live chat from the account menu when you need a data correction, cookie question or device access check. Share your username and the relevant Wallet or Security step so we can trace the request faster.

Email request channel

Send privacy requests by email when you need a written record, account export or deletion query. Include your registered mobile number, last login device and payment rail name if the request involves DANA, OVO, GoPay or QRIS.

Account menu request

Open Profile then Security to check saved devices before contacting us. If a phone or browser looks unfamiliar, message support between 09:00 and 23:00 WIB so we can help review the access trail.

DATA HANDLING

Six Controls Behind This Policy

A privacy page should show the working parts, not just broad promises. We separate login records, wallet references and support messages so the team only sees what is needed for the task.

Account identity checks

When you open an account, we collect the details needed to keep one profile tied to one login. Passwords are stored as hashes, and support cannot read or send your password back to you.

Payment reference handling

DANA, OVO, GoPay and QRIS records are used to match wallet movement with your account. We keep the payment reference, status and time stamp so deposit and withdrawal questions can be checked without guessing.

Cookie and session use

Cookies keep your session active, remember device choices and help us spot repeated failed logins. You can clear browser cookies, but you may need to log in again and repeat security checks afterward.

Device access records

The Security area can show recent device activity such as phone browser, desktop browser or app-like web shortcut. If a device does not look familiar, contact us before making wallet changes.

Retention and deletion

We keep account and transaction records for operational checks, dispute handling and legal duties where local law permits. If you ask for deletion, we verify ownership first and explain any records we must retain.

Privacy request process

To change mobile number data, request an export or ask about stored records, start from Profile or email support. We may ask for recent login details to make sure the request is really yours.

Privacy Questions Before You Join

Before you open an account, you should know how your data moves through registration, wallet checks and support. These answers focus on the Privacy Policy only: what we collect, how we use it, how long we keep it and how you can ask us to change or remove it. For account access, our wording is simple: availability depends on local law.

We collect account details such as username, mobile number, password hash, login region, device type and profile activity. If you use DANA, OVO, GoPay, QRIS or bank transfer, we also keep payment references linked to your wallet.

Device and browser records help us keep your session stable and notice unusual access. For example, a new desktop login after regular mobile use may trigger extra checks before support changes profile or wallet details.

We use payment details to match your wallet activity with the right account, check failed deposits and review withdrawal requests. We store references, status and time stamps, not your full wallet app login credentials.

Yes. Contact support by live chat or email and state whether you want a correction, export or deletion request. We verify account ownership first, then explain what can be changed and what must be retained.

Cookies mainly support login sessions, language choices and security checks. We may also record lobby activity such as opening Aviator, Bingo or Fishing God so the account flow works correctly across mobile and desktop.

Only the support or account team handling the request should access the related record. A payment question may involve wallet staff, while a device-access question may go to the team checking login and security records.

Go to Profile, open Security and check recent devices before changing wallet settings. Then contact live chat from 09:00 to 23:00 WIB with your username, last known device and any payment rail involved.