PRIVACY POLICY - OMNISPEED
Last Updated: October 2026
OmniSpeed ("we", "our", or "the extension") is committed to protecting your privacy. This Privacy Policy details our data collection policies, explains why permissions are required, and addresses whether each requested permission is strictly necessary for the extension to function.
======================================================================
1. CORE PRINCIPLE: ZERO DATA COLLECTION
======================================================================
OmniSpeed operates on a strict zero-telemetry, privacy-first model:
• We DO NOT collect, store, transmit, or sell any personal data.
• We DO NOT track your browsing history, URLs visited, search queries, or media viewing habits.
• We DO NOT inject advertisements or use external tracking libraries, Google Analytics, or third-party SDKs.
• We DO NOT run remote servers to capture user data; 100% of code execution takes place locally in your browser.
======================================================================
2. EXPLANATION OF REQUESTED PERMISSIONS
======================================================================
OmniSpeed requests the following browser permissions in its manifest.json:
• "storage"
Purpose: Stores your playback preferences (custom speed step, default speed, volume boost level, pitch lock toggle, and custom keyboard shortcuts) locally on your device via Chrome's chrome.storage.local API.
Data Stored: Simple JSON configuration settings (e.g., {"speed": 1.5, "step": 0.1}). No personal identifiers.
• "activeTab"
Purpose: Allows the extension popup and background worker to inspect and communicate with media elements in the currently focused tab when you interact with the extension.
• Host Permission ("<all_urls>")
Purpose: Allows OmniSpeed to identify and control HTML5 <video> and <audio> elements regardless of what site you visit (YouTube, Netflix, Coursera, Spotify, Twitch, private school portals, local intranet sites).
======================================================================
3. ARE ALL THESE PERMISSIONS STRICTLY NECESSARY?
======================================================================
Yes. OmniSpeed strictly adheres to the Principle of Least Privilege:
1. Why is "<all_urls>" necessary?
Because videos are hosted across thousands of diverse domains (streaming platforms, social media, online courses, news sites, personal blogs). If we restricted the permission to specific domains (e.g., only youtube.com), OmniSpeed would fail to function on Netflix, Coursera, Vimeo, podcasts, or university lecture portals. The universal nature of "<all_urls>" is essential for a "Universal Speed Controller".
2. Why is "storage" necessary?
Without storage, your speed preferences and customized hotkeys would reset back to defaults every time you closed the browser or refreshed a tab.
3. Why is "scripting" NOT requested?
OmniSpeed does NOT request the broad "scripting" permission because all required content scripts are statically declared in manifest.json with "all_frames: true". This eliminates unnecessary permission warnings during Chrome Web Store review.
4. What permissions did we intentionally AVOID?
To prove our dedication to minimal permissions, OmniSpeed explicitly DOES NOT request:
- "scripting" (no arbitrary script injection)
- "webRequest" (no traffic sniffing)
- "cookies" (no access to login sessions or cookies)
- "history" (no access to visited websites)
- "bookmarks" (no access to user bookmarks)
- "identity" (no Google login required)
- "clipboardRead" / "clipboardWrite" (no clipboard snooping)
Every requested permission serves an indispensable technical requirement for controlling HTML5 media, with zero excess privileges.
======================================================================
4. THIRD-PARTY SERVICES & EXTERNAL SERVERS
======================================================================
OmniSpeed does not communicate with external servers, cloud databases, or third-party APIs. All features—including the audio amplifier (Web Audio API), speed controls (HTMLMediaElement API), and video filters (CSS filters)—run entirely within your local browser sandbox.
======================================================================
5. USER DATA RIGHTS & CONTROLS
======================================================================
You maintain complete control over your preferences:
• You can reset all saved settings at any time via the OmniSpeed Options page by clicking "Restore Defaults".
• Uninstalling OmniSpeed from Chrome automatically purges all locally stored preferences from your device.
======================================================================
6. CONTACT & INQUIRIES
======================================================================
If you have questions or concerns regarding this Privacy Policy or OmniSpeed's operation, please reach out through the official support channel on the Chrome Web Store extension listing.