Last updated: September 17, 2026

This policy describes how the notsponsored browser extension processes, stores, and transmits data.


notsponsored helps skip YouTube sponsor segments. It can use SponsorBlock data, inspect YouTube captions
locally, and, if enabled and configured by the user, ask an OpenAI-compatible language-model endpoint to verify or
detect
sponsor segments.


The extension may read the current YouTube video ID, channel handle, and caption/transcript data exposed by the YouTube
page. The local sponsor detection runs in the browser, and transcript text used only for local detection is not sent to
a server
by that feature.

Browser extension storage may contain:

• extension settings, including routing, skip, and trim preferences
• blocked channel handles and skip statistics
• the user's chosen LLM endpoint, model, and API key
• a cache of LLM detection results

The LLM cache stores detection results for LLM scanned videos. The cache is limited to 100
entries and entries older than 30 days are discarded upon the next use.


When SponsorBlock routing is enabled, the extension sends the current YouTube video ID to
https://sponsor.ajay.app/api/skipSegments to retrieve sponsor segments from SponsorBlock.
It only requests sponsor segments, and does not transmit and other information.

LLM processing is optional and is off by default. After the user configures an endpoint and model, enables the feature,
and
grants the required permissions, the extension may send transcript text, timing information, and locally detected
candidate ranges
to the user endpoint chosen by the user. In Firefox, this requires consent to transmit website content in
addition to permission to contact the endpoint.

Clicking the Load models button can contact the configured endpoint even while LLM processing is disabled. If an API
key is
configured, both model-list requests and transcript-processing requests send it in the request's Authorization: Bearer
header. Firefox requires consent to transmit authentication information before the key is sent. The key is stored in
browser extension storage and is not encrypted.

Remote endpoints for LLM processing have to use HTTPS. HTTP is supported only for local endpoints on localhost,
127.0.0.1, or [::1].
Requests go directly from the browser to the endpoint selected by the user. The provider you use's privacy policy and
retention
practices apply. The provider may charge for API usage.

The extension does not operate an account service or analytics service, and it does not include extension analytics,
advertising telemetry, or tracking beacons.


The user can disable the extension, choose SponsorBlock-only or local detection modes, disable LLM processing, change or
remove the LLM endpoint, model, or API key, and clear or read the extension's stored data through the browser. Firefox
users can
also revoke optional data permissions in the extension's Permissions and data settings. Revoking endpoint access or
optional LLM data permissions cancels LLM requests and disables LLM processing until the user enables it and grants
permission again. Local settings, statistics, blocked channels, and cached results remain in browser extension storage
until changed or cleared by the user or removed with the extension. No data is retained or transmitted on a server
operated by
notsponsored, not that there even exists such a server.


For privacy questions or support, contact support@zyluxd3v.com.

Source code: github.com/ZyluxXD/notsponsered