Effective date: [2026-07-23]
MediaDeck is a Chrome extension that lets users adjust the playback speed, audio processing, and visual presentation of HTML5 video and audio on regular web pages.
This policy explains the information MediaDeck accesses, processes, stores, and shares. In this policy, "processes" includes information handled only in the user's browser. The MediaDeck publisher does not receive that locally processed information.
Information MediaDeck processes
Current-page and media information
MediaDeck runs content scripts on web pages covered by its site access. To find and control playable HTML5 media, it processes a limited set of current-page and media information:
the current page URL in memory, including its protocol, so MediaDeck can recognize supported pages and changes in single-page applications;
HTML <video> and <audio> elements in the regular page DOM and accessible frames;
a temporary media identifier, media type, playback duration and paused state;
whether a stream appears to be live;
video dimensions;
whether browser-protected media keys appear to be in use;
the media source hostname and origin/CORS conditions needed to determine whether browser audio processing is available; and
the playback and visual state needed to apply the user's selected controls.
When a user enables an audio adjustment, the media element's audio is routed through the browser's Web Audio API so the requested effect can be applied. When a user enables a frame adjustment, MediaDeck applies browser CSS or SVG effects to that video element. MediaDeck does not record or persist audio samples, video frames, page text, form entries, messages, cookies, passwords, or authentication tokens.
This current-page and media information is used only to provide MediaDeck's media controls and related compatibility messages. It is not sent to the MediaDeck publisher or to a developer-controlled server.
Preferences stored with Chrome Sync
MediaDeck stores the user's control preferences under the mediadeck_settings key in chrome.storage.sync. These preferences can include playback speed, speed-ramp settings, audio-effect levels, video-effect levels, zoom, crop, rotation, flip options, and light/dark theme.
Chrome stores these preferences locally. If the user has Chrome Sync enabled, Chrome may also synchronize them through the user's Google account to other signed-in Chrome browsers. This synchronization is provided and controlled by Chrome and Google, not by the MediaDeck publisher. MediaDeck does not store page URLs, media source hostnames, or media metadata in Chrome Sync.
Network communication
MediaDeck contains no analytics, advertising, telemetry, tracking pixels, third-party SDKs, account system, or developer-operated network service. The extension does not initiate network requests to send page, media, or usage data to the MediaDeck publisher.
The Chrome Sync behavior described above is the only extension-initiated persistent data synchronization. Web pages and their media players may make their own network requests independently of MediaDeck.
Sharing, selling, and advertising
The MediaDeck publisher does not receive, sell, rent, share, or use page information, media information, or user preferences for advertising, profiling, credit decisions, or any purpose unrelated to MediaDeck's user-facing media controls.
When Chrome Sync is enabled, Google processes the saved preferences as the provider of Chrome and Chrome Sync under Google's own terms and privacy practices. MediaDeck does not otherwise disclose user information to third parties.
A web page's own scripts can observe changes made to that page's media element, such as its playback rate or inline visual styles, just as they can observe changes made with the page's player controls. MediaDeck does not expose saved preferences or information from other pages to that site.
MediaDeck's use of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.
Retention
Current-page and media information is held only in browser memory. Popup data is discarded when the popup closes. Content-script state is discarded when the relevant page or frame is unloaded, and entries for removed media elements are pruned while a page remains open.
Preferences in chrome.storage.sync remain until they are changed or reset by the user, the user clears the extension's stored data, or Chrome/Google removes them under the user's browser and sync settings. MediaDeck does not apply a separate server-side retention period because the publisher does not operate a server that receives this data.
User choices and deletion
Users can:
change individual preferences or use Reset All Settings in MediaDeck;
manage or disable Chrome Sync in Chrome's settings;
restrict MediaDeck's site access through Chrome's extension settings;
leave access to file:// pages disabled, as it is by default; or
disable or uninstall MediaDeck.
Resetting MediaDeck replaces saved custom preferences with the default values. Chrome controls deletion of any copies maintained by Chrome Sync.
Permissions
MediaDeck may request the following Chrome permissions:
Storage: saves the preferences described above with chrome.storage.sync.
Site access (<all_urls>): lets MediaDeck locate and control HTML5 media on regular web pages and in covered frames. It does not give MediaDeck access to restricted browser pages such as chrome:// pages or the Chrome Web Store.
Scripting: allows MediaDeck to load its packaged content scripts into the current page when an already-open page has not yet received them. MediaDeck does not download or execute remote code.
Security
MediaDeck minimizes persistent storage to non-sensitive control preferences and keeps current-page and media information in browser memory. Because the extension does not send page, media, or preference information to the publisher, there is no publisher-operated database containing that data.
No method of local storage or software operation can be guaranteed completely secure. Users should keep Chrome and MediaDeck up to date.
Changes to this policy
If MediaDeck's data practices change, this policy will be updated before or at the same time as the relevant extension release. The effective date above will also be updated. Any new practice requiring an in-product disclosure or consent will be presented in the extension as required.
Contact
For privacy questions or requests, contact: