Reference

Open your privacy choices

benuabet explains how we handle your account, device and payment data before you jump into Live Casino, Fortune Dragon or UFC MMA.

Account data useDANA and QRIS contextCookie choicesSupport contact paths

Explore Lobby Read FAQ

Explore the policy scope

benuabet Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Your privacy choices matter from the first account step, so we keep this page focused on what data we collect, why we collect it and how you can ask us to adjust it. When you create an account, we record details you provide, device signals from

1
your browser or mobile session, login timing and wallet activity tied to DANA, OVO, GoPay or QRIS. We use those records to run your account, check payment status, secure access and answer support requests. Eligibility for access depends on local law, and we do not use
2
this policy to create rights that local rules do not allow. If you connect from Bandung on mobile and later continue on another device, we may compare session data so your wallet and account history stay linked to you rather than to an unverified browser.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Check privacy support paths

Fast privacy help starts with the same account signals we use to verify wallet and login activity.

Live chat Use live chat from your logged-in account between 09:00 and 23:00 WIB. We may ask for your username, recent login device and payment rail name, never your wallet PIN or one-time code.

Email desk Send privacy requests to the support email shown in your account area. Include the email on your profile, the request type and whether it involves DANA, OVO, GoPay or QRIS records.

Account center Open Profile, then Security, then Privacy Request to submit a logged-in ticket. This path gives our team the session ID needed to check your data request without extra back-and-forth.

HANDLING RULES

Browse how we protect data

Privacy controls work better when you know what happens behind the screen. We separate account details, wallet status and device logs so a single support action does not expose more data than…

Account records

We collect the details you enter during registration, such as username, contact email and security settings. These records help us identify you when you request access, correction or account help.

Payment context

Wallet activity tied to DANA, OVO, GoPay and QRIS is stored as transaction context, not as your wallet password. We keep references needed to match deposits, withdrawals and support cases.

Device signals

When you log in, we may record browser type, IP region, device ID and session timing. These signals help us spot unusual account access and keep your lobby session connected to you.

Cookie controls

Cookies keep you signed in, remember language choices and measure page errors. You can clear them through your browser settings, though doing so may require a fresh login check.

Retention steps

We keep data only for account operation, payment tracing, security checks and required record periods. When data is no longer needed, we aim to delete it or reduce identifying details.

Change requests

You can ask us to correct profile data, explain stored records or review a privacy concern. Start from Profile, then Security, then Privacy Request so we can verify the account first.

See common privacy questions

These answers focus on how we handle data connected to your account, payments, devices and support contact. They do not replace the full policy wording, but they give you practical steps before you open a ticket or update your profile. For account-specific requests, sign in first so our team can verify ownership.

We collect the account details you provide, such as username, contact email and security choices. We also record login timing, device signals and wallet activity needed to operate your account and answer support requests.

We use payment references to match deposits, withdrawals and wallet support cases to your account. We do not ask for your wallet PIN, app password or one-time code through chat or email.

Yes. Open Profile, then Security, then Privacy Request from a logged-in session. Tell us which detail is wrong, and we will verify account ownership before changing records tied to payments or access.

Device and login details help us identify unusual access, keep sessions connected and protect wallet actions. We may compare browser type, IP region and session timing when a security check is needed.

Cookies help keep your session active, remember basic preferences and measure page errors. You can clear cookies in your browser, but you may need to log in again and pass a security check.

Use live chat from 09:00 to 23:00 WIB or send email from the address on your account. For faster handling, include your username, request type and relevant payment rail.

You can request deletion or reduced data where local law permits. Some records may need to stay for payment tracing, security checks or required account records before we can remove them.

Open your privacy choices

Check privacy support paths

Browse how we protect data

Account records

Payment context

Device signals

Cookie controls

Retention steps

Change requests

See common privacy questions

01 What personal data does benuabet collect when I open an account?

02 How is my DANA, OVO, GoPay or QRIS data used?

03 Can I ask to correct my profile data?

04 Why do you record device and login details?

05 How do cookies affect my privacy choices?

06 Who can I contact about a privacy concern?

07 Can I ask for my account data to be removed?

Related Pages