Reference

Privacy Policy for Your Account

Open your account and our Privacy Policy tells you exactly what we keep when you use Super Sic Bo, Mahjong Panda, Rocket Crash, or live tables on Android…

Account dataCookie useLocal lawSupport logs
bapetogel Privacy Policy for Your Account
ASK US HERE

Where to Ask About Privacy

When you want a copy, a correction, or a removal step, we keep the route simple and traceable. Send us a chat message from 09:00-23:00 WIB, email privacy@bapetogel.

Live chat Use live chat from 09:00-23:00 WIB for data-use questions, correction requests, or a quick check on a consent change. We match the chat to your account before sharing any record details.
Email request Send a note to [email protected] when you need a copy, an update, or deletion steps for stored records. We reply in the same thread and ask for account checks before changes.
In-account form After login, open the privacy form in your profile area to submit requests tied to your phone, email, or wallet record. It works on Android, iPhone, and desktop browsers.
DATA SAFETY STEPS

Data, Cookies, and Retention Rules

We keep the policy practical: collect only what your account, payments, and support trail need, then reduce it when the legal window closes.

Data minimisation

We ask for the few fields needed to open and run your account, such as phone number, email, device ID, and transaction reference. We do not collect extra details just to fill space in the profile.

Cookie control

Our cookies remember language, device choice, and login state so you do not repeat the same steps on every visit. You can clear them in your browser, and the next login rebuilds the session from fresh.

Device checks

If you switch between Android Chrome, iPhone Safari, and desktop, we log the device path to spot unusual access. That helps us confirm it is you when a password reset or phone change is requested.

Account security

When you edit an email, phone number, or wallet reference, we ask for a code or a second check before the update goes live. That reduces accidental changes and protects the record from misuse.

Retention rules

We keep logs only as long as we need them for security checks, payment tracing, dispute handling, and legal duties. After that window, we remove or anonymise them where our process allows.

Your requests

To request access, correction, or removal steps, send the exact account email, phone number, and the change you want. We confirm the match, then answer with the next action on the same thread.

Common Questions About This Policy

These questions cover the parts people ask first: what we collect, how long we keep it, and how you can change it. If your account uses DANA, OVO, GoPay, or QRIS, the same privacy rules still apply. We verify the request against your login trail before we release or change any record, and the result returns through chat or email.

We keep the fields needed to create and secure your account: name, contact details, login logs, device signals, and payment references. We do not add extra fields unless you send them in a support request.

Yes, but only the reference data needed to match the transfer, confirm timing, and handle a mismatch. The wallet balance stays with the payment provider, and we do not expose transaction details on public pages.

Yes. Send the account email or phone number plus the exact change you want, and we will verify the match before updating the record. We answer through the same channel you used to reach us.

We keep records only for the time needed for account security, payment tracing, issue handling, and legal duties. After that, we remove or anonymise them where our process and local law allow.

No. Our cookies mainly remember language, device choice, and login state so the next visit is smoother. They do not turn your private browser into a public profile, and you can clear them in your browser settings.

Only the staff who need it to verify the account and carry out the change can see it. We route the request through the chat, email, or in-account form, then log the action for audit.

Yes. Access depends on local law and is available only where local law permits. If a region is not permitted, we restrict the account path and keep only the logs needed for security and legal handling.