How ThreadEast works
ThreadEast is a discovery and context layer over selected public trend pages. Its daily archives preserve observations; rankings do not provide a truth score.
Minimal collection
We collect list-page metadata: title, rank, public URL, source heat label, and capture time. Daily archives preserve a final observed listing for longitudinal analysis. We do not store article bodies, comments, videos, account data, or user profiles.
Direct provenance
Every signal names its source and links to the original public page. Source rankings describe attention on that platform; they do not prove that a circulating claim is true.
Cadence and freshness
Collection is scheduled every 12 hours for current production sources. First and last observed timestamps describe our captures, not original publication dates. Successful fetching does not prove a list changed. Source status separately shows the last successful fetch and most recent newly recorded URL; a freshness warning requires verification rather than proving an upstream fault.
Reading and measurement
Guides and coverage briefings provide explicit context and sources. Automated topic translations remain distinct from these articles. We count actual page navigation, 30 seconds in the foreground, and link actions in daily aggregates. We do not store analytics IPs, emails, raw query parameters or persistent visitor identifiers. DNT and Global Privacy Control disable this measurement. These counts are not unique readers, confirmed subscriptions or proof of reading.
Bounded AI
Automation translates only known titles and classifies broad categories. It must not invent people, dates, causes, outcomes, or background. Model and prompt versions are retained internally.
Automatic publishing
Collected public titles are translated, categorized, and published automatically. Trend pages use recorded rankings to calculate observation spans and within-platform movement. These measurements describe ThreadEast coverage, not total audience size.
Responsible sources
Sources must be public, policy-checked, and registered before collection. We do not automate logins, solve CAPTCHAs, evade access controls, or collect from sources that prohibit it.
Corrections and removal
We correct material errors visibly and retain correction metadata. Rights holders and source operators can request source-specific removal or correction.
View correction process