LEGAL REFERENCE

How We Handle Your Account Data

This is the texas189 login privacy policy — the page that tells you, plainly, what we collect when you open an account, what we keep on file, and...

Account dataLogin recordsPayment referencesCookiesIndonesia-first
Enter Game Lobby Read FAQ
texas189 login How We Handle Your Account Data

Our Privacy Posture, Plainly Written

We collect only what your account needs to work: your name, contact handle, login timestamps, and the payment references tied to DANA, OVO, GoPay or QRIS transactions. Where local law permits, we retain these for the period required by Indonesian financial and gaming regulations, then we purge. We don't sell your data to third parties, and marketing contact is opt-in from your

dashboard. Internal access is limited to staff handling verification, payouts and fraud checks. If you close your account, we keep only the minimum mandated by supported-region rules, and the rest is removed on a documented schedule you can request in writing.

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

PLAYER SUPPORT

Privacy Contact Paths

If you have a privacy question, a data-access request, or you want something corrected on file, reach us through any of the channels below. We answer privacy mail faster than general support because the team that handles it is smaller and more focused.

Team online

Privacy Inbox

Email our data team directly for access requests, corrections, or deletion under supported-region rules. We aim to acknowledge within one business day and resolve inside fourteen.

Live Chat

Open the chat bubble from any lobby page and ask for the privacy desk. The agent will escalate to a named officer rather than answer generic policy questions themselves.

In-Account Form

Signed-in users get a privacy form inside the dashboard. Submit there if you want a written trail tied to your account ID and verified identity on record.

EDITORIAL CLARITY

How This Policy Is Reviewed

Quarterly Review

Our policy is re-read every quarter against current Indonesian data rules, and any change to wording, retention windows or contact paths is dated at the foot of this page for you.

Named Officer

A specific data protection officer signs off on this document. That person — not a generic inbox — owns escalations, audit responses and any cross-border data questions you raise with us.

Plain Language

We deliberately avoid legalese. If a clause can be said in one sentence of normal English, we say it that way so you actually finish reading instead of skimming.

Versioned Edits

Older versions of this policy are archived and available on request. You can compare what changed, when it changed, and which paragraph was rewritten without trusting our summary.

Independent Audit

Security and storage practices behind this policy are checked by an external reviewer annually. The audit covers encryption at rest, access logs and the deletion workflow described above.

Reader Feedback

If a paragraph here confuses you, tell us. We've rewritten sections more than once because a reader flagged ambiguous wording, and credit goes in the changelog at the bottom.

Consistency Across Our Policy Pages

Cookie Notice
The cookie page uses the same retention windows quoted here, so you won't find one number on this page and a different number two clicks away.
Terms of Service
Data clauses inside our terms point back to this document rather than restating rules, which keeps a single source of truth for what we hold.
KYC Notice
Verification documents are described identically on the KYC page — same storage period, same access list, same deletion trigger when your account closes.
Payments Policy
References to DANA, OVO, GoPay and QRIS data on the payments page match the categories listed here, including how long transaction IDs stay on file.
Marketing Preferences
Opt-in language on the preferences page mirrors the consent paragraph in this policy so toggling one setting has the effect this document promises.
Account Closure
The closure flow follows the deletion schedule named here. Nothing is held longer than this page says, except where Indonesian law specifically requires it.
Complaints Path
Dispute steps echo the contact channels in this policy, so a privacy complaint and a general complaint both reach the same documented escalation ladder.
PLATFORM SNAPSHOT

What This Policy Page Includes

Scope Statement The opening clause tells you exactly which texas189 login services...
Data Categories A clean list of what we collect — identity, contact...
Retention Windows Specific timeframes for each data category, not vague phrases like...
Your Rights A dedicated block explains access, correction, deletion and portability rights...
Third Parties Named categories of processors — payment partners, verification vendors, hosting...
Change Log A dated list at the foot of the page showing...

Privacy Questions We Get Often

We keep your name, contact handle, date of birth for age checks, your chosen payment reference for DANA, OVO, GoPay or QRIS, plus login timestamps. Nothing beyond that is collected at sign-up.

No. We don't sell account data and we don't pass identifiable details to ad networks. Aggregate, non-identifying traffic figures may be shared with analytics vendors named in the third-parties section above.

Transaction references tied to DANA, OVO, GoPay and QRIS are held for the period Indonesian financial rules require, typically five years, then purged on a documented schedule you can request in writing.

Yes, where local law permits. Submit the in-account form or email the privacy inbox. We'll confirm receipt, complete deletion within the regulatory window, and keep only what statute specifically forces us to retain.

Active marketing data is removed immediately. Verification records and transaction logs follow the retention windows on this page, then they're erased. You'll get a written confirmation once the cycle finishes.

Primary storage sits with hosting partners serving the Indonesia region. Backup copies may live in secondary locations named in our third-parties block, all encrypted at rest and accessed only by cleared staff.

Every revision is dated in the change log at the foot of this page. Material changes also trigger a dashboard notice the next time you sign in, so you don't miss anything important.