How teh 4d Handles Your Account Data
This is the teh 4d privacy policy — the document that tells you exactly what we collect when you open an account, why we store it, and how...
Policy Scope, Jurisdiction and Data Posture
Our privacy policy applies to every visit you make to teh4d.bet and every interaction tied to your account, where local law permits. We collect the data needed to verify you, route deposits, and keep your session secure — nothing speculative. Identity fields are stored encrypted, transaction references are kept for the period our auditors require, and behavioural data on the lobby is
aggregated rather than tied to your name. If you sit in supported regions across Indonesia, the rights granted to you in this policy travel with your account. You can request a copy, a correction, or a deletion at any time, and we'll action it within the windows defined in the sections that follow.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy Contact Paths
If you have a question about your data, three lanes connect you to the privacy desk. Pick whichever fits the moment — each one routes to the same team and the same response window.
Privacy Inbox
Email the privacy desk directly with your account reference. We acknowledge inside one working day and resolve standard data requests within the statutory window your region allows.
In-Lobby Chat
Open the chat bubble after you sign in and ask for the privacy team. The agent flags your ticket so it bypasses general queues and lands with a data handler.
Deletion Form
Submit the structured deletion form linked from your account settings. It captures the identifiers we need so we can verify the request belongs to you before anything is removed.
How We Keep This Policy Honest
Editorial trust matters on a legal page. Here's how the privacy policy you're reading is maintained, reviewed and kept aligned with what actually happens on our servers.
Quarterly Review
Our compliance team re-reads this document every quarter and flags clauses that no longer match how the lobby works. Outdated...
Engineering Sign-Off
Each policy change is countersigned by the engineer who owns the data pipeline it describes. If the code and the...
Indonesia Counsel
We retain local counsel familiar with Indonesian data expectations. Their notes shape how we phrase consent, retention and cross-border transfer...
Plain Language
We strip legalese before publishing. If a paragraph cannot be read by someone outside the legal team, it gets sent...
Version History
Every published version of this policy is archived. You can request the prior text if you want to compare what...
Named Owner
A single data protection lead owns this page. That accountability means questions land with a person, not a shared inbox...
Consistency Across Our Policy Pages
This privacy policy sits alongside our terms, cookie notice and account-closure pages. The table below shows how the wording stays consistent so you aren't told one thing here...
| Definitions | Terms like account, session and identifier carry the same meaning across privacy, terms and cookie pages, so a clause you read here means the same thing on the next page. |
|---|---|
| Retention Windows | Storage periods quoted in this privacy policy match the windows referenced in our terms. Numbers are pulled from one source so they cannot drift apart between documents. |
| Contact Routes | The privacy inbox, chat path and deletion form appear identically wherever they're cited. One canonical list, reused, prevents stale email addresses from lingering in old pages. |
| Jurisdiction Wording | We use the same phrase — where local law permits — across every legal surface. That keeps your regional rights described consistently from policy to terms. |
| Update Dates | The revision stamp on this policy aligns with the changelog on sibling pages. If one moves, the others are reviewed in the same release cycle. |
| Rights Language | Access, correction and deletion rights are described in matching terms across pages, so the rights you read about here are the rights you'll see invoked elsewhere. |
| Tone | Plain English is used consistently. Neither this policy nor its siblings switch to dense legalese halfway through — readability is held to the same bar across the set. |
What This Policy Page Shows You
Beyond the legal substance, the page itself is designed so you can find the clause you need fast. These are the visible elements that shape the...
Section Anchors
Jump links at the top let you skip straight to retention, deletion or contact without scrolling the full document. Useful when you're returning to re-check a single clause.
Last-Updated Stamp
A clear revision date sits near the title so you know whether the text in front of you reflects the current build or a version you read months ago.
Defined Terms
Key words are highlighted on first use and linked to a short definition. Hover or tap to see what we mean before the clause leans on the term.
Print View
A clean print stylesheet strips the navigation so you can keep a paper copy of the policy as it stood on the day you signed in.
Change Log
A short summary of what moved between the last version and this one sits at the foot of the page, so returning readers see deltas without re-reading everything.
Reader Feedback
A one-line feedback prompt at the bottom lets you flag a clause that reads unclearly. Your note routes to the policy owner, not a generic inbox.