TL;DR — The short version
- FeedWatch does not collect, store, or sell your personal data on any server
- All tracking happens locally in your browser
- Your Telegram Chat ID and email are stored only in your browser's local storage
- Your X (Twitter) access token is stored only in your browser — we never see it
- We never read or store the tweets your feed contains
📋 1. What FeedWatch Is
FeedWatch is a Chrome browser extension that monitors your X (Twitter) feed locally in your browser for keywords, accounts, or hashtags you specify. It sends recap digests to Telegram or email channels you configure.
FeedWatch is operated by its developer (Soul, reachable at [email protected]).
🔍 2. What Data We Process
FeedWatch processes the following data entirely on your device:
- Your tracker terms — keywords, @handles, and #hashtags you add
- Post content from your X feed — read locally in real time to detect matches; never sent to our servers
- Your name — used only to personalize your recap digest
- Your email address — used only to send you digests via EmailJS; stored locally in your browser
- Your Telegram Chat ID — used only to send you digests via Telegram Bot API; stored locally in your browser
- Your X (Twitter) access token — obtained via Twitter OAuth 2.0 PKCE; stored locally in your browser and used only to fetch your profile display name
None of this data is transmitted to FeedWatch servers. We do not have servers that store user data.
🚫 3. What We Do NOT Do
- We do not collect, log, or store your tweets, posts, or feed data on any server
- We do not store your email, Telegram Chat ID, or name on any server
- We do not sell, share, or monetize your personal information
- We do not track your browsing history or behavior on other sites
- We do not use advertising cookies or third-party trackers on this website
- We do not read your X account's private messages or data beyond your public profile info
🔗 4. Third-Party Services
FeedWatch communicates with the following third-party APIs on your behalf and at your request:
- X (Twitter) API — to authenticate your account via OAuth 2.0 PKCE and retrieve your public profile (username, display name, avatar). Governed by X's Privacy Policy.
- Telegram Bot API — to deliver your recap digest to your Telegram chat. Governed by Telegram's Privacy Policy. Only your Chat ID and your recap content are sent.
- EmailJS — to deliver your recap digest to your email address. Governed by EmailJS's Privacy Policy. Only your email address and recap content are sent.
- Stripe — to process Pro subscription payments. Governed by Stripe's Privacy Policy. FeedWatch does not store your payment card details.
- Supabase — to store subscription status (email + subscription tier only). Governed by Supabase's Privacy Policy.
🍪 5. Cookies & Local Storage
This website (getfeedwatch.com) does not use tracking cookies or advertising cookies.
The FeedWatch Chrome extension uses Chrome's local storage (chrome.storage.local) to store your settings, trackers, and recap history locally on your device. This data never leaves your browser unless you explicitly send a recap to Telegram or email.
🔒 6. X (Twitter) OAuth & Permissions
When you use "Login with X", FeedWatch requests the following OAuth 2.0 scopes:
- tweet.read — to read your public timeline (processed locally only)
- users.read — to fetch your display name and avatar for the extension UI
FeedWatch does not request write permissions. It cannot post, like, retweet, follow, or take any action on your X account.
Your access token is stored only in your browser's local storage. You can revoke FeedWatch's access at any time from your X account's Connected Apps settings.
👤 7. Your Rights
Because FeedWatch does not store your personal data on any server, most data subject rights are exercised directly on your own device:
- Access / Portability — All your data is already in your browser's local storage. You can inspect it via Chrome DevTools.
- Deletion — Uninstalling the extension removes all locally stored data. To remove your email from Supabase subscription records, email [email protected].
- Correction — Update your settings directly in the FeedWatch options page at any time.
👶 8. Children's Privacy
FeedWatch is not directed at children under the age of 13. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided personal data, please contact us at [email protected] and we will take appropriate steps to delete it.
🔄 9. Changes to This Policy
If we make material changes to this privacy policy, we will update the "Last updated" date at the top of this page. Continued use of the extension after changes constitutes acceptance of the updated policy.
✉️ 10. Contact
Questions, concerns, or deletion requests? Contact us at:
Email: [email protected]
Website: getfeedwatch.com