Reference

Privacy Policy for Your Account Data

Your account, wallet, cookie and device data are covered in one clear Privacy Policy before you open an account or return to the lobby.

Account data scopeDANA and OVO contextCookie choicesSupport 09:00-23:00 WIB
studiobetlogin Privacy Policy for Your Account Data
CONTACT ROUTES

Three Ways to Ask Us

Privacy requests should reach the right team without making you repeat your account story. We route chat, WhatsApp and email messages by request type, then confirm ownership before we discuss account data. If you need a copy, correction or deletion review, include your registered mobile number and the channel you used for your latest DANA, OVO, GoPay or QRIS wallet action.

Team online

Live chat privacy help

Use live chat from the account menu between 09:00 and 23:00 WIB. We ask for your registered mobile number and one recent wallet reference before sharing any personal data or changing privacy settings.

WhatsApp account check

Message our WhatsApp support line from the number on your profile. For privacy requests, we verify the login time, device type and one payment rail used recently, such as GoPay or QRIS.

Email privacy mailbox

Send detailed privacy requests by email when you need a written reply. Include your account ID, registered email and requested action so we can confirm ownership before handling records.

DATA CARE

Six Controls Around Your Data

We keep the Privacy Policy tied to daily account operations, not hidden legal wording. Your cookie choices affect device recognition, payment logs support wallet checks, and retention periods depend on security, dispute…

Account creation records

When you open an account, we store the details needed to identify you later: mobile number, email, username, registration time and device signal. This helps us answer privacy requests without exposing your account to others.

Wallet activity handling

DANA, OVO, GoPay and QRIS references are kept with timestamps, amounts and status codes so we can trace payments and resolve disputes. We separate wallet logs from chat content where the systems allow.

Cookie and device choices

Cookies help remember language, login state and basic device risk signals. You can remove them in your browser settings, though we may ask for another verification step when your device looks new.

Lobby activity records

We record game-category activity such as slot rooms, live casino tables and sportsbook market access to support account security and dispute checks. Specific titles like Super Bingo or Mega Fishing may appear in activity logs.

Retention and deletion review

We keep data only for operational, security, dispute and legal reasons, then reduce or remove it when those reasons no longer apply. Some payment records must remain tied to wallet audit needs.

Change requests

You can ask us to correct profile details, update contact data or review stored records. We verify account ownership first, because privacy rights must protect you rather than expose your data.

Privacy Policy Questions You May Search

These answers explain how our Privacy Policy works when you create an account, use local wallets, change devices or contact support. We keep the wording practical so you know which data is involved, why we use it and how to reach us when something needs correction.

We collect account details such as username, mobile number, email, registration time, device signal and login records. We use them to create your profile, protect access, confirm ownership and respond to privacy requests.

We keep payment references, timestamps, status codes and account matches so we can trace wallet activity and resolve disputes. These records also help confirm you own the account before we discuss private data.

Yes, you can request a copy through live chat, WhatsApp or email. We verify your registered mobile number, account ID and a recent account action before preparing data linked to your profile.

Cookies remember language, session status and device signals. If you clear cookies through Android Chrome > Settings > Site settings > Cookies, we may ask for another verification step at your next login.

We keep records while they are needed for security, wallet checks, dispute handling and legal requirements. When those reasons no longer apply, we review whether data can be reduced, anonymised or removed.

Only support or account staff assigned to handle the request can access the relevant records. We limit what they see to the request type, such as profile correction, wallet trace or cookie-related login issue.

Yes, ask support from the account channel you can still access. We verify ownership first using login details, device signals and recent wallet activity before changing contact data in your profile.