Privacy Policy
How DevFeed processes account information, preferences and usage data, and how to contact us about your privacy.
Effective and last updated:
1. About this policy
This policy covers DevFeed at devfeed.tech, the DevFeed extensions for Chrome and Microsoft Edge, and the services that support them. DevFeed is a developer-content discovery service. You can browse without signing in; an account is optional for personalization and contributions.
This policy does not cover independent publishers or identity providers. Their policies apply when you use their services. See also our Terms of Service.
2. Information we process
- Account information: an identifier from our sign-in service, your name and email, organization membership, and sign-in timestamps. We use ZITADEL with supported providers such as GitHub. DevFeed does not receive your GitHub password.
- Profile and preferences: a display name or photo URL you choose to save, followed topics and sources, likes, feed and appearance settings, and notification preferences.
- Contributions and correspondence: source suggestions, their review status and information you send when contacting us.
- Usage and operational information: original-article clicks, search requests, analytics events, request timing, errors and information needed to deliver and protect the service.
Our infrastructure and providers necessarily process connection information such as IP addresses and browser request details. This is separate from DevFeed’s article-click records, which use account or random browser identifiers rather than storing IP addresses or browser fingerprints.
3. DevFeed browser extensions
Each extension replaces its browser’s new-tab page with the DevFeed reader. It requests access to https://devfeed.tech/* to retrieve feeds, articles, topics, sources and search results, and to provide optional account features. It does not read your browser’s general browsing history, inspect other tabs, or inject content scripts into websites.
When you sign in through the website, your browser supplies the existing HttpOnly session cookie with authenticated requests. The reader receives your account identifier, name, email and session-expiry information and uses a CSRF token for account changes. Your profile, bookmarks, likes, follows, settings, source suggestions and notification actions are processed by DevFeed. Search text is sent to DevFeed to return results. Passwords are handled by the sign-in provider, not by the extension.
DevFeed records original-article clicks made through the reader for counts and abuse prevention. These records concern activity within DevFeed, not your browsing on other websites. Infrastructure and image providers process connection information such as IP addresses; the extension does not request GPS or device-location access.
The extension caches public article and topic records in tab storage to support previews after a reload. Cached snapshots are checked for a 24-hour expiry when loaded; browser storage limits can remove them sooner. This cache excludes account profiles, session cookies, CSRF tokens, personal engagement state and recommendation reasons. Theme and interface preferences may also be stored locally. Publisher images are requested directly from their hosts without a referrer.
4. How we use information
We use this information to authenticate users, save settings, personalize recommendations, deliver in-app notifications, review source suggestions, respond to requests, measure useful features and keep DevFeed secure and reliable.
Recommendations use signals such as follows and likes together with article freshness and topic relationships. You can change these signals through your preferences and likes, or browse the public feed without signing in.
6. Google Analytics
The public production website uses Google Analytics 4 to understand visits and feature usage. Google can receive page URLs, referrers, browser and device information, cookie identifiers and interaction data. Its collection and processing are described in How Google uses information from sites or apps that use its services and Google’s Privacy Policy.
When enabled, the Chrome and Edge extensions send normalized page views, focused reading time and feature interactions through DevFeed’s server to a separate Google Analytics property. A random installation identifier and analytics session are stored locally. Extension analytics do not send your account identity, session cookies, CSRF tokens, search text, article titles or URL query parameters to Google. Article and follow events can include public article, topic or source identifiers.
Extension analytics respect Do Not Track and Global Privacy Control signals. You can also disable extension analytics by setting the local storage item devfeed:extension-analytics-disabled to true in the extension’s DevTools and reloading the tab. Removing the extension removes its local storage but does not delete account or analytics records already held by the service or providers.
Our custom events include original-article clicks, likes, follows, source suggestions and saved preferences. Those event payloads do not include your name, email, account identifier, submitted source URL or free-text input. Standard page URLs can include search or filter parameters, so do not put confidential information into searches or URLs.
You can manage cookies in your browser and use Google’s Analytics opt-out browser add-on where supported. These controls do not disable DevFeed’s separate article-click abuse protection.
7. Service providers and external content
We use infrastructure and services to run DevFeed, including Cloudflare for web delivery and protection, our hosted ZITADEL sign-in service, GitHub when selected for sign-in, Google Analytics for measurement, and our hosted notification service for in-app notifications.
AI services, including OpenAI, process public article, source and taxonomy content to produce summaries, classifications and research. A submitted public source URL and its retrieved content may be processed during source assessment. Do not submit private or confidential material.
Publisher images, logos and profile photo URLs may be loaded from external hosts. Those hosts can receive connection information when your browser requests an image. Following an original-article link takes you to the publisher’s service and privacy practices.
Information may be processed in countries other than your own, depending on the provider. We may also disclose information when required by law or reasonably necessary to investigate abuse, protect people or defend legal rights.
8. Extension data use and Chrome Web Store Limited Use
DevFeed’s use of information received through the Chrome extension complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. We use this information only to provide or improve the extension’s single purpose: developer-content discovery and reading, including its account, personalization and notification features.
We do not sell user data or use or transfer it for personalized advertising, creditworthiness or lending decisions. We transfer data only as needed to provide or improve the single purpose, comply with applicable law, protect security or investigate abuse, or as part of a merger, acquisition or sale of assets with explicit prior consent from the user. Service providers must handle the data consistently with these limits.
These data-use and transfer limits apply to both the Chrome and Microsoft Edge extensions. Human access to extension user data is limited to cases with the user’s explicit consent for specific data, security investigations, legal obligations, or aggregated and anonymized data used for internal operations. Public publisher content remains public content; processing it to produce summaries does not authorize unrelated use of account or activity data.
9. Retention
Account details, preferences and contributions are retained while needed to provide the service and handle legitimate operational or legal requirements. You can request account deletion by email. There is currently no self-service account-deletion control in DevFeed.
Article-click deduplication records are scheduled for removal after 30 days; aggregate article counts can remain. Sessions, rate-limit records and caches expire. Operational records and backups may remain for their operational or recovery periods; deletion from active systems does not imply immediate erasure from every backup.
Google Analytics and other independent providers apply their own retention settings and policies. Signing out or clearing your browser does not itself delete data already processed by those providers.
10. Your choices and privacy requests
You can browse anonymously, change your profile and preferences, unfollow topics or sources, remove likes, adjust notifications and sign out. Email us to request access to, correction of or deletion of your DevFeed personal information, or to raise a privacy concern.
Depending on the law that applies to you, you may also have rights to object to processing, restrict processing, receive a portable copy, withdraw consent where processing relies on it, or complain to a relevant supervisory authority. We may need to verify your identity before handling a request. Applicable exceptions and legal retention duties may limit what we can erase.
Requests about a GitHub account or another provider’s independent processing must also be directed to that provider. Removing your DevFeed account does not remove those separate accounts.
11. Security and children
We use safeguards such as encrypted connections, access controls, isolated account sessions and rate limits. No internet service can guarantee absolute security. Please do not send passwords, access tokens or unnecessary sensitive information in support requests.
DevFeed is a general developer resource and is not designed for children. If you believe a child has provided personal information inappropriately, contact us so we can investigate and take appropriate action.
12. Policy updates
We will update this page when our practices change and revise the date above. We will provide additional notice or seek consent where required by applicable law.
13. Contact
Contact DevFeed at [email protected]. You can also find us on X at @abhi16_93. Please use email for account, privacy or copyright requests, and do not post personal information publicly.