Discourse
Privacy Policy
Effective —.
What this covers
Discourse helps you track what you read and augments it with AI-generated context. This policy covers both the Discourse web app and the Discourse browser extension.
What we collect
The extension only collects data while you are signed in, and only for pages you capture or that pass the relevance gate:
- Content you view or capture — the page URL, title, publisher, author, publish date, thumbnail, and the text of the article, post, or tweet.
- Engagement signals — time on page, scroll depth, and whether audio/video played, used to gauge what mattered to you.
- Facebook context (opt-in, off by default) — only if you turn on “Capture Facebook context” in the extension. When on, and only while Facebook is the tab you’re actively viewing, we read the feed your own signed-in session already loaded to find posts matching your interests, and keep four fields: the post’s text, author name, link, and whether it’s sponsored (sponsored posts are dropped). The raw Facebook data never leaves your browser. We never collect messages, private or friends-only content, notifications, or posts you don’t view.
- Social posts you act on — on X, when you summon Discourse on a specific post, the text of that post, so an agent can add context to it.
- Account data — your email and sign-in identity (Google), plus a device token that links the extension to your account.
How we use it
To build your feed, run AI agents that add context to claims, and personalize what’s surfaced. Processing uses third-party services (OpenAI, Supadata, Brave Search) under their own terms; we send them only the content needed to process a given item.
Where it’s stored
On our infrastructure (Vercel and Supabase, hosted in the United States).
Sharing
We don’t sell your data. We share content with the processing services listed above solely to provide the product.
Retention & deletion
You can delete your account and its associated data at any time from your Discourse settings. For deletion requests or questions, contact [privacy contact email].
Changes
We’ll update this page if our practices change and revise the effective date above.