Same Definitions
Terms like account data, session metadata and payout handle mean the same thing here as on our terms and KYC pages — no quiet redefinitions between documents.
LEGAL REFERENCE
How teh4d Handles Your Account Data
This is the teh4d privacy policy in plain language. We explain what account details we collect when you open a lobby session, why we need them for KYC...
Plain-English PolicyLast Reviewed QuarterlyIndonesia-Aware WordingAccount Data OnlyContactable Privacy Desk
Privacy Posture and Jurisdiction Notes
We collect the account details you submit at signup — name, contact, date of birth, payment handle — plus session metadata our systems log when you browse the lobby. This data supports KYC checks, fraud screening and payout routing where local law permits. We retain records for the period our supported regions require, then archive or delete them on a fixed schedule.
We do not sell your data. Third parties only receive what's needed to clear a transaction, verify identity, or meet a regulator request you'd expect us to honour. Your rights to access, correct or remove records are described in the support section below.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
HELP CHANNELS
Privacy Contact Paths
Privacy Desk Email
Write to our privacy desk for data access, correction or deletion requests. Include the email tied to your teh4d account so we can verify ownership before any record is touched.
In-App Policy Chat
Open the chat bubble in your lobby and choose the privacy topic. Our agents route policy questions straight to the review team rather than the general support queue, so answers stay specific.
Written Notice Address
For formal data subject requests you'd like on paper, our registered correspondence address is published in the footer. Allow extra working days for postal handling and identity verification on those filings.
PLATFORM TRUST SIGNALS
How This Policy Is Maintained
Quarterly Review
Our policy team re-reads this document every quarter against the rules our supported regions publish. If anything material shifts, we...
Legal Sign-Off
Each substantive edit goes through legal counsel familiar with Indonesian data handling expectations before it reaches your screen. We don't...
Plain Language First
We rewrite legalese into sentences you can actually parse. If a clause needs a technical term, we define it in...
Change Log Kept
Older versions of this policy stay archived internally. If you ask which wording applied when you opened your account, our...
Named Owner
A single privacy lead owns this page end to end. That person signs off on edits, answers escalations, and reports...
No Dark Patterns
Consent prompts on teh4d are written to be skipped or accepted with equal ease. We don't bury opt-outs, pre-tick boxes...
PLATFORM COMPARISON
Consistency Across Our Policy Pages
Aligned Retention
Retention windows quoted here match the figures listed in our internal data schedule and on the KYC notice. One source of truth, mirrored everywhere you read it.
Shared Contact Desk
The privacy email on this page is the same desk referenced from terms, cookies and KYC. You won't get bounced between inboxes when your question crosses topics.
Matching Jurisdiction Wording
Phrases like where local law permits and supported regions appear identically across policy pages, so the scope of our service stays unambiguous wherever you check.
Unified Update Date
When this policy is revised, sibling pages affected by the same change are republished on the same day to prevent stale cross-references appearing in your reading.
Single Owner
Our named privacy lead owns this document and the cookie notice together, so the tone and depth stay consistent rather than reading like two different authors.
Cross-Linked Clauses
Where a clause here depends on the terms or KYC text, we link directly to the relevant section instead of paraphrasing, keeping you anchored to the authoritative wording.
SERVICE CONTEXT
What This Policy Page Covers
01
Scope Statement
The opening block tells you exactly which teh4d services this policy governs — lobby sessions, sportsbook tickets, slot play and account management — so you know what's in and out of scope.
02
Data Categories
A clear list of the data types we hold: identity fields, contact details, payment handles, session logs and support correspondence. Each category is described in everyday language with examples.
03
Purpose Mapping
Every category is tied to a stated purpose — KYC, payout routing, fraud checks, customer support — so you can see why a given field exists in your record at all.
04
Retention Block
A dedicated section sets out how long each data category lives on our systems and what triggers archival or deletion once the retention window has fully elapsed.
05
Your Rights
Access, correction, deletion, portability and objection rights are listed with the practical steps to invoke them, including which channel reaches our privacy desk fastest.
06
Update History
At the foot of the page you'll find the last reviewed date and a short note describing what changed in the most recent revision, so repeat readers spot edits quickly.
Privacy Policy Questions
Identity details from signup, your contact channels, the payment handle you link for deposits and withdrawals, and session metadata our systems log while you browse the lobby. Nothing beyond what the account flow requires.
Yes. Send a data access request to our privacy desk from the email tied to your teh4d account. We verify ownership, then return a structured export within the timeframe our supported regions require.
Retention follows the schedule our supported regions mandate for account, KYC and transaction data. Once the window closes, records are archived or deleted on a fixed cycle rather than left sitting on active systems.
Only where needed — payment processors clearing your DANA, OVO, GoPay or QRIS movement, KYC vendors verifying identity, and regulators making lawful requests. We do not sell account data to marketers under any circumstance.
Message our privacy desk with a closure and deletion request. We settle any open balance, complete required record-keeping for our supported regions, then remove or anonymise remaining fields per the retention schedule above.
The last reviewed date at the top of the page updates with every revision, and a short change note describes what shifted. Material changes also trigger a notice on your next lobby sign-in.
Our named privacy lead handles everything on this page. Reach them through the privacy desk email or the in-app chat privacy topic, and your message routes directly rather than sitting in general support.