LEGAL REFERENCE

How bantai77 Handles Your Account Data

This is the bantai77 privacy policy. We wrote it so you know exactly what we collect when you open an account, what we keep on file while you...

Indonesia-focusedPlain-EnglishAccount-levelLobby-wideUpdated

Enter Game Lobby Read FAQ

Our Privacy Posture and Scope

We collect the basics needed to run your account: the name you register with, your contact handle, the device you sign in from, and the wallet reference you use at the cashier. Where local law permits, we store this on servers that serve our supported regions. We do not sell your data to third parties. We share only what's necessary with payment

partners to clear a DANA, OVO, GoPay or QRIS movement, and with game providers to load a table or slot session. You can request a copy or deletion at any time, and we'll act within the window our jurisdiction sets out.

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

HELP CHANNELS

Privacy Contact Paths

If something about your data needs attention, reach us through any of the channels below and our privacy desk will pick it...

REVIEW SIGNALS

How We Review This Policy

Our policy isn't a copy-paste page. Here's how we keep it honest.

Drafted In-House

Our compliance team writes this policy line by line, not a template bought off the shelf. Every clause maps to...

Legal Sign-Off

Indonesian counsel reviews the wording before it ships. Where local law permits specific data handling, we say so plainly instead...

Quarterly Refresh

We revisit this page every quarter and any time a process changes. The last-updated stamp at the foot of the...

Plain-English Pass

After legal sign-off, an editor rewrites dense clauses into sentences you can scan on a phone. The intent stays identical...

Vendor Audits

Game providers and payment partners we plug into are audited for their own data handling before we route anything through...

Reader Feedback

When you flag a clause as unclear through chat or the privacy inbox, we log it. Recurring questions trigger a...

Consistency Across Our Policy Pages

This policy lines up with our other legal pages. Here's how the pieces fit.

Privacy vs Terms

Privacy covers what data we hold. Terms cover what you agree to when you use the lobby. They reference each other but don't repeat clauses, so each page stays focused on its own scope.

Privacy vs Cookies

This page handles account data. The cookie notice handles browser-side trackers and your consent choices. Updates to one don't automatically restate the other; check both if you want the full picture.

Privacy vs AML

AML checks reuse identity data covered here, but the legal basis is different. We flag that distinction so you know why a verification step might ask for documents the privacy page already lists.

Privacy vs Payments

Cashier flows for DANA, OVO, GoPay and QRIS surface in the payments page. Privacy explains what the cashier keeps on file afterwards and how long that record sits with us.

Privacy vs Marketing

Marketing preferences live inside your account settings. This policy explains what those toggles actually control and which channels they cover, so you're not toggling something blind.

Privacy vs Support

Support tickets are stored under the same retention window described here. The support page tells you how to open one; this page tells you what happens to the transcript afterwards.

Privacy vs Account

Account closure routes to the deletion process described in this policy. The account help page walks the steps; we describe what data survives closure and why, where local law permits.

What This Policy Page Shows You

The layout of this page is built around the questions readers actually ask. Here's what each block delivers.

Scope Block

The opening posture block tells you which products this policy covers: the casino tables, the slot rooms, the sportsbook side and the cashier. One paragraph, no scrolling needed to find the scope.

Data Categories

A clean list of what we hold on you — identity, contact, device, wallet reference — sits near the top so you can confirm in seconds whether your concern is even covered by this document.

Retention Window

We surface how long records stay on file rather than burying it in a footnote. The window depends on the data type and the jurisdiction, and we say so in the same sentence.

Your Controls

A dedicated block lists the toggles inside your account: marketing channels, session visibility, export and deletion. Each one links straight into the panel where the change actually happens.

Contact Paths

The support block above gives you three ways to raise a privacy question. We list response windows next to each so you know what to expect before you send the message.

Update Stamp

The footer carries a last-updated date and a short changelog of what moved. If you've read this page before, the changelog tells you whether anything material has shifted since.

Privacy Questions We Hear Most

We collect the registration name, a contact handle, the device fingerprint of the session you sign up from, and the wallet reference tied to your first DANA, OVO, GoPay or QRIS movement. Nothing beyond that at signup.

No. We share data only with payment partners to clear a cashier movement and with game providers to load your session. Both are contractually limited to the task. We do not sell data to advertisers or list brokers.

Active accounts keep records for as long as the account is open. After closure, we hold the minimum the jurisdiction requires — typically a fixed window for financial records — then the file is removed from active systems.

Yes. Open the privacy inbox or the export button inside account settings, confirm your identity, and we'll send a structured file covering profile, session history and cashier records within the window our jurisdiction sets.

Trigger closure from the account panel or message the privacy desk. We confirm there are no pending cashier movements, then proceed. Some records survive closure where local law requires retention; the rest is removed.

The wallet reference and the movement amount pass to the payment partner so the transfer clears. We keep a record on our side for reconciliation and audit. The partner handles its own privacy obligations separately.

The footer carries a last-updated stamp and a short changelog. Material changes also trigger an in-lobby notice the next time you sign in, so you don't have to revisit the page to spot a shift.