LEGAL REFERENCE

Privacy Policy for Your taiwan pool Account

This is the privacy policy that governs your taiwan pool account across our live casino tables, slot rooms and sportsbook markets. We've written it for Indonesia readers in...

Account dataWallet recordsCookie useIndonesia readersPlain English

Browse the Lobby Read FAQ

How Our Privacy Posture Works

Where local law permits, taiwan pool processes your data on the lawful basis of contract performance — you opened an account, we keep it running. That means we store your registered details, verification documents, device fingerprints, session logs and transaction history tied to DANA, OVO, GoPay or QRIS top-ups. We retain this only while your account is active, plus the retention window

our auditors require for supported regions. You can request a copy, a correction, or a closure through the contact paths below, and we'll act inside the statutory window. Third-party processors who touch your data — payment routers, KYC checkers, fraud screens — are bound by written terms that mirror this policy.

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

SUPPORT

Privacy Contact Paths

If something in this policy needs clarification, or you want to exercise a data right, reach our privacy desk through any of the channels here. We aim to acknowledge within one business...

Privacy Inbox Email our data protection desk directly for access requests, correction requests, deletion requests, or any question about how a specific field on your account is processed and stored.

In-App Chat Open the chat bubble after signing in and ask for the privacy team. Your session context loads automatically so we can verify identity and answer policy questions without long back-and-forth.

Postal Address For formal notices, our registered correspondence address is published in the footer. Send signed letters here when you need a paper trail for regulators or your own legal advisers.

WHY VISITORS TRUST US

Editorial Trust Behind This Policy

This policy is reviewed by named owners, not generated and forgotten.

Policy Owner

Our data protection lead reviews this page each quarter and signs off on the version number you see at the...

Legal Review

External counsel in Indonesia checks our wording against current data protection statutes and advises when phrasing needs to track new...

Security Sign-Off

Our security engineers confirm the technical claims here — encryption in transit, hashed credentials, segregated wallet logs — match what's...

Audit Trail

Every privacy request we receive is ticketed, timestamped and resolved against a service-level target. Auditors can sample the queue to...

Processor List

We keep a current register of sub-processors handling your data. It names each vendor, the data category they touch, and...

Breach Protocol

If a security event affects your data, we follow a written incident plan: contain, assess, notify the regulator inside the...

Consistency Across Our Policy Pages

Our privacy, cookie and terms pages are written to agree with each other. Here's how this page lines up with its siblings.

Data Categories	The categories listed here match the categories named in our cookie policy and terms — no category appears in one document and disappears in another.
Retention Windows	Retention periods quoted here are the same numbers our terms reference when describing account closure and the post-closure archival window.
Lawful Basis	Contract performance and legal obligation are cited consistently. Where consent applies — marketing emails, optional cookies — that's flagged in both this page and the cookie notice.
Your Rights	Access, correction, deletion, portability and objection are described in identical language across our policy stack so there's no ambiguity about which right applies where.
Contact Routes	The privacy inbox, in-app chat and postal address shown here are the same routes published in the footer and the terms document.
Processor Disclosure	The sub-processor register linked from this page is the same register referenced by the cookie policy when third-party tags are discussed.
Version Control	Each sibling policy carries a version number and revision date in the same format, so you can cross-check which release of the stack you're reading.

What This Policy Page Includes

Quick map of the visible elements on this privacy page so you can jump straight to what you need.

Plain-English Sections

We've broken the policy into short, named sections instead of one wall of legal text. Each section has a heading you can scan and a paragraph short enough to read on a phone.

Named Owners

The trust block above names the roles that own this document. You're not reading anonymous boilerplate — there are humans accountable for what's written here.

Contact Block

Three contact paths sit inside this page itself, not buried in a separate help centre, so a data request is one click away from where you read about your rights.

Version Stamp

At the bottom of the document you'll see the current version number and the date of the last substantive change, so you know which release you're looking at.

Cross-Links

Inline links connect this page to the cookie policy, terms and sub-processor register so you can follow a reference without searching the site for it.

FAQ Block

The questions below cover the things our privacy desk gets asked most often. Read them first — your answer is likely already there before you draft an email.

Privacy Questions We Hear Often

We collect your registration details, the identity documents needed for verification, your device and session metadata, and the transaction records tied to DANA, OVO, GoPay or QRIS top-ups against your wallet.

Where local law permits, we retain core account and transaction records for the statutory window required by our auditors, then purge or anonymise the rest. The exact period is named in the retention clause above.

Yes. Email the privacy inbox listed in the contact block, confirm your identity through the standard verification step, and we'll deliver a structured export inside the response window the law sets for supported regions.

Only with the processors named in our sub-processor register — payment routers, KYC vendors, fraud screens and hosting providers. Each one signs terms that mirror this policy. We do not sell your data to advertisers.

Credentials are hashed, traffic is encrypted in transit, and wallet logs sit in segregated stores with restricted access. Our security team signs off on the technical claims before each policy revision goes live.

We follow a written incident plan: contain the event, assess the scope, notify the supervisory authority inside the statutory window, and email any account holder whose data was directly affected with concrete next steps.

The version stamp at the foot of this page updates with every substantive change, and we email registered account holders when a revision affects how their data is handled rather than just tidying wording.