Reference

Privacy Policy for Your Account

Privacy controls for your account, wallet, and game session records sit inside the same flow you use to open an account at betoffice.

Cookie choicesDANA referencesDevice controlsSupport 10:00-02:00 WIB
betoffice Privacy Policy for Your Account
CONTACT ROUTES

Privacy Help Through Real Channels

Privacy questions move faster when you contact us from the same account you use for wallet activity. Our live chat is open from 10:00 to 02:00 WIB, and email requests go to [email protected]. For logged-in requests, head to Account > Messages so our team can reply inside your profile. We may ask you to confirm a payment rail, recent login device, or account step before changing data.

Team online

Live Chat Privacy

Use live chat from 10:00 to 02:00 WIB for quick privacy checks, such as removing an old phone from your account or asking why a login alert appeared after a new browser session.

Email Record Requests

Send data access, correction, or deletion requests to [email protected]. Include your account name and the payment rail involved, such as QRIS or GoPay, so we can locate records accurately.

Account Inbox

Open Account > Messages after login when you want a private reply kept inside your profile. We use it for document follow-up, cookie preference replies, and updates on retention requests.

DATA PRACTICE

Cookie Choices Around Rocket Crash

We write this policy around tasks you actually perform: creating an account, setting a password, entering Limbo or Rocket Crash, and moving funds through DANA, OVO, GoPay, or QRIS.

Data We Collect

During account creation we ask for the details needed to identify your profile, connect wallet records, and keep login access secure. We do not ask for data unrelated to account operation.

Payment Records

DANA, OVO, GoPay, and QRIS references are stored with time, amount, status, and account ID. This helps us answer wallet questions without exposing full payment app credentials.

Cookies and Devices

Cookies remember session status, language choice, and risk signals on mobile browser or computer. You can clear browser cookies, but we may ask for a fresh login after that change.

Game Session Logs

When you enter Auto Roulette, Limbo, or Rocket Crash, we record session IDs, timestamps, and wallet outcomes. These logs help reconcile disputes without showing private payment app details to game staff.

Retention Window

We keep account and transaction records for operational, tax, anti-abuse, and legal reasons, then restrict or erase data when the retention reason ends and local rules allow.

Change Requests

Ask us to correct profile fields, close old device sessions, or delete data that no longer needs to be kept. We verify the request through login, email, or account inbox.

Privacy Questions You May Ask

These answers keep privacy requests practical, especially when you are checking account data before opening the lobby or asking why a wallet record appears in your history. Use them to understand what we collect, how long we keep it, and which contact path fits your request. If your case involves payment app records, include the rail name so we can answer with less back-and-forth.

We collect the data you enter during account setup, login device details, cookie choices, wallet references, and game session records. We use it for account operation, support, payment checks, and security monitoring.

Email [email protected] from the address linked to your account, or use Account > Messages after login. Include your account name, preferred contact channel, and any DANA, OVO, GoPay, or QRIS reference.

Yes. You can edit some profile fields in account settings, while sensitive changes go through support. We may confirm your password, email, recent device, or payment rail before applying the change.

We store payment references with account IDs, timestamps, status, and transaction context. Full payment app credentials are not shown to game staff, and access is limited to teams handling wallet checks.

Cookies help keep your session active, remember language choice, and connect activity to the right account. Rocket Crash logs are stored separately with session IDs, timestamps, and wallet outcomes for dispute checks.

Retention depends on the record type. Account, wallet, and support records are kept while needed for operation, dispute handling, tax, anti-abuse, or legal reasons, then restricted or erased when allowed.

The policy itself does not open or block games. It explains what data is checked when access to Auto Roulette, Limbo, Boxing Betting, or wallet features depends on local law.