LEGAL REFERENCE

Our Privacy Policy at asiabet138

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...

Account dataCookiesRetentionYour rightsIndonesia
asiabet138 Our Privacy Policy at asiabet138

How We Handle Your Account Data

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

PLAYER SUPPORT

Reach Us About Your Privacy

Privacy Inbox Send data-access, correction or deletion requests straight to our privacy desk. We log every ticket, reply inside the statutory window, and confirm in writing once your record has been updated or removed.
Live Chat Open the chat bubble inside your account and ask for the privacy team. The agent will route you to a specialist who can verify your identity and walk through what we hold on file.
Compliance Desk For regulator-level questions or formal complaints, our compliance desk takes written submissions. Include your account reference and we'll acknowledge receipt the same business day where local law permits.
TRUST MARKERS

Why You Can Rely on This Policy

Reviewed Quarterly

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.

Encrypted Storage

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.

Named Owners

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.

Plain Wording

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.

Independent Audit

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.

Indonesia Focus

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.

BENCHMARKED

Consistency Across Our Policy Pages

01

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.

02

Cookie Notice

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.

03

AML Statement

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.

04

Payments Policy

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.

05

Promotions Rules

Promo eligibility data — entries, opt-ins, exclusions — follows the retention clock set here. Marketing teams cannot extend the window unilaterally.

06

Complaints Charter

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.

07

Account Closure

The closure flow ends with the purge schedule described here. Whatever the help centre tells you about closure, this policy is the binding version.

AT A GLANCE

What Defines This Privacy Page

01
Dated Revisions Every update to this document carries a revision date and a short summary of what changed. Scroll to the footer of the policy and you'll see the trail rather than a single undated block.
02
Section Anchors Each clause has its own anchor link. If support points you at a specific paragraph, the URL drops you exactly there instead of leaving you to scan the whole document on a phone screen.
03
Reader-First Layout Headings sit above the legal text in larger type. The structure is built so you can skim on mobile, find the clause you need, and read just that part without losing your place.
04
Defined Terms Words like account, processor and personal data are defined in one place and used consistently. No silent swaps between paragraphs, no terms that mean one thing in clause four and another in clause nine.
05
Contact Block A live contact block sits at the bottom with the privacy inbox, chat route and compliance desk. You never have to leave the policy to find out where your question should land.
06
Change Log A short change log records material edits. If we tighten a retention period or add a processor, the entry shows the date and the affected clause so you can track our direction over time.

Privacy Policy Questions

We collect your name, contact details, date of birth, device identifiers and the wallet handle you fund with. That set lets us verify your identity, run fraud checks and route DANA, OVO, GoPay or QRIS transactions correctly.

Yes. Send a request through the privacy inbox and we'll prepare an export of your record. We verify your identity first, then deliver the file inside the window your jurisdiction sets for access requests.

Active records are removed shortly after closure. A minimal compliance trail — enough to satisfy anti-money-laundering and tax obligations — is retained for the statutory period, then purged on schedule from our encrypted archives.

No. We don't sell personal data. Marketing partners receive aggregated, non-identifying signals only. Identity-level data stays with us, our payment processors and the regulators entitled to request it through proper legal channels.

Wallet handles are treated as sensitive payment identifiers. They're encrypted at rest, masked in our internal tools, and only decrypted when a transaction or a logged compliance review genuinely requires the full value.

Material changes are dated at the top of the page and recorded in the change log. Where local law requires it, we'll also notify you inside your account before the new wording takes effect for your record.

Start with our compliance desk using the contact block on this page. If you're not satisfied with our response, you can escalate to the data-protection authority covering supported regions where your account was registered.