Privacy Policy
Last Updated: October 7, 2026
1. Our Core Privacy Principle
Sponskip is built on a strict zero-knowledge architecture. We believe that browser extensions should perform their utility locally without eavesdropping on what users watch, read, or listen to. We do not track, collect, transmit, or monetize any of your personal data or browsing activity.
2. What Data Sponskip Accesses
Sponskip requests the minimum browser permissions necessary to operate:
- Host Permission (
*://*.youtube.com/*): Required solely to inject the lightweight playback controller script that detects video timestamps and advances playback past sponsor reads. - Host Permission (
https://sponsor.ajay.app/*): Used to fetch public, crowdsourced sponsor segment intervals for the currently active YouTube video ID. No user identifiers or Google account tokens are sent with this request. - Storage Permission (
chrome.storage.local): Used entirely on your local machine to remember your preferences (such as auto-skip toggles, enabled categories, and cached segment timestamps).
3. Zero Data Collection & Zero Telemetry
Sponskip does not contain any analytics SDKs, error tracking reporting libraries (such as Sentry), advertising beacons, or telemetry. No information regarding your identity, IP address, browsing history, subscriptions, search queries, or watch history is ever stored or transmitted to Sponskip servers.
4. Third-Party Services
When viewing a YouTube video, the extension queries the public SponsorBlock API for segment boundaries. Queries transmit only the video ID (or hash prefix). For information regarding SponsorBlock's data practices, please review the SponsorBlock documentation. Sponskip has no commercial or corporate affiliation with YouTube, Google LLC, or SponsorBlock.
5. Open Source & Auditability
The full source code of Sponskip is public and available for inspection at github.com/sponskip/sponskip. Anyone may review the codebase to verify our privacy guarantees.
6. Contact
If you have questions regarding this privacy policy or the extension's behavior, you may open an issue on GitHub or contact Blake Burford at burfordblake056@gmail.com.