Savvid extension for Chrome, version 3.0.0 and later

Savvid Privacy Policy

Last updated:

This policy describes the Savvid extension for Chrome, version 3.0.0 and later. Before version 3.0.0 it was called VideoGrab. It also describes Savvid for Firefox, version 3.0.6 and later; the section Savvid for Firefox says where that version differs. Savvid runs entirely in your browser. It has no server, no account and no analytics. It never sends information about you or your browsing to its developers, and it does not sell or share it. Its network requests go only to the servers that the pages you visit name, the addresses those servers redirect to, and links you choose, as described below.

Summary

How Savvid uses this information

Savvid uses the information described in this policy only to find and save the video you choose. The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

What Savvid reads in your browser

What Why Leaves your computer?
Addresses and response headers of the http and https network requests in your tabsto recognise HLS and DASH playlists and media filesNo
The request headers Accept, Authorization (a Brightcove player's access token), BCOV-Policy (a Brightcove policy key) and X-Requested-With of the player data requests of item 5, held only in memory (forgotten when Savvid's background stops) and never stored; Chrome passes Savvid request headers only for requests to the hosts of these five servicesto repeat that request with the headers the player sentOnly to the server the player sent them to, in Savvid's repeated request of item 5 (and, should that server redirect the request, to the address it redirects to)
The page title, Open Graph and Twitter meta tags, schema.org VideoObject data, the first heading of the page, and the poster of each video on the page (at most 10)to name files and to show each video with its own thumbnail; the length the page gives for its video (og:video:duration or the schema.org duration) tells Savvid whether a video it found is the page's own, so that another video is not named or pictured after the pageNo
The address, length, picture size and poster of each video element of the page, whether it is paused, muted and has played at all, whether it has loaded media, how much of the window it covers, and the addresses of the other files it lists as sourcesto show the length, picture size and poster of a video, to offer the other files a video element lists (they are listed without being requested), to leave out a video the page only loads ahead (the next video, a muted preview) while you watch another one, and to tell which video plays, or, before any plays, which is the page's main video (the largest one in the window), so that only that video takes the page's title and picture and is listed first as the video of the pageNo
Whether the page uses the Encrypted Media Extensions (DRM) APIto mark protected videosNo
The video data the page embeds in itself, with the page's address at that moment: its data blocks (script elements of type application/json or application/ld+json, such as schema.org VideoObject data and Next.js or Nuxt page data) and its Open Graph video tags (og:video, og:video:secure_url, og:video:url, og:video:type, og:video:duration, twitter:player:stream). Savvid keeps only the video file, playlist and DASH manifest addresses of the videos that the page's address names by an identifier, that the schema.org data or the Open Graph tags declare, or that a video element of the page plays, has played or, as the page's only video element, shows (once the top page has moved to another address without loading a new page, only a video element that is playing counts), or, when none is named, of the one video whose list of qualities the page embeds, with the picture size, length, title and thumbnail address given next to them; every other address in that data is discarded at once and never stored. The data is read from the page already open once it has loaded (or, if it never finishes loading, 10 seconds after its document has been parsed), 3 seconds later, and again each time the top page moves to another address without loading a new page (not when only the part after # or a tracking parameter changes); Savvid does not request the page again and runs none of the page's scriptsto offer the video the page shows in every quality the page lists, and each video of a post that holds several (a carousel, a gallery or a thread) with its own title and thumbnailThe playlist and DASH manifest addresses among them, and the thumbnail address. For each video Savvid requests one of its playlists (its HLS playlist when the page names one, else its DASH manifest) without cookies to list its qualities, as it requests any playlist it detects (item 1 of Network requests Savvid makes; a server that refuses that request gets it once more with the page's origin, see Referer and Origin), and the later reads of the same loaded page do not request it again. While the popup is open, it loads the thumbnail (item 6). Video file addresses and the lists of qualities embedded in the page are listed without being requested
When you open the Savvid popup on a tab it was not watching yet (a page that was already open when Savvid started): the addresses of the page and its frames and the time each started loading, the addresses of the files they already loaded (the browser's resource timing list) with the size of each one they received in full, and the addresses of their video and audio elements with the length of what each one playsto find the video without reloading the pageNo. They are read into memory only: at most 8 that look like playlists or media files are passed to detection (item 8), which requests the playlists among them: addresses from the page's list of loaded files, and playlist addresses its video and audio elements name, even ones the page has not loaded yet; the others are discarded at once and never stored. A size lets detection skip a file too small to be a video; a size and a length are shown with the file they belong to, as for a video Savvid saw load

Savvid for Chrome does not detect or download YouTube media. It never lists or requests a video or playlist at an address on youtube.com, youtu.be, youtube-nocookie.com, youtubekids.com, googlevideo.com or ytimg.com (or their sub-domains), and it lists nothing in a tab that shows a YouTube page. Its content script does not run on YouTube pages (youtube.com, youtu.be, youtube-nocookie.com, youtubekids.com and their sub-domains). Savvid for Firefox downloads YouTube videos as its one extra feature; its privacy addendum at https://savvid.net/privacy/firefox/ describes what that feature reads and sends.

Network requests Savvid makes

Requests go to the servers that the pages you visit name, including embedded frames and ads on those pages: the playlist addresses a page requests, the addresses listed inside those playlists (other qualities, segments, keys, subtitles), the playlist addresses a page names in its embedded video data (item 1), the player data addresses of item 5 and the playlist addresses a page loaded, or names in its video and audio elements, before Savvid was watching it (item 8), the first bytes of the files a page plays in slices (item 9), and to the address of a link you choose with Find video with Savvid (item 7). Apart from that link, these servers are chosen by the page and its playlists, not by Savvid, and they can belong to other companies than the site you are on. Savvid never fetches addresses on your local network or your own computer, for detection or for a download, unless the page you are on is itself on such an address (for example the web interface of a media server at home). These are localhost, the ranges 127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, 169.254.0.0/16 and 100.64.0.0/10, and local host names such as *.local and *.lan; this includes a media file on such an address that a public page plays. A browser rule also refuses Savvid's own requests that a public address redirects to such an address. The rule covers the requests Savvid makes itself (playlists, segments, keys, subtitles and the files it converts), not a single media file that Chrome's downloader saves directly. While a tab is open on a page on your local network (until that tab moves on to a public website or closes), or a download from such a page runs, Savvid's requests to the local addresses that page uses are let through for every tab, including a request that a public address redirects there. Savvid judges this from the address as written: a public host name whose DNS entry points to a local address is not fully covered. Savvid never contacts a server of its own; it has none.

  1. Playlists and manifests: HLS master and media playlists and DASH manifests, once when a stream is detected (to list its qualities) and again when you download it. This includes a playlist that a server redirects a request of the page to: when the page made that request with HEAD (a player that only checks an address) and Savvid has not read the playlist from the browser's own request of it within 1.5 seconds, Savvid requests that playlist itself (see Cookies below). A playlist or DASH manifest address that a page names in its embedded video data (see What Savvid reads in your browser) is requested in the same way, without cookies when Savvid lists its qualities; when you download it, it carries cookies like any other download (not in incognito tabs, see Cookies below).
  2. Media segments and files: the segments, initialisation segments and byte ranges of the stream you download, or the media file itself. A single media file that you save as it is (for example an MP4 or WebM file, without conversion) is handed to Chrome's own downloader, which fetches it, except when it comes from an incognito tab or is on your local network while the page is a public website; everything else, including a file you convert, is fetched by Savvid itself. When the server refuses Chrome's downloader or answers it with something other than the file, when a network or server error cuts its transfer off, or when no data arrives for 90 seconds, Savvid fetches that file itself instead, from the start, and the part Chrome had saved is deleted.
  3. HLS key files: the AES-128 key file that an HLS playlist links to (standard HLS encryption that every HLS player handles, not DRM), used only on your computer to read that stream, the same way the page's player does. DRM-protected content (Widevine, PlayReady, FairPlay) is never downloaded.
  4. Subtitles: subtitle playlists and WebVTT or TTML files of the stream, when subtitles are enabled.
  5. Player data requests: for five known video players Savvid repeats, once, the metadata request the page's player just made, to read the list of available files. Only GET requests are repeated, never a request body, and at most 5 per 10 seconds per tab. The repeated request carries headers copied from the player's own request: the player's Accept header and, when the player sent them, the Brightcove policy key (BCOV-Policy) and access token (Authorization) and Rumble's X-Requested-With header. No other header of the player's request is copied. These headers go only to the server the player sent them to (and to the address it redirects the request to, if it does), are held only in Savvid's memory and are never stored.
    • JW Player (cdn.jwplayer.com/v2/media), Wistia (fast.wistia.com or fast.wistia.net /embed/medias/<id>.json) and Brightcove (edge.api.brightcove.com/playback or edge-auth.api.brightcove.com/playback) are requested without cookies, but with the player's Authorization (access token) and BCOV-Policy (policy key) headers when the player sent them to Brightcove. The playlists their answer names are requested without cookies unless they are on the site of the page or frame that made the request.
    • Rumble (rumble.com/embedJS) and Dailymotion player metadata are requested with the cookies your browser holds for rumble.com or dailymotion.com, and only when the request was made by a page or player frame on that same site (this includes a Rumble or Dailymotion player embedded in another site's page) or the tab is on that platform. In incognito tabs they are not repeated at all.
  6. Thumbnails: while the popup is open, it loads the stream thumbnails of the current tab from the https image address that the page names. That address is chosen by the page (its metadata, its embedded video data or its player), so it can be on any server, including one of another company. The image is fetched without cookies (credentials: 'omit') and without a referrer (referrerPolicy: no-referrer), except while Savvid holds a Referer rule for that server (a download from it is running, or a detection in any open tab needed one). The thumbnail request then carries the Referer and Origin headers that rule sets: the origin of the page the download or detection belongs to, which can be a page in a different tab (see Referer and Origin below). The image is shown from a copy held in the popup's memory while it is open. Thumbnails on local-network addresses are not loaded when the page is a public website, and a popup opened in an incognito window loads none. Thumbnail images are never stored. The thumbnail address of a detected stream is kept in the session list of detected streams (registry:v1, deleted when the browser closes) and in the entry of a download while it runs (activeDownloads); the download history and the saved streams never keep it.
  7. Links you choose: when you use Find video with Savvid on a link whose address does not already look like a video or playlist, Savvid requests the first kilobyte of that address (a ranged GET, bytes 0-1023; the address may be an ordinary web page) to find out whether it is a video or a playlist. Nothing from the answer is kept unless it is media, which is then listed like any other detected stream. The request carries your cookies only when the link is on the same site as the frame that shows it (the page itself for a link outside any embedded frame), never in incognito tabs; with cookies it follows no redirect (a redirect is requested again without cookies). While a rule of another origin or of the other browsing context is installed (see Cookies below), the request follows no redirect at all, and a link that answers with one is not listed. As for any address, the local-network rule above applies.
  8. Page scan: each time you open the popup on a tab Savvid was not watching yet (see What Savvid reads in your browser), Savvid looks through the addresses that page already loaded and its video and audio sources, and passes at most 8 that look like playlists or media files to detection. Playlists among them are requested as in item 1 (a playlist named by a video or audio element is requested even when the page has not loaded it yet); media files are listed without being requested. A playlist is requested with your cookies only when it is on the same site as the frame that loaded or names it (the page itself for an address outside any embedded frame), never in incognito tabs, as for Find video with Savvid. Ads, YouTube addresses, segments and, while the page is a public website, local-network addresses are skipped. No other address from the list is requested or kept. A tab Savvid was already watching is never scanned. The scan runs in Savvid's own isolated copy of the page's scripting context, never among the page's own scripts: it changes nothing in the page, and the page's scripts cannot read what it collects.
  9. Files a page plays in slices: when a page plays a video by requesting its files in byte-range slices (addresses with bytestart and byteend parameters) and Savvid cannot match a file to the qualities of a video it already found, Savvid notes the address of the file without those two parameters. Each time the popup loads the list of videos of that tab (when you open it, and when it loads the list again), Savvid requests the first 4 kilobytes of each noted file of the page the tab shows that it has not requested before (a ranged GET, bytes 0-4095, without cookies), once per file and at most 24 files each time, to read whether the file holds video or sound, its picture size, its codec, its length and its total size. When the index of a long file starts in those 4 kilobytes and ends after them, Savvid requests the rest of that index in the same way (one more ranged GET, only when the index ends within the first 64 kilobytes of the file). A video file is offered together with a sound file only when both answered and their lengths match; nothing else from the answer is kept, and a file that does not answer with the start of a larger file is not listed. Only the popup starts these requests: none is made for a tab before you open the popup on it, but requests the popup started can still go out after you close it.

How these requests are made:

What Savvid stores

All of this is kept in Chrome's storage for the extension, on your computer. It is never uploaded. "local" is the extension's chrome.storage.local; "IndexedDB" is the extension's own database (videograb), which only Savvid's own pages and background can open, never the scripts it runs in web pages; "session" is chrome.storage.session, deleted when the browser closes. Should the database fail to open, the items marked IndexedDB are kept in session storage instead (trusted: keys) until the browser closes. Items an older version of Savvid kept in local storage (activeDownloads, downloadHistory, savedStreams) are moved to the database once and removed from local storage. Two markers in the database record that move (legacyLocalMigrated and savedStreamsMigrated), and schemaVersion (local) records the version of the storage layout; they hold no page data.

Item Where Contents How long
Settings (userSettings)localyour choices in the settings paneluntil you change them or remove the extension
Download history (downloadHistory)IndexedDBthe last 50 finished or failed downloads: title, file name, size, status, the stream addresses needed to retry (with their query strings, which can hold the site's signed access parameters), the address of the web page the video was found on (needed to set the Referer when a download is retried) and, when the video played in a player frame embedded from another site, the address of the embedded player frame with its query string (which can hold the player's share key or signed access parameters; only its origin is used, as the Referer); for a video saved with missing parts, which segments are missing (their positions), whether and until when their parts are kept, the file's place in your downloads folder (to replace the incomplete copy when Retry missing or Download again rebuilds it), and the reason of a failed retry; no thumbnailsuntil you clear it or remove the extension
Saved streams (savedStreams)IndexedDBat most 5 streams you started a download from, shown in the popup as Recent downloads: title, site, quality list, the time it was saved, the stream addresses (with their query strings), the address of the web page the video was found on (needed to set the Referer when a download is started again from the list) and, when the video played in a player frame embedded from another site, the address of the embedded player frame with its query string (which can hold the player's share key or signed access parameters; only its origin is used, as the Referer); no thumbnails; never for DRM streams or incognito tabsuntil newer saves replace them (at most 5 are kept), until you remove one or clear the list (in the Recent downloads list of the popup, or with Clear Recent downloads in Settings, Your data), until you use Reset saved data (in Settings, Your data, or in the panel shown when Savvid could not start), or until you remove the extension. An entry can no longer be downloaded from the list once it is older than 6 hours by default (setting: 1 to 168 hours) or a signed expiry in its address has passed; such an entry is deleted the next time the popup opens in a regular window, and so is an entry an older version of Savvid saved for an HLS or DASH stream, whatever its age (those versions kept no audio tracks for it), and any other entry an older version saved that is more than 24 hours old (a younger one is kept, without the live mark those versions could set by mistake). A popup in an incognito window only hides such entries and deletes nothing
Active downloads (activeDownloads)IndexedDBdownloads in progress: stream addresses, title, progress, the address of the web page the video was found on (needed to set the Referer while the download runs and when it is restarted), the stream's thumbnail address and, when the video played in a player frame embedded from another site, the address of the embedded player frame with its query string (which can hold the player's share key or signed access parameters; only its origin is used, as the Referer), so a download survives a restart of the extension, and, for a retry of a finished download, a copy of its history entry (restored when the retry fails), and, while the rebuilt file of a retried download is saved over its incomplete copy, the full path of that copy on your computer (to check that the new file lands exactly there and to leave the old download item alone otherwise; never for incognito downloads)removed when the download ends
Theme and preferred quality (theme, preferredQuality)locallight, dark or follow the system; the last chosen video height and codecuntil you remove the extension
Theme mirror (vg-theme)the popup page's own local storagelight, dark or follow the system, so the popup opens in the right coloursuntil you remove the extension
First-run card (introSeen)localthe version number of the first-run card you closed with Got it (not written from an incognito window)until you remove the extension
Recent downloads list state (vg-recent-open)the popup page's own local storagewhether the Recent downloads list in the popup is open (1) or closed (0)until you remove the extension
Failures seen (vg-failures-seen)the popup page's own local storagea time: that of the newest failed download the Downloads tab has shown, or of the first time the popup opened (a number; no titles or addresses), so a download that failed while the popup was closed is marked on the Downloads tab at the next open (not written from an incognito window)until you remove the extension
Pending removals (popup:pendingDismissals)sessionthe identifiers (no titles or addresses) of download history entries you removed while Undo is still offeredremoved after 5 seconds, once the removal is carried out (sooner when another message replaces the Undo offer); if the popup closes before then, the removal is sent at once and the identifiers stay until the next time the popup opens; deleted when the browser closes
Detected streams, header rules, pending saves (registry:v1, headerRules, pendingBrowserDownloads, retainedBlobs, cancelledIds, parked:v1, slices:v1, contentScriptsInjected, sessionStartedAt)sessionstreams detected in your open tabs (their addresses, the address of the page, the title, the thumbnail address and, when the video plays in a player frame embedded from another site, the address of the embedded player frame with its query string), a yes or no flag on each file you chose with Find video with Savvid (so that a video the page plays later does not take it off the list) and, for each open tab, a yes or no flag telling whether Savvid is watching its current page, the addresses of the files a page played in byte-range slices that Savvid has not matched yet, with when their slices were requested and what their first bytes showed (at most 128 per tab, for item 9 of Network requests), and, for a tab whose page played such slices, a hash of each address that page moved to without loading a new page, with when it moved (at most 16 per tab; no page address in clear), the bookkeeping of running downloads, contentScriptsInjected (true once the content script was added to the open tabs in this browser session; it holds no page data) and sessionStartedAt (when Savvid's background first started in this browser session, to tell whether a tab's page loaded before Savvid was watching; it holds no page data)deleted when the browser closes or the extension is updated or reloaded
Temporary download files (OPFS)the extension's private file storage (OPFS)the parts of a download while it is assembled, and the title of the videodeleted after the file is saved or cancelled (for a video saved with missing parts, its parts and title stay as described in the next row); if you cancel the save dialog, the finished file is kept for 10 minutes so you can save it again. Files left behind by a crash or by closing the browser during a download stay until the next time Savvid's converter starts (when you start a download or open the settings panel), which then deletes the ones more than 24 hours old
Parts of a video saved with missing parts (OPFS, partial.json)the extension's private file storage (OPFS)when a few segments of a video could not be downloaded and the video was saved without them: the downloaded parts of that video (the same video data as the saved file), the title of the video, and a list of the missing segments (their numbers, positions, durations, file names, a short fingerprint of each one's address instead of the address itself, and where they belong in the parts), and for a video saved as MKV the subtitle files embedded in it, so Retry missing can fetch only those segments and embed the subtitles again; never for incognito downloads, live streams or files over 4 GBuntil Retry missing completes the video or you remove the entry from the Downloads list (Dismiss, Clear finished or Clear finished downloads); otherwise for 24 hours after the video was saved (a Retry missing that still misses segments starts a new 24 hours) or until newer downloads push the entry out of the list (it keeps the last 50), and they are deleted shortly after that (if the browser is closed at that time, once Savvid runs again); sooner when the kept parts of all such videos together pass 4 GB (the oldest go first); deleted when the extension is removed

Finished downloads are saved by Chrome to your downloads folder like any other download.

Incognito windows

Savvid runs in incognito windows only if you turn on "Allow in Incognito" for it in chrome://extensions. If you do:

Permissions and why they are needed

Permission Used for
Access to http and https sites (http://*/*, https://*/*)detecting streams on the sites you visit and downloading them from the servers that their pages and playlists name; Savvid asks for no other kind of address (for example no file:// pages)
Content script on http and https pages, in every frame, not on YouTube pagesnoting whether a page uses DRM (to mark protected videos), reading the page's title, metadata and video elements for file names, thumbnails and video sizes, to leave out videos the page only loads ahead and to tell which video plays, telling Savvid when a page comes back from the back/forward cache, and reading the video addresses a page embeds in its own data, again after the top page changes its address without loading a new page (see What Savvid reads in your browser)
webRequestseeing the addresses and response headers of the http and https requests in your tabs, to find playlists and media files, and the request headers of the player data requests of item 5; no request is blocked or changed
webNavigationkeeping the popup's list of found videos and the toolbar badge in step with the tab: the list is cleared when the tab opens a new page, comes back when you reload the page or go back or forward to it, and moves to Earlier on this page when the page changes its address without loading a new page or a player frame opens another page; such an address change of the top page also has the content script read the page's embedded video data again, for the video of the new address; also finding which player frame a video came from, whose address is then used as the Referer for that video
scriptingreading the title of a frame that plays a video and the page's thumbnail when the content script cannot answer, adding the content script to the http and https tabs that were already open when Savvid was installed, updated, reloaded or enabled again (Chrome adds it only to pages loaded afterwards; YouTube pages never get it), and, when you open the popup on a tab Savvid was not watching yet, reading the addresses that page already loaded and its video and audio sources (item 8)
storageyour settings and choices and the version of the storage layout (local storage); the list of streams found in open tabs, the header rules, the bookkeeping of running downloads and the downloads of incognito tabs (session storage). The download history, the saved streams and the regular downloads in progress are kept in the extension's own database (IndexedDB), which needs no permission
downloadssaving files to your downloads folder, and asking Chrome where a saved file is and whether it is still there, so that the Downloads tab can show its folder and Show in folder can open it (the answer is not stored)
offscreenthe background page that fetches, converts and assembles downloads
unlimitedStoragekeeping Chrome from deleting the extension's own data when the disk is almost full: the database (the download history, the saved streams and the downloads in progress) and the private file storage (the parts of a download while it is assembled, the copy kept for Save again and the parts kept for Retry missing); it also lets one download use the free disk space instead of a fixed share of the disk. It has no function of its own and gives no access to any page or file
alarmstimed work that must also happen while Savvid's background is stopped: checking running downloads every 30 seconds, so that a stalled one restarts from its last checkpoint or fails; deleting the copy kept for Save again after 10 minutes; deleting the parts kept for Retry missing after 24 hours; and deleting the private copy of a finished video once its subtitle files are saved
declarativeNetRequestWithHostAccesssetting Referer and Origin on Savvid's own requests, and refusing Savvid's own requests to your local network when the page is a public website
notificationsthe "Download complete", "Saved with warnings", "Saved with missing parts", "Download failed" and "Retry failed" notifications (not shown for incognito downloads; can be turned off in Settings)
contextMenusthe "Find video with Savvid" item on videos, audio and links

What Savvid does not do

Asking for help

In Help, and on the panel that says no video was found, Copy diagnostics puts a short text on your clipboard: the versions of Savvid and Chrome, the site of the tab (its origin only, never the page address or a title), whether Savvid saw the page load, how many videos it found by kind, whether the converter works, whether the window is incognito, and your settings (the file name template and the subfolder only as default or custom). It is made only when you press the button, it goes only to the clipboard, and it leaves your computer only if you paste it somewhere, for example into an email to us. Write to us in Help opens an email to the address under Contact in your mail program, with only a subject; Savvid sends nothing itself.

Savvid for Firefox

Savvid for Firefox (desktop, Firefox 140 and later) is made from the same code as Savvid for Chrome. Everything this policy says about what Savvid reads, the requests it makes, what it stores and what it does not do holds for it too, with these differences:

Changes

This policy is published at https://savvid.net/privacy. If it changes, the updated version will be posted there with a new date.

Contact

For questions about this privacy policy, email privacy@savvid.net.