Definitions
The terms used here — account, wallet reference, session — match the definitions in our terms page so a word never means two things across bandar303 documents.
LEGAL REFERENCE
How bandar303 Handles Your Account Data
This privacy policy is the plain-English version of how we look after the data tied to your bandar303 account. We cover what we collect when you open an...
Account dataWallet logsCookiesYour controlsIndonesia scope
Our Privacy Posture and Jurisdiction Scope
We process your data under the laws of the supported regions where local law permits bandar303 to operate, with Indonesia treated as our primary scope. The categories we hold are the ones you'd expect: identity fields you submit at sign-up, device and session signals, lobby activity inside slots and sportsbook tabs, and the wallet references generated when you move funds. We retain
these only as long as the account is active or as record-keeping rules require. You can ask us to export, correct or delete your file at any time, and we'll respond inside the windows our policy commits to.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
WHY THIS PLATFORM
How We Keep This Policy Honest
Our editorial and compliance leads review this page on a fixed schedule, and any change to how bandar303 handles your data is reflected here before it goes live...
Quarterly review
The policy gets a line-by-line read every quarter. If a vendor changes or a retention window shifts, we update the...
Named owner
A single data protection lead signs off the page. That accountability means questions don't bounce between teams when you ask...
Versioned changes
Material updates are dated at the foot of the policy. You can see when language changed, so nothing about your...
Plain wording
We rewrite legal jargon into sentences you can actually parse on a phone. The aim is comprehension, not a wall...
Vendor list
Processors that touch your data — payment rails, anti-fraud, hosting — are named in summary form. You see the categories...
Indonesia scope
The policy is written for Indonesia first. Local context around DANA, OVO, GoPay and QRIS is built into the wording...
WHY THIS PLATFORM
Consistency Across Our Policy Pages
This privacy page sits alongside our terms, cookie and account pages. Here's how it lines up so you don't get conflicting answers depending on which document you opened.
Retention
Retention windows quoted in this policy are the same ones surfaced in our account closure page, so closing your account follows the timeline you read here.
Cookies
Cookie categories named here mirror the toggles on our cookie preferences panel. What you switch off there is what we describe processing in this document.
Payments
Wallet handling for DANA, OVO, GoPay and QRIS is covered at a data level here and at a flow level on the cashier page, with no contradictions between the two.
Support
The contact paths listed in our support page include the privacy queue described above, so reaching us through either route ends up at the same desk.
Jurisdiction
The supported-regions wording matches our terms page exactly. If a region is listed as out of scope there, this policy treats it the same way.
Updates
Change-log dates at the foot of this page line up with the version notes published on our terms page, so you can audit both documents on one timeline.
SERVICE CONTEXT
What This Policy Page Surfaces For You
A few visible elements define how this policy reads on your screen. They're the parts visitors tell us actually help, so we keep them pinned in the layout.
Last-updated stamp
A date sits at the top and bottom of the...
Section anchors
Each clause has its own anchor link. Share a specific...
Plain summaries
Every dense clause has a one-line summary above it. Skim...
Request shortcuts
Inline buttons take you straight to the access, correction or...
Mobile layout
The page reflows for phone reading. Tables collapse into stacked...
Change log
A short log at the foot lists what moved in...
Privacy Questions We Hear Most Often
We collect the identity fields you submit at sign-up, the device and session signals your browser shares, and the wallet references created when you fund your account. Nothing extra is pulled in the background.
Active accounts keep their full record while you're using the lobby. After closure, we hold the minimum required for record-keeping under supported-region rules, then the file is deleted on the schedule listed in this policy.
Yes. Use the in-account privacy form or email the data desk and we'll prepare an export of the file we hold against your bandar303 account, delivered inside our published response window.
Wallet movements are stored as references — not raw credentials. The payment rail keeps the sensitive part on its side, and we only see the fields needed to match a transaction to your account history.
Only with processors that make the lobby work — hosting, anti-fraud and payment rails — and only for the purpose described in this policy. We don't sell your file to advertisers or external data brokers.
Essential cookies keep you logged in and route your session safely. Analytics and preference cookies are optional and sit behind the consent panel you saw on first visit, where you can change choices anytime.
The change log at the foot of the page records material updates with dates. For larger shifts we surface a notice inside your account on next sign-in so the change isn't easy to miss.