HumanFeed Privacy Policy Effective date: 22 August 2026 HumanFeed is a browser extension designed to give users more control over the content shown in their social-media feeds. HumanFeed is built with privacy as a core principle. The current HumanFeed 0.3 Beta performs its feed filtering locally in your browser and does not require a HumanFeed account. This Privacy Policy explains what information HumanFeed accesses, why it is needed, how it is handled, and the choices available to you. 1. Information HumanFeed Accesses Website Content HumanFeed accesses visible content on websites where the extension is enabled so it can determine whether content matches your filtering preferences. This may include: - Post or video titles - Captions and visible text - Images and thumbnails - Hyperlinks - Creator names or handles - Visible platform labels - AI-content disclosures - Content Credentials or other available provenance information - Other visible information associated with a feed item HumanFeed needs access to this content in order to provide its core feed-filtering functionality. In HumanFeed 0.3 Beta, this processing occurs locally in your browser. HumanFeed does not send social-media feed content to HumanFeed servers for classification. Current Website Information HumanFeed may identify the website or tab you are currently viewing in order to: - Determine whether HumanFeed supports the website - Apply site-specific filtering preferences - Show the current website in the extension popup - Enable or disable filtering for that website - Apply user-created blocked-destination rules HumanFeed does not maintain or transmit a browsing-history log. 2. Information Stored Locally HumanFeed may store the following information locally in your browser: - Filtering preferences - Selected content categories - Filtering sensitivity and actions - Custom keyword, phrase, or regular-expression rules - Allowed or blocked creators - Website filtering preferences - Blocked destination domains - Temporary pause settings - Local filtering statistics - Privacy-safe diagnostic information - Extension configuration - Temporary “Show once” state This information is used to operate HumanFeed and remember your preferences. HumanFeed does not intentionally store a history of the social-media posts or pages you have viewed. 3. Local Processing HumanFeed 0.3 Beta is designed to perform feed analysis locally on your device. The current public beta does not use: - Cloud AI classification - OpenAI for feed classification - Google cloud AI detection - Remote content-analysis services - HumanFeed servers for feed classification HumanFeed may include experimental or future functionality in its source code, but cloud-based classification is not enabled in the HumanFeed 0.3 Beta public release. If a future HumanFeed feature sends content to an external service, this Privacy Policy and the product interface will be updated before that feature is enabled for users. 4. Personal Communications HumanFeed is not designed to collect or analyze private communications. HumanFeed does not intentionally collect: - Private messages - Direct messages - Emails - Chat conversations - Form contents - Draft posts or messages HumanFeed's supported-site adapters are designed to avoid private messaging and composition interfaces. 5. Authentication and Sensitive Information HumanFeed does not intentionally collect: - Passwords - Authentication credentials - Session tokens - Cookies - Security questions - PINs - Payment-card information - Financial information - Health information - Precise location information HumanFeed does not require a HumanFeed account in the 0.3 Beta. 6. User Activity HumanFeed does not create a log of your mouse movements, keystrokes, scrolling behavior, or general browsing activity. HumanFeed may react to changes in a webpage in order to detect newly loaded feed items, but this is part of the extension's local filtering functionality and is not used to build an activity profile. Local statistics may include aggregate information such as the number of items scanned or filtered. These statistics are not intended to create a record of the individual posts or pages you viewed. 7. Diagnostics HumanFeed may maintain privacy-safe diagnostic information locally to help identify extension errors or compatibility problems. Diagnostics may include information such as: - Extension version - Supported platform - Adapter status - Counts of filtering operations - Error categories - Performance information - Feature configuration states HumanFeed is designed to avoid including raw post content, passwords, private messages, authentication tokens, or complete browsing history in diagnostic exports. Diagnostic information is not automatically uploaded to HumanFeed in the 0.3 Beta. If you choose to export diagnostic information, sharing that exported file is under your control. 8. Optional Website Permissions HumanFeed supports certain social-media websites directly. HumanFeed may also offer optional filtering for additional websites. When additional website access is required, HumanFeed may ask you to grant permission through your browser. HumanFeed does not request additional optional website access unless the relevant feature requires it. You can revoke optional website permissions through Chrome's extension settings. 9. Blocked Destinations HumanFeed includes an optional blocked-destination feature. If you explicitly add a domain to your blocked destinations, HumanFeed may use browser-provided declarative network rules to prevent top-level navigation to that domain. These rules are based on preferences you create. HumanFeed does not use this feature as a general-purpose network-monitoring or advertising-tracking system. 10. Content Credentials and Provenance HumanFeed may inspect available provenance signals, including: - Content Credentials - C2PA information - Platform-provided AI labels - Creator disclosures - Other trusted provenance metadata These checks are used to help HumanFeed apply the filtering preferences you selected. Where possible, these checks are performed locally. The absence of provenance information does not mean that content was created by a human. HumanFeed does not claim to identify every piece of AI-generated content. 11. Data Sharing HumanFeed 0.3 Beta does not sell your browsing data. HumanFeed does not use your browsing activity for advertising. HumanFeed does not transfer social-media feed content to HumanFeed servers for classification in this release. HumanFeed does not transfer data obtained through Chrome extension permissions for unrelated purposes. 12. Advertising HumanFeed 0.3 Beta does not use your browsing information to deliver targeted advertising. HumanFeed does not sell browsing information to advertisers. 13. Chrome Web Store Limited Use HumanFeed's use of information obtained through Chrome extension permissions is limited to providing and improving HumanFeed's user-facing feed-filtering functionality. HumanFeed does not use or transfer information obtained through Chrome extension permissions: - For personalized advertising - For unrelated advertising purposes - For determining creditworthiness - For lending purposes - For purposes unrelated to HumanFeed's primary feed-filtering functionality HumanFeed follows the Chrome Web Store User Data and Limited Use requirements applicable to the extension. 14. Data Retention Most HumanFeed information is stored locally in your browser for as long as necessary to preserve your settings and provide the extension's functionality. You can remove locally stored HumanFeed data by: - Deleting individual rules or preferences - Clearing HumanFeed statistics or diagnostics where available - Using HumanFeed's reset function - Removing the extension from Chrome Temporary session information may be removed automatically when it is no longer needed. 15. Data Deletion HumanFeed provides controls for resetting or deleting locally stored extension information. Removing HumanFeed from Chrome will also cause Chrome to remove extension-managed local storage according to Chrome's normal extension behavior. HumanFeed does not maintain a cloud account or server-side feed-history database for users of the 0.3 Beta. 16. Security HumanFeed is designed to minimize the information it handles and to keep filtering data local whenever practical. The extension uses browser-provided security mechanisms and packages its executable extension code with the extension. HumanFeed 0.3 Beta does not download and execute remote code as part of its filtering functionality. No software can guarantee absolute security, but HumanFeed is designed to limit unnecessary collection and transmission of user data. 17. Children's Privacy HumanFeed is not designed to knowingly collect personal information from children. Because HumanFeed 0.3 Beta does not require an account and does not operate a server-side user database, HumanFeed does not intentionally maintain profiles of children or other users. 18. Changes to This Privacy Policy HumanFeed may update this Privacy Policy as the extension evolves. Material changes—particularly changes involving cloud processing, accounts, payments, or external data processing—will be reflected in an updated Privacy Policy and, where appropriate, in the HumanFeed interface before those features are made available. The effective date at the top of this policy will be updated when changes are made. 19. Contact For privacy questions, support requests, or concerns about HumanFeed, contact: Email: ThreadConfessions@proton.me HumanFeed 0.3 Beta Your feed. Your rules.