A2VM Privacy Policy
Static content-script match patterns cover HTTP, HTTPS, and file URL pages. Media discovery, the Overlay, and command execution remain gated by the site-enabled setting; continuous activation uses optional host permission granted by the user.
Last updated: September 30, 2026
Summary: Media state, commands, settings, and explicitly requested screenshots are processed locally. A2VM does not send them to the developer or third parties and uses no analytics, advertising, or remote media services.
Data processed temporarily
- Accessible HTMLMediaElement type, visibility, playback state, duration, current time, volume, mute state, rate, gain, and capabilities;
- Minimal media geometry for toolbar positioning and temporary wide/viewport presentation;
- A current-frame image, preview, and download data only after an explicit screenshot request; screenshot history and cloud sync are not enabled;
- Interface language, theme, transparency, toolbar size, and site activation settings selected in Popup or Options.
A2VM does not read page text, forms, cookies, browsing history, or unrelated business fields. It does not download media streams or bypass DRM.
Purpose, sharing, and retention
The data above is used only to discover accessible media, execute commands, display results, position the toolbar, and create a requested screenshot. A2VM does not send, sell, rent, or share page content, media URLs, media state, screenshots, settings, or usage information.
chrome.storage.local stores only user-selected interface and site settings. Media state and gain remain in the current page session. Screenshot memory and history storage are deferred and are not written to storage quotas.
Permissions
- storage: local interface and site settings.
- activeTab: temporary access after an explicit Popup or extension action to send commands.
- scripting: on-demand content-script activation and media discovery.
- Optional host permissions: HTTP/HTTPS site activation and
file:///*when local-file access is allowed; Chrome still requires its separate setting.
A2VM does not request browsing-history, cookie, clipboard-read, download, or remotely hosted executable-code permissions.
Third-party services, user control, and changes
Control, gain processing, and screenshot previews run locally. A2VM uses no remote recognition, analytics, advertising, telemetry, tracking, or remote executable code. Users can control the current active tab from the page toolbar or Popup, disable sites, change settings, or uninstall the extension. If practices change, this policy and its update date will be revised. Contact the publisher through the A2VM Chrome Web Store listing.