YOUR PRIVACY, EXPLAINED

A clearer feed.
Your data stays yours.

NoAI helps you filter AI-disclosed content on YouTube and YouTube Music. Here’s exactly how the extension handles your information.

Privacy PolicyLast updated

Local by design

Preferences and checked-video cache are stored on your device.

No tracking

No analytics, advertising trackers, or behavioral profiling.

No NoAI account

No sign-up or developer-operated backend to use the extension.

01 — OVERVIEW

The short version

NoAI — YouTube AI Filter is a browser extension maintained by Wojciech Osak. It reads limited YouTube page content to determine whether videos should be hidden, blurred, or labeled based on YouTube-provided AI or synthetic-content disclosures.

The extension processes this information locally. It does not send your preferences, local cache, or filtering results to the developer, an analytics service, or an external AI service. NoAI does not sell personal data or use it for advertising.

A filter that runs in your browser.

NoAI uses YouTube’s disclosure information. It does not upload videos to an AI model for analysis.

02 — DATA & PURPOSE

What NoAI reads & stores

NoAI accesses information only to provide its filtering features on YouTube and YouTube Music.

YouTube page content
Video IDs, relevant video metadata, AI/synthetic-content disclosures, and page elements needed to identify and change the display of matching videos. These are read locally to apply your selected filtering behavior.
Your preferences
Your extension settings are saved in Chrome’s local extension storage so NoAI can remember how you want content to be filtered.
Checked-video cache
Video IDs and their disclosure-check results are stored locally to avoid repeatedly checking the same videos. This cache is used for filtering, not to build a profile of your viewing habits.

NoAI does not collect your name, email address, passwords, payment information, private messages, or precise location through the extension. It does not track clicks, keystrokes, or browsing activity for analytics.

03 — CONNECTIONS & SHARING

What leaves your device?

NoAI may request YouTube pages or metadata to check disclosure information for a video. These requests go directly to YouTube and necessarily identify the requested video or page. YouTube receives normal connection information, such as your IP address, and may receive cookies according to your browser settings.

NoAI does not send this information to a developer-operated server or other services for tracking, advertising, or AI analysis. It has no analytics SDKs, advertising trackers, or remote backend.

Your use of YouTube and YouTube Music, including these requests, is covered by Google’s Privacy Policy.

04 — YOUR CONTROL

Stored locally. Controlled by you.

Preferences and cached results remain in the browser’s local extension storage until they are updated or cleared, or the extension is removed. They are not synced by NoAI to a developer account or cloud database.

  • Change your preferences using the extension’s settings.
  • Stop filtering by disabling NoAI in your browser’s extension manager.
  • Remove local extension data by uninstalling NoAI. Chrome removes its local extension storage when the extension is removed.

Disabling the extension does not erase its saved data. Clearing normal browsing history or the browser cache does not necessarily clear extension storage.

05 — THIS WEBSITE

A simple page, too.

This privacy-policy website contains no analytics scripts, advertising trackers, forms, or embedded third-party media. It does not set cookies or use browser storage, and its fonts and assets do not require external font services.

The page is hosted by GitHub Pages. GitHub logs visitors’ IP addresses for security purposes, as explained in the GitHub Pages documentation and GitHub Privacy Statement.

06 — UPDATES & CONTACT

Questions are welcome.

This policy may be updated if NoAI’s functionality or data practices change. The latest version will be published here with a revised “Last updated” date.

For questions about this policy, contact Wojciech Osak through the project’s GitHub issues. If you choose to contact us, we receive the information you include and use it to respond to your request. GitHub handles that interaction under its own privacy policy.

Contact via GitHub

GitHub issues are public. Please do not include sensitive personal information.