Copyright Policy
Last updated: May 7, 2026
How DevFeed uses third-party content
DevFeed indexes publicly available RSS and Atom feeds selected by users or listed in our catalog. We display feed metadata, article excerpts, and links back to the original source. Original articles remain owned by their publishers and authors.
To help an authorized reader find a Feed Article, DevFeed may privately index text supplied by its feed and validated text extracted from the publicly available original. Extracted text is not displayed as an article body, search excerpt, or snippet. DevFeed is a discovery and attribution product, not a complete publisher archive.
AI-generated summaries are created to help users decide what to read. They should not be republished as a substitute for the original article.
Requesting removal or correction
Send copyright, takedown, removal, or source-exclusion requests to [email protected]. Include:
- The DevFeed URL or original article URL involved
- The publisher domain or feed URL if you want future fetching excluded
- Your name and relationship to the content owner
- A short description of the issue
- The requested action: correction, removal, article exclusion, feed exclusion, or domain exclusion
- A contact email for follow-up
What we may do
We may remove individual articles, suppress a catalog blog, stop fetching a feed or domain, correct metadata, or ask for additional information. Source suppression removes matching content from reader surfaces immediately. When a publisher-scoped purge is required, we remove stored feed bodies, validated extracted text, materialized AI outputs, search matches, and copied online Briefing text while retaining only attribution, reader-state, and non-reconstructable audit evidence needed to prove the operation.
Online removal takes effect when the purge completes. Encrypted backups expire under DevFeed's verified backup schedule; append-only recovery logs may be retained longer for disaster recovery. Removing suppression later does not restore purged text. New content can return only through normal fetching after suppression is deliberately removed.
We also reserve the right to reject incomplete or abusive requests.