PRIVACY POLICY FOR H264 STREAMLINE
Last updated: October 2026
1. INTRODUCTION & CORE PRIVACY COMMITMENT
H264 Streamline ("the Extension") is dedicated to protecting user privacy. This Extension is built with a strict "privacy-by-design" philosophy:
• We do NOT collect, store, transmit, or sell any personal data.
• We do NOT track browsing activity, watch history, search queries, or video selections.
• We do NOT use analytics, cookies, telemetry, or remote servers.
All code runs 100% locally on your machine inside your browser.
2. WHAT DATA DO WE COLLECT?
None. H264 Streamline does not collect, process, or transmit any user data, device identifiers, IP addresses, or personal information whatsoever.
3. PERMISSIONS BREAKDOWN & WHY THEY ARE NEEDED
To function properly, Chrome requires extensions to declare specific permissions in their manifest. H264 Streamline requests only two minimal permissions:
a) "storage"
• Purpose: Saves your selected extension toggles (for instance: whether VP9 blocking is active, whether AV1 blocking is active, or whether Battery Saver mode is enabled).
• Scope: Settings are stored locally on your machine via Chrome's native storage API. No data leaves your computer.
b) Host Permissions ("*://*.youtube.com/*", "*://*.youtube-nocookie.com/*", "*://*.youtu.be/*")
• Purpose: Enables the extension to inject a lightweight script into YouTube video player pages at load time.
• Scope: This script intercepts browser media capability queries (canPlayType and MediaSource.isTypeSupported) so YouTube's player selects hardware-accelerated H.264 video streams instead of VP9 or AV1.
• Restriction: This permission is strictly restricted to YouTube domains and embedded YouTube players. The extension cannot access, read, or run on any other websites.
4. ARE ALL THESE PERMISSIONS REALLY NECESSARY?
Yes, and they represent the absolute minimum technical baseline required for the extension to operate:
• Without "storage": The extension would lose your preferred settings (like 60 FPS blocking or battery saver mode) every time you close your browser or reload a tab.
• Without YouTube host permissions: The browser would block the extension from overriding video player codec queries on YouTube, rendering the extension incapable of forcing H.264 streams.
CRITICAL SECURITY NOTE ON OMITTED PERMISSIONS:
Many video extensions request broad, unnecessary permissions such as:
• "<all_urls>" or broad web access (which allows reading any website you visit)
• "tabs" (which allows reading all open browser tabs and URLs)
• "webRequest" (which allows inspecting or intercepting all network traffic)
• "cookies" (which allows accessing session authentication)
• "scripting" (broad arbitrary script injection across domains)
H264 Streamline explicitly DOES NOT request ANY of these permissions. By using declarative Manifest V3 content scripts targeting only YouTube origins, we ensure maximum security and zero exposure of user data.
5. THIRD-PARTY SHARING & NETWORK ACTIVITY
The Extension makes zero outgoing or incoming network requests. It contains no third-party tracking scripts, no advertisements, no affiliate links, and no external CDNs. All assets and scripts are packaged locally within the extension bundle.
6. USER CONTROL & DATA DELETION
You have full control over your settings through the extension popup. If you uninstall the extension from Chrome, all locally stored preferences are immediately and permanently removed by Chrome.
7. COMPLIANCE
H264 Streamline complies fully with:
• Google Chrome Web Store Developer Program Policies & User Data FAQ
• General Data Protection Regulation (GDPR)
• California Consumer Privacy Act (CCPA)
8. CONTACT & INQUIRIES
For questions, support, or privacy inquiries regarding H264 Streamline, please contact the developer via the official Chrome Web Store support tab.