Reference

How We Protect Your Account Data

Aviator, Andar Bahar, Mines and UFC MMA sit behind one account flow, so our Privacy Policy explains exactly what we collect when you open your account, enter the…

Account data useDANA privacy contextOVO payment recordsGoPay and QRIS logs
beruang88 How We Protect Your Account Data
CONTACT ROUTES

3 Ways To Ask About Privacy

Privacy questions should not leave you guessing. We give you direct contact paths for account data checks, cookie questions and correction requests, so you can ask before opening your account or after a payment record appears in your wallet history. Our team may ask for your account name, recent login device and payment rail used, but we will not request your password in chat or email.

Team online

Live chat

Use live chat from the account screen when you need a quick privacy check. Our team is available every day from 10:00 to 02:00 WIB and can confirm what record type is needed before escalation.

Email requests

Send privacy requests to the address shown in the footer when you need a written reply. Include your account name, registered contact route and whether the request concerns DANA, OVO, GoPay or QRIS records.

Account centre

Open the account centre, choose profile settings, then check your contact and device details. This path helps you spot outdated data before asking us to update or correct a privacy record.

DATA HANDLING

6 Privacy Controls Inside beruang88

We handle privacy through account checks, limited staff access and record controls tied to real account actions.

Account registration

When you open an account, we collect the details needed to create your login and contact route. We use those records to recognise you, maintain account access and support requests tied to your profile.

Payment matching

DANA, OVO, GoPay and QRIS references are stored with transaction timestamps so our team can match wallet activity to your account. This helps us answer payment privacy questions without exposing full payment app credentials.

Device signals

We may record browser type, IP signals and device changes when you log in. If a new phone or desktop appears, those signals help us spot unusual access and protect your account history.

Cookie use

Cookies help keep sessions active, remember language and measure page performance. You can manage browser cookies through Chrome settings, Safari settings or your device privacy menu, though some account pages may need session cookies.

Retention checks

We keep account and payment records only for operational, security and legal needs tied to the service. If you ask about removal, we review what can be deleted and what must stay for record matching.

Correction requests

If your contact route or profile detail is wrong, ask us to correct it through live chat or email. We may verify your account name, recent login route and payment rail before updating the record.

Your Privacy Questions Answered Here

These answers focus only on how our Privacy Policy works for your account, device and payment activity. If your question is about lobby rules, promotions or game results, use the relevant help page instead. For privacy requests, keep your account name ready and tell us whether the issue concerns login data, cookies, DANA, OVO, GoPay or QRIS records.

We collect the details needed to create and protect your account, such as login name, contact route, password record, device signals and wallet activity. We use them for access, account service and payment matching.

We keep payment references so deposits, withdrawals and wallet checks can be matched to the right account. The record normally includes rail name, time, status and transaction reference, not your full app password.

Yes. Contact live chat or email with your account name and the detail that needs correction. We may verify your recent login device or payment rail before updating the record to prevent unwanted changes.

Cookies keep your session active, remember basic preferences and help us measure whether pages load correctly. You can manage them in your browser settings, but account pages may require session cookies to function.

We share only what is needed for account operation, payment matching, security checks or service delivery. For example, a payment processor may receive transaction references, while game sessions may use account identifiers rather than full profile details.

Retention depends on the record type and the reason it is kept. Payment and security records may stay longer than simple profile edits because they help answer disputes, protect access and meet legal record needs.

Use live chat from 10:00 to 02:00 WIB for quick direction, or send email for a written request. Include your account name, contact route and whether the question concerns login, cookies or payments.