Terms of Service
The terms page sets the contract; this privacy page explains the data side. Definitions match across both — an account here means the same account there, with no quiet redefinitions in the footnotes.
This is the privacy page for asiabet138. We've written it so you know exactly what we collect when you open an account, what we do with that information...
We collect the basics needed to run your account: name, contact details, device fingerprint, and the e-wallet handle you choose to fund with. That data is processed where local law permits and stored on encrypted servers covering supported regions. We do not sell your information to third parties. We share it only with licensed payment processors, fraud-screening partners, and regulators who request
it through proper channels. You can ask us to export, correct or delete your record at any time, and we'll act on the request inside the windows our jurisdiction sets. If you close your account, we keep a minimal compliance trail for the period the law requires, then purge the rest. Payment-context chips below show which rails apply to your record.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Our legal team reads this policy every quarter against fresh guidance from Indonesian and regional regulators. When wording shifts, we publish a dated revision and flag the change at the top of the page.
Your identity documents and wallet handles sit behind layered encryption. Only staff with a logged business reason can decrypt a record, and every access leaves an audit line our compliance team reviews.
This policy has named owners inside our company, not an anonymous mailbox. If you escalate, a real person signs the response and stays on the ticket until you confirm the matter is closed.
We strip the legalese where we can. If a clause needs precise language to stay enforceable, we keep it and add a plain-English line beneath so you actually understand what you're agreeing to.
An external auditor checks our data-handling controls on a fixed cycle. Findings flow back into this document, so what you read reflects what the auditor verified, not just what we wrote internally.
We tune retention and disclosure rules to the Indonesian market first. DANA, OVO, GoPay and QRIS handles are treated as sensitive payment identifiers, not casual marketing data points.
The terms page sets the contract; this privacy page explains the data side. Definitions match across both — an account here means the same account there, with no quiet redefinitions in the footnotes.
Our cookie notice expands the tracking section here. Categories, vendors and opt-out switches use the same names on both pages so you don't have to translate between documents.
Anti-money-laundering checks reference the identity data described here. Retention windows align, so you won't see one page promising deletion while another quietly holds the same record.
Wallet handles for DANA, OVO, GoPay and QRIS are handled identically across the payments policy and this notice. One source of truth, mirrored where it needs to appear.
Promo eligibility data — entries, opt-ins, exclusions — follows the retention clock set here. Marketing teams cannot extend the window unilaterally.
Response times quoted in the complaints charter match the privacy timelines on this page. If we owe you a reply in ten days for a data request, the charter says the same.
The closure flow ends with the purge schedule described here. Whatever the help centre tells you about closure, this policy is the binding version.