← Back to WatchFilter
⚡ WatchFilter

Privacy Policy

Effective date: July 30, 2026

WatchFilter is a video intelligence tool that analyzes YouTube content on your behalf. WatchFilter uses YouTube API Services. By using WatchFilter, you agree to be bound by the YouTube Terms of Service and Google's Privacy Policy. We are committed to being transparent about what data we handle and how.

1. Information We Collect

Data you provide

  • YouTube URLs — submitted by you for analysis. We process these to fetch transcripts and metadata.
  • Google account access — if you connect your Google account, we request read-only access to your YouTube subscriptions and account identifiers (email, name) via Google Sign-In, using YouTube API Services. This is used solely to display and analyze your subscription feed inside WatchFilter.
  • Email address — collected when you sign in with Google, or if you use the "Email Briefing" feature. Sign-in email is stored server-side to associate your OAuth tokens with your account; briefing email is stored locally in your browser and used solely to deliver that briefing.
  • Voice preference — your selected TTS voice (Onyx / Nova) stored in local session state only.

Data we generate on your behalf

  • Analysis records — structured intelligence extracted from the video transcript (clickbait score, data points, playbook). Stored in our database tied to the video ID, not to any personal identifier.
  • Audio briefings — MP3 files generated via OpenAI TTS, stored on Vercel Blob Storage with a private URL. No personal data is embedded in these files.

Data we do not collect

  • We do not track browsing behavior, set advertising cookies, or fingerprint devices.
  • We do not sell, rent, or share any data with third-party advertisers.

2. How We Use, Process & Share Your Information

We use the data described above only to operate and improve WatchFilter. Specifically:

  • Your YouTube subscription data (obtained via YouTube API Services after you sign in with Google) is used only to build your in-app subscription feed and to generate the AI analysis you see. It is cached server-side to avoid re-fetching on every visit, and is never sold, rented, shared with advertisers, or used for any purpose beyond powering your WatchFilter feed.
  • Your Google OAuth refresh token is stored server-side (encrypted at rest by our database provider) so we can refresh your access without asking you to sign in repeatedly. It is used only to call YouTube API Services on your behalf and is never shared with any third party.
  • Video transcripts and titles you submit (or that are pulled from your subscription feed) are sent to OpenAI for AI analysis — see Section 3 below.
  • We do not share your personal information (email, Google account identifiers, subscription data) with any internal team, affiliate, or external party other than the service providers listed in Section 3, who process it solely to provide the Service to you and are contractually/by-policy bound not to use it for their own purposes.

3. Third-Party Services

To provide the service, data described above is sent to the following third parties:

  • OpenAI API — transcript text is sent to OpenAI's GPT-4o-mini model for analysis and to OpenAI TTS for audio generation. OpenAI's API data usage policy applies.
  • YouTube API Services / Google — video transcripts, metadata, and (if you sign in) your subscription feed are fetched using YouTube API Services and Google Sign-In. Google's Privacy Policy applies to that data.
  • Vercel — our hosting platform and Blob Storage provider. Vercel's Privacy Policy applies to infrastructure-level data.

4. Data Retention, Deletion & Revoking Access

  • Analysis records are stored until you clear your local database or we purge inactive records (no fixed schedule currently).
  • Audio files on Vercel Blob are retained indefinitely unless you delete an analysis or we remove inactive blobs.
  • We do not retain briefing email addresses beyond the delivery of a single briefing.
  • Deleting your account data: to request deletion of your stored Google account data (OAuth tokens, cached subscription data, sign-in email), use the "Disconnect Google Account" option in WatchFilter's Settings, or email hello@watchfilter.app and we will delete it within 30 days.
  • Revoking WatchFilter's access to your Google account: disconnecting in-app immediately deletes our stored refresh token and revokes it with Google. You can also revoke WatchFilter's access at any time directly from Google, independent of WatchFilter, at myaccount.google.com/connections.

5. Cookies & Local Storage

WatchFilter does not use tracking cookies. We use browser localStorage only to remember your email address across sessions for the email briefing feature, and a session cookie to keep you signed in with Google. No analytics or advertising cookies are set.

6. Security

All data is transmitted over HTTPS. Audio files are served from private Vercel Blob URLs. OAuth tokens are stored server-side only and are never exposed to client-side code.

7. Children's Privacy

WatchFilter is not directed at children under 13. We do not knowingly collect data from minors.

8. Changes to This Policy

We may update this Privacy Policy as the product evolves. Material changes will be reflected in an updated effective date at the top of this page.

9. Contact

Questions about this policy, or a request to delete your data? Email us at hello@watchfilter.app.