What does AfterFeed capture?
AfterFeed watches supported X pages only after you sign in and turn feed tracking on in the extension. It looks for eligible Posts displayed to you there and records the minimum data needed to power Reflection: the Post identifier and URL, when the Post was visible, how long it held your active attention, and how many times it was seen during the session. It also records whether you liked or expanded the Post, or opened its detail page.
The extension does not intentionally collect private messages, passwords, payment card numbers, X account settings, follower lists, or unrelated browsing history through the Post capture flow. Post content may still include names, handles, images, or other information visible in the rendered Post.
This may include Posts available to you because you subscribe to an account. AfterFeed processes only content rendered in your browser and does not bypass X's access controls.
What stays in your browser?
Attention is measured locally first. A Post qualifies for capture only if it holds your active attention past a minimum threshold, currently ten cumulative seconds; briefer glances are discarded in the browser and never sent. A session's qualifying Posts are used at session end to generate Reflection topics. Turning feed tracking off or signing out abandons the session in progress and deletes its unsynced local data.
How does capture become Reflection?
The full text of qualified Posts, including text from a subscriber-only Post, is sent together to a language model provider (currently DeepSeek) to select meaningful Posts, group them into topics, and generate linked summaries. That session text is processed transiently and discarded; AfterFeed does not persist a separate copy of the raw Post body.
AfterFeed stores the generated topics, linked summaries, and your Useful, Not sure, or Not useful feedback. Optional suggestions are processed by a separate language-model step into one account-level Reflection Memory, which is included with future Reflection requests. You can view or reset that Memory in the dashboard.
How does AfterFeed use your information?
AfterFeed uses the information described in this policy to:
- operate feed tracking and topic-based Reflection;
- generate topic summaries and maintain Reflection Memory on Pro;
- authenticate accounts and apply plan entitlements;
- process subscriptions and provide billing support;
- diagnose failures that you choose to report; and
- protect the service from abuse, fraud, and security threats.
AfterFeed's use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Which service providers does AfterFeed use?
AfterFeed stores account identifiers needed for sign-in, ownership, entitlement checks, support, and deletion controls. Google and Supabase provide authentication and backend infrastructure. Vercel hosts the web app and provides web analytics. DeepSeek currently provides language model processing for AI features. Stripe processes subscriptions, payments, tax calculations, invoices, and receipts. AfterFeed provides billing support and does not receive or store complete card details.
What can you control, and how long is data kept?
You can turn feed tracking off in the extension at any time. You can also delete captured encounters, Reflections, feedback, and Reflection Memory from the Privacy section of your dashboard without deleting your account or changing billing. Captured data is otherwise kept until you delete it. Transaction records may be retained by Stripe or AfterFeed where required for legal, tax, fraud-prevention, and accounting obligations.
How does AfterFeed protect your information?
AfterFeed uses access controls and account-scoped records intended to prevent one account from reading another account's data. Service providers also apply their own security measures. No online service can guarantee absolute security, so AfterFeed limits collection and gives you controls to delete captured data.
What privacy requests can you make?
Depending on where you live, you may have rights to request access, correction, deletion, or a copy of personal information associated with your account. The dashboard provides direct deletion controls for captured data and Reflections. Deleting your account itself is handled by email: send a request to support@afterfeed.app from the Google account email you sign in with, and AfterFeed will delete the account and its associated data, subject to the retention exceptions described above. Other privacy requests can be sent to the same address and should identify the Google account used to sign in.
What is included in a diagnostic report?
If the extension fails to capture a Post, you may choose to share a diagnostic report. AfterFeed receives the error details and timestamp, a snapshot of the full page as it appeared at that moment, and the extension and browser versions. The page URL is not included. Reports are never collected automatically.
Diagnostic reports are stored without an account identifier or email by default. You may choose to include your account email for follow-up. Reports are retained for at most 30 days.
Can this policy change?
AfterFeed may update this policy as the product evolves. Updates appear on this page with a new last-updated date. For material changes to how personal information is collected or used, AfterFeed will give reasonable advance notice — such as by email or an in-product notice — before the change takes effect.
How can you ask a privacy question?
Questions and privacy requests can be sent to support@afterfeed.app. Do not include passwords, payment card details, or other sensitive information in your message.