Terms of Service
The account rules referenced in our terms align with the data points listed here, so what you agree to at signup is what we describe on this privacy page.
This is our privacy policy in plain English. We tell you what we collect when you open an account with bingkaibet, why we keep it, and how long...
We collect what your account needs and nothing extra: name, contact, device fingerprint, wallet references and gameplay logs tied to your sessions. Where local law permits, we process this data to keep your lobby working, your payouts traceable and your login secure. In supported regions of Indonesia, we honour requests to access, correct or remove your records, subject to financial-record retention rules.
Third-party processors handling QRIS routing or e-wallet confirmations see only the fields they need to settle a transaction. We never sell your profile, and marketing contact stays opt-in from the moment you confirm your email.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Email our privacy desk directly for access, deletion or correction requests on the data tied to your bingkaibet account. Replies land within two working days where local law permits.
Open the in-lobby chat and ask for the privacy team. The agent flags your ticket so a policy reviewer, not a general host, handles your account question end to end.
Send a signed letter if you prefer paper trails for legal records. We log receipt, route it to our data officer and confirm the action taken on your file.
Our policy editor signs off every revision before it reaches this page, so wording you read here matches the controls...
We revisit the document each quarter, comparing it against payment-partner contracts and Indonesia data-handling expectations, then publish the dated change...
No buried clauses, no twelve-line sentences. If a paragraph needs a lawyer to decode, we rewrite it until a first-time...
Processors touching QRIS settlement or e-wallet confirmation are reviewed annually. We drop partners who cannot evidence the access controls our...
Session logs, KYC scans and wallet receipts each have their own clock. When the clock runs out, the record leaves...
A real person owns this policy. Your written request reaches that desk, not a generic queue, and the response carries...
The account rules referenced in our terms align with the data points listed here, so what you agree to at signup is what we describe on this privacy page.
Tracking pixels and session cookies covered in the cookie notice are summarised here too, with the same retention windows and the same opt-out switch.
Identity documents handled under our KYC statement follow the storage limits printed here. No quiet exceptions, no longer holding periods buried elsewhere.
DANA, OVO, GoPay and QRIS routing details in the payment disclosure use the same processor list named in this policy's vendor section.
The closure flow honours deletion windows we promise here. When you close, the timeline you read on this page is the timeline we follow.
Opt-in language on the marketing settings page mirrors the consent wording in this policy, so toggling one updates the record described in the other.
Escalation routes printed here match the complaint page exactly, including the data officer's contact and the response window we commit to.