Browser extensions have to ask for their permissions up front. Here is every one Media Grabber asks for, exactly what it's used for, and what it is never used for. Nothing here is collected or sent to us — Media Grabber has no servers, no analytics and no account.
12 permissions + site accessNothing leaves your deviceNo remote codeNo analytics
01 Finding videos
host access: all websitesChrome shows: "Read and change all your data on all websites"
Why: videos can be on any website, so the extension needs to notice video streams on whichever page you're on, and fetch the video you choose from that site.
Never: it doesn't read your passwords, forms or messages, and it doesn't change pages you visit. It only looks for video and audio.
webRequestCovered by the warning above
Why: watches the addresses of files the page loads, so it can spot video playlists and media files (HLS .m3u8, DASH .mpd, MP4…) and list them in the popup. That's how the toolbar badge knows how many videos are on the page.
Never: it only observes; it doesn't block, redirect or change requests. Addresses are kept in memory for the current tab and forgotten when you leave the page. YouTube traffic is ignored completely.
content script on every pageCovered by the warning above
Why: a small script looks for <video> and <audio> elements on the page (including embedded players), and reads the page title and the video's poster image so your file gets a proper name and preview.
Never: it doesn't read the rest of the page, and it doesn't send anything anywhere.
tabsChrome shows: "Read your browsing history"
Why: to know which tab a video belongs to, use the tab's title as the file name, and open the source page from your download history. When a video has no poster image, the popup takes one picture of the visible tab and crops it to the video for the preview — only while you have the popup open.
Never: it doesn't build a list of sites you visit, and the preview image never leaves your device.
scriptingCovered by the site-access warning
Why: three things: finding the video's preview image, fetching video data through the page for sites that refuse requests from extensions, and Capture what's playing, which records what the site's player loads. Capture only starts when you click it, only on that one site, and is removed when you stop.
Never: it doesn't inject ads, trackers or anything that changes how sites look or behave.
02 Downloading
downloadsChrome shows: "Manage your downloads"
Why: saves the finished video, audio and subtitle files to your Downloads folder (or asks where to save if you turned that on), and powers pause, resume, cancel and "Show in folder".
Never: it doesn't look at, change or delete your other downloads.
downloads.openNo separate warning
Why: the Open button on a finished download.
Never: it never opens a file unless you click Open.
declarativeNetRequestWithHostAccessNo separate warning
Why: many video servers only answer requests that say which page they came from. This lets the extension add the page's Referer / Origin to its own requests for the video, just like the site's player does.
Never: the rules apply only to the extension's own downloads, last only for the browser session, and never touch your normal browsing.
offscreenNo warning · Chrome & Edge only
Why: runs the download engine — merging picture and sound, converting formats — in a hidden extension page, so downloads keep going when you close the popup.
Never: it has no window, can't see your tabs and does nothing but process the files you asked for.
unlimitedStorageNo warning
Why: pieces of a video are kept on disk while they download, so long videos don't run out of memory and interrupted downloads can resume. They're deleted as soon as the file is saved (or from Settings → Delete temporary files).
Never: it doesn't keep copies of your videos after saving them.
03 Settings & convenience
storageNo warning
Why: remembers your settings, the download queue, and your download history (which you can turn off or clear). If you use browser sync, your browser syncs your settings between your own devices.
Never: nothing is stored on our side — there is no "our side".
Why: tells you when a download finishes or fails. You can turn this off in Settings.
Never: no promotions, no "rate us" pop-ups.
contextMenusNo warning
Why: adds Download this video with Media Grabber when you right-click a video or a link to a video file.
sidePanelNo warning · Chrome & Edge only
Why: lets you use Media Grabber in the browser's side panel instead of the popup, if you prefer. On Firefox the built-in sidebar is used, which needs no permission.
04 Worth knowing
Requests use your cookies for that site. When you download, the video is fetched with the same sign-in the site's own player uses — that's what makes downloads work on sites where you're logged in. Those requests go only to the website that hosts the video.
No other network traffic. The extension doesn't contact any server of ours or anyone else's: no analytics, no update checks beyond the store's own, no remote code. All code, including the open-source parts (mux.js, lamejs), is inside the package the store reviewed.
Copy diagnostics is manual. It copies technical details (versions, settings, recent errors with site domains) to your clipboard. Nothing is sent unless you paste it into a message yourself.
Not supported on purpose: YouTube and DRM-protected services (Netflix, Disney+, Prime Video…). The extension never circumvents copy protection.
05 What we don't ask for
Media Grabber does not request access to your cookies store, history, bookmarks, passwords, identity, location, camera, microphone, clipboard reading, other extensions, proxy settings or native apps on your computer.
06 Stay in control
See the list yourself: open chrome://extensions (or edge://extensions) → Media Grabber → Details. On Firefox: Add-ons → Media Grabber → Permissions.
Limit site access: on the same Details page, set Site access to On click or On specific sites. Media Grabber then only works where you allow it.
New permissions are rare and announced. If a future version ever needs one, your browser will ask you first, and the change will be explained in the changelog and on this page.