LEGAL REFERENCE

How teratai 888 Handles Your Account Data

This is our privacy policy in plain language. We explain what we collect when you open an account with teratai 888, why we hold it, and the controls...

Account dataCookies explainedYour controlsIndonesia scopeLast updated
teratai 888 How teratai 888 Handles Your Account Data

Our Privacy Posture and Your Rights

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

HELP CHANNELS

Privacy Contact Paths

Data requests inbox Write to our privacy desk for access, correction...
Live chat for policy queries Open the chat bubble in the lobby and...
Account settings panel Sign in and head to your settings to...
WHY THIS PLATFORM

How We Keep This Policy Honest

Reviewed quarterly

We revisit this policy every quarter so the wording matches what our systems actually do. When something changes on the back end, the public text here changes with it on the same release.

Named data owner

A specific team inside teratai 888 owns this document, not an anonymous legal mailbox. That person signs off every revision and is the one your privacy ticket eventually reaches.

Plain-language drafting

We write in the same tone you'd hear in chat. If a clause needs a defined term, we define it inline rather than burying meanings in a glossary you'd have to scroll for.

Processor list maintained

Every third party that touches your data — verification, payments, analytics — is listed and reviewed before onboarding. We drop processors that can't meet our handling standards for Indonesia traffic.

Change log kept

Material edits are logged with a date and a short note on what moved. You can scan the log and see whether the change affects your consent or just tidies the language.

Independent checks

Our security and data flows are tested by external assessors on a fixed cycle. Findings feed back into both the technical controls and the wording you're reading on this page.

Consistency Across Our Legal Pages

Terms of Service
The data points named here match the account obligations described in our terms. No surprise category appears in one document and goes missing in the other.
Cookie Notice
Cookie categories listed in the banner mirror the tracking section of this policy. Toggle a category off there and the same scope drops here.
AML Statement
Verification data we hold under AML rules is described with the same retention windows you'll read in the dedicated statement, so nothing contradicts.
Payments Terms
Wallet identifiers for DANA, OVO, GoPay and QRIS are handled the way the payments terms describe — same processors, same retention, same access path.
Account Closure
The closure flow referenced here matches the one inside your settings panel. What you trigger in-app is what this policy promises in writing.
Marketing Preferences
Opt-in language on this page lines up with the toggles in your account. Turning marketing off in one place turns it off everywhere we send from.
Complaints Path
The escalation route in this policy is the same one our complaints page lists, so a privacy issue and a service issue follow one consistent ladder.

What This Policy Page Shows You

Scope panel

A clean summary at the top tells you which teratai 888 surfaces this policy covers — lobby, sportsbook, slot rooms and account area — so you don't have to guess what's in scope.

Data category list

Every category we collect is broken out with the reason we need it. Identity, device, transactional and preference data each sit under their own heading instead of one wall of text.

Retention windows

We name how long each category stays with us and what triggers deletion. Where statute fixes a minimum, we say so; where we choose the window, we explain why.

Your-rights block

Access, correction, portability and erasure rights are spelled out with the exact channel to use. No legal scavenger hunt before you can act on them.

Processor disclosure

A short table names the processors that touch your data and the function they serve. Any addition shows up here before it goes live in the back end.

Update timestamp

The last-modified date sits at the top of the page, paired with a one-line summary of what changed since the previous version. No silent edits.

Privacy Questions Visitors Ask Us

We collect your name, contact, the wallet you fund from — DANA, OVO, GoPay or QRIS — and the device signals needed to keep the session secure. Nothing else is required to get you into the lobby.

Identity and transactional records stay for the period local financial rules require, typically several years. Marketing preferences and device signals drop sooner, on the schedule named in the retention block above.

Yes. Email the privacy desk or open a ticket from your settings panel. We confirm the request the same day and return your file inside the statutory window that applies to your region.

No. We don't sell account data. Processors we contract are bound to use what we share only for the function we hired them for — verification, payment routing, fraud checks, analytics — and nothing beyond that.

Sign in, open your settings, and flip the marketing toggles off. The change applies across email and SMS the moment you save. Lobby access and account features are unaffected by the choice.

On access-controlled infrastructure with processors we've vetted for Indonesia traffic. Cross-border transfers, where they happen, sit under contractual safeguards we describe in the processor disclosure section of this page.

The timestamp at the top moves and a short note explains what shifted. Material changes that affect your consent trigger an in-account notice before they take effect, so nothing slides past you quietly.