Last updated: August 17, 2026
Video Speed Controller Pro does not collect analytics, create user profiles, sell data, or send your activity to developer-operated servers. Its runtime behavior is local to the browser, apart from Chrome’s optional built-in settings sync described below.
The extension reads the current page URL and HTML media-element state in memory so it can apply site/URL rules, choose the active player, change playback speed, and calculate remaining time. It does not store a browsing history or a list of watched videos.
For Chrome Web Store disclosure purposes, this local processing can include web history (the current URL and hostnames attached to user-created site preferences), user activity (media playback state and the aggregate time-saved calculation), and website content (HTML media metadata, user-requested screenshot pixels, and the audio amplitude described below). These data are used only to provide the extension’s user-facing media controls. They are not sent to the developer or to third parties.
If silence skipping is enabled, the browser’s Web Audio API calculates short-lived amplitude samples in memory. Audio is not recorded, retained, uploaded, or exposed outside the page’s local extension context. Unsupported, protected, or clearly cross-origin media is not analysed.
The following user-created settings may be stored with chrome.storage.sync:
Chrome may sync those settings through the Google account connected to the browser. That service is operated by the browser provider; the extension developer cannot access the synced contents. Disable Chrome Sync to keep these settings only in the local browser profile.
The aggregate time-saved counter is stored in chrome.storage.local and is not placed in the
extension’s Sync data.
storage saves and syncs the preferences listed above.activeTab lets the popup identify and control the current tab.The extension does not request browsing-history, cookies, identity, location, microphone, camera, downloads, or native-application permissions.
The shipped extension contains no analytics SDK, advertising SDK, telemetry endpoint, or developer backend. It does not share or sell personal data. Loading a video and Chrome Sync may involve the page’s provider and Google respectively, but the extension does not add tracking requests to those services.
The development-only locale generator is not part of the packaged extension and is not executed in users’ browsers.
The extension’s use of user data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. User data is used only to provide or improve the extension’s single purpose and is not used for advertising, creditworthiness, lending, or unrelated purposes.
Use Reset settings in the options page to clear extension preferences and the local time-saved counter, or uninstall the extension to remove its browser-managed storage. Synced settings may also be managed through Chrome’s Sync controls.
Material changes will update the date at the top of this policy. Questions can be filed through GitHub Issues.