Privacy policy

Publisher: WantSave · Effective and updated: October 20, 2026

1. Scope

This policy covers the WantSave 1.1.0 basic Chrome extension, this privacy policy website and questions you send to WantSave's support email. The basic edition saves web videos, audio and images, merges supported media in the browser and provides local download task recovery.

The current basic edition has no extension account, purchases, subscriptions, advertising, telemetry or local agent/MCP integration. Save only content you have the right to download. The source website's access conditions and privacy policy still apply.

2. Data handled by the extension

• Page and media information: addresses and titles of the current page and relevant frames, media elements and links, playlists, playback information and available qualities.
• Media network responses: request URLs, source frames, response types, filenames, file sizes, referring sources and detection times used to identify media.
• Local download tasks: titles, necessary normalized source information, selected quality, status, progress, timestamps, download record identifiers and cached complete media streams, segments or merged files.
• Settings: whether download buttons appear near videos, and automatic, Chinese or English language preferences.

This information supports media discovery and saving, task display, download completion checks and task recovery. The in-page button setting controls the page entry point; background media discovery can still run on authorized pages. You can restrict website access or disable the extension through Chrome's extension settings.

3. Local storage, retention and deletion

Button and language preferences are saved in the current Chrome profile's local extension storage. Network media candidates and some source records containing temporary URL parameters use browser session storage. Relevant media candidates are cleared when pages navigate or tabs close, and session data is cleared when the browser session ends.

Task records and media caches use the extension's local database so tasks can be recovered after closing a task page or restarting Chrome. They remain until you clear the task through the task list. Recovery may require refreshing or supplying a source URL again when a temporary link expires or its query parameters were not retained. Incomplete streams or segments are fetched again. Temporary sources used by new site adapters remain only in the current browser session; an unfinished task may need to be added again from its original page after restarting.

Clearing tasks and caches does not delete files already saved to your computer. You manage disk files and Chrome download history through your operating system and browser. Uninstalling the extension or clearing its data makes its local settings and caches unavailable.

4. Requests to source websites and media servers

Downloads request the source website, playlist and media distribution servers you select. Bilibili and YouTube discovery also request public original-site pages and playback metadata. The YouTube adapter reads public player configuration from the current page. Bundled code calls the already-loaded player URL conversion function; downloaded scripts are never executed. YouTube playback-metadata requests on the original site use the browser's normal site context. These services receive information needed for the request, such as your IP address, request URL and headers, and process it under their own policies.

The extension does not directly read, store or export browser cookies. Chrome may attach existing credentials to some source-site requests according to site and privacy settings. The resource's network protocol depends on its original URL. The extension has no separate form for collecting logins, passwords or payment details.

5. Use and sharing

The extension does not upload media, download tasks or browsing activity to a publisher-operated data collection service and does not use Chrome sync storage. WantSave does not sell this data or use it for advertising, creditworthiness, lending or purposes unrelated to media downloading and local task recovery. Requests needed to deliver downloads are described in the previous section.

WantSave's use of information from Chrome APIs follows the Chrome Web Store User Data Policy, including its Limited Use requirements.

6. This website and GitHub Pages

This is a static website hosted on GitHub Pages. WantSave has added no analytics scripts, advertisements, tracking pixels or login feature to the site. GitHub states that it logs and stores visitors' IP addresses for security when GitHub Pages sites are visited. This is separate from the extension's local media processing.

See GitHub Pages data collection and the GitHub Privacy Statement.

7. Support email

If you choose to email support, WantSave receives your sender address, message and any information you attach to answer and resolve your request. The email provider also processes messages under its own policy. Support correspondence is retained for as long as needed to handle the request and necessary follow-up. You can request deletion using the contact address below.

An issue report normally needs only the extension version, steps and error message. Please leave out passwords, verification codes, private media and complete links containing access tokens.

8. Permissions

9. Changes and contact

When the product or its data handling changes, WantSave will update this policy and its date, along with the corresponding store privacy disclosures. For questions about this policy, data handling or deletion of support correspondence, contact:

Publisher: WantSave
Support email: wantsave.help@gmail.com