VidGet (嗅嗅) - Privacy Policy / 隐私政策

1. 数据收集

本扩展不向任何远端服务器发送数据. 在用户主动操作时, 扩展会读取以下数据, 仅用于在本机内传递给配套桌面客户端:

视频流元数据: 在白名单视频站点上, 嗅探当前页面正在播放的视频流 URL / 标题 / 封面, 用户在扩展弹窗中查看, 点击下载时转交本机桌面客户端
登录 cookie: 在白名单站点上, 严格按 cookie 名白名单读取登录 session cookie (例如 Bilibili SESSDATA, YouTube SAPISID/SID), 仅在用户主动点下载时一次性传给本机桌面客户端用于反 LOGIN_REQUIRED 或解锁大会员画质
右键链接: 用户右键链接选 "用嗅嗅 Pro 下载" 时, 扩展拿到该链接 URL + 当前页面 URL (作 Referer), 转交本机桌面客户端下载

以下数据从不收集:

个人身份信息 (姓名, 邮箱, 电话等)
浏览历史 (扩展仅在白名单视频站点和用户主动右键的链接上工作, 不监控用户全网浏览)
网页正文内容 (除上述视频元数据外)
设备信息或位置
健康 / 财务 / 通信内容

2. 单一目的与架构

本扩展的单一目的是: 作为浏览器与本机 VidGet Pro 桌面客户端之间的桥, 检测可下载的媒体链接并转交本机客户端处理实际下载. 扩展自身不下载文件, 实际下载全部由用户本机的桌面客户端完成 (类似 IDM Integration Module + IDM 桌面端的协同).

扩展在用户浏览器内进行的处理仅限以下范围, 全部在本地完成:

数据	用途	范围
视频流元数据	识别白名单站点正在播放的视频, 在扩展弹窗展示给用户选	仅当前 tab, `chrome.storage.session` 浏览器关闭自动清空
右键链接 URL	用户右键 "用嗅嗅 Pro 下载" 时拿到链接 + 当前页 URL, 转交本机桌面客户端	仅用户主动点击时, 不持久化
登录 cookie	仅在用户点击下载时读取, 用于让站点服务器返回登录态内容 (大会员画质 / 反 LOGIN_REQUIRED)	白名单站点 (`bilibili.com` / `youtube.com` / `google.com`), 严格按 cookie 名白名单, 不持久化

⚠ 扩展所有处理均在本地完成, 不向任何远程服务器发送数据. 用户点击下载时, 扩展把视频网址传给本机的桌面客户端 (本机内部通信, 不走互联网).

3. 第三方共享

本扩展不与任何第三方共享数据. 不集成任何 analytics, 广告, 或远程遥测服务.

4. Cookie 用途说明

本扩展请求 cookies 权限是为了在用户主动点击下载时, 读取白名单站点的登录 cookie, 一次性传给本机桌面客户端, 让站点服务器返回用户已登录状态下能访问的内容. 具体范围:

bilibili.com: 读 SESSDATA / bfe_id 等关键 cookie, 让 Bilibili 返回大会员画质
youtube.com / google.com: 读 yt-dlp 抓 YouTube 实际需要的关键 cookie (SAPISID / SID 等), 反 LOGIN_REQUIRED

严格按 cookie 名白名单读取 (例如 youtube/google 域大约 100 个 cookie, 仅取 yt-dlp 抓 youtube 需要的约 15 个), 不读取分析 / 广告 / 其他服务的 cookie.

Cookie 仅在用户点击下载时使用, 不被扩展存储, 不发送到任何我们运营的远端服务器. 仅在本机内传递给桌面客户端.

5. 权限完整说明

权限	用途
`webRequest`	在白名单站点上只读监听网络请求, 识别可下载的媒体流 URL (HLS / DASH / MP4 等). 不修改, 不拦截, 不重定向
`downloads`	覆盖 blob URL 的默认 UUID 文件名为可读标题, 可选展示下载进度
`storage`	用 `chrome.storage.session` 临时缓存当前 tab 嗅探结果, 浏览器关闭自动清空
`tabs`	读取当前 tab URL 关联视频; 监听 tab 关闭事件清缓存
`scripting`	仅在用户操作扩展弹窗时, 在当前 tab 注入小脚本读取 og:image / video.poster 用作下载 UI 封面
`cookies`	见上述 Cookie 用途说明
`declarativeNetRequestWithHostAccess`	为白名单站点的媒体 CDN 请求重写 Referer 头, 用于绕过防盗链 (否则下载返 HTTP 403)
`nativeMessaging`	跟用户本机的 VidGet Pro 桌面客户端通信. 通信仅限本机, 不走互联网
`contextMenus`	在链接的右键菜单加一项 "用嗅嗅 Pro 下载", 仅在 link 上下文显示, 不在页面 / 选区 / 图片等其他上下文显示
`host_permissions <all_urls>`	白名单站点的视频 CDN 域名按会话动态调度 (跟页面域名不同), webRequest 监听需观察跨域请求才能捕获实际媒体 URL; 非白名单页面发起的请求被静默丢弃, 不入库不上传

6. 配套桌面客户端

VidGet Pro 桌面客户端是配套的本机程序, 用户需单独下载安装. 它接收扩展转交的下载任务, 跟视频源服务器直接通信完成下载. 桌面客户端不向 VidGet Pro 项目方上传任何用户数据.

7. 用户权益与联系

用户随时可在 chrome://extensions/ 移除本扩展, 所有本地缓存立即失效
如有隐私相关问题, 请通过 Chrome Web Store 商店页面的"开发者联系方式"反馈

8. 政策变更

本政策若有更新, 将通过版本说明公告. 用户继续使用即视为同意更新.

1. Data Collection

This extension does not send any data to remote servers we operate. When the user actively interacts with the extension, the following data is read solely for forwarding to the locally-installed companion desktop client:

Video stream metadata: On a small allowlist of video sites, the extension detects video stream URLs / titles / thumbnails of the currently playing video; the user views these in the popup and selects which to download via the local companion app
Authentication cookies: On allowlisted sites, the extension reads login session cookies, strictly limited to a per-domain allowlist of cookie names (e.g., Bilibili SESSDATA, YouTube SAPISID/SID); these are forwarded once to the local companion only when the user explicitly clicks download, used to bypass LOGIN_REQUIRED or unlock HD-quality streams the user is entitled to
Right-click link URL: When the user picks "Download with VidGet Pro" from the link right-click menu, the extension obtains the link URL plus the current page URL (used as Referer) and forwards both to the local companion app

The following data is never collected:

Personal identifiers (name, email, phone)
Browsing history (the extension only operates on whitelisted video sites and on links the user explicitly right-clicks; it does not monitor the user's general browsing)
Page text content (other than the video metadata above)
Device or location information
Health, financial, or communication contents

2. Single Purpose & Architecture

The single purpose of this extension is: act as a bridge between the browser and the locally-installed VidGet Pro desktop client, detecting downloadable media links and forwarding them to the local companion app for actual download. The extension itself does not download files. All actual downloading is performed by the user's local desktop client (similar to the IDM Integration Module + IDM desktop application coupling).

The extension's processing is limited to the following, all performed locally inside the browser:

Data	Purpose	Scope
Video stream metadata	Identify videos playing on whitelisted sites; display in the popup for user selection	Only the active tab; `chrome.storage.session` is automatically cleared on browser close
Right-click link URL	When user picks "Download with VidGet Pro" on a link, capture the link URL + current page URL, forward to local companion	Only when user actively clicks; not persisted
Login cookies	Read only when user clicks download, used so the source server returns content the user is entitled to in their logged-in state (HD streams / bypass LOGIN_REQUIRED)	Allowlisted sites (`bilibili.com` / `youtube.com` / `google.com`), strict cookie-name allowlist, not persisted

⚠ All extension processing happens locally. No data is sent to any remote server. When the user clicks download, the extension passes the video URL to the local desktop client (local communication only, never via the internet).

3. Third-Party Sharing

This extension shares NO data with any third party. It contains no analytics, advertising, or remote telemetry.

4. Cookie Permission

This extension requests the cookies permission so that, when the user actively clicks download, it can read login cookies from a small allowlist of source sites and forward them once to the local companion desktop client, so that the source server returns content the user is entitled to in their logged-in state. Specific scope:

bilibili.com: reads SESSDATA / bfe_id and similar key cookies so Bilibili returns HD-quality streams
youtube.com / google.com: reads only the cookies yt-dlp actually requires to fetch YouTube content (SAPISID / SID etc.), bypassing LOGIN_REQUIRED

Cookies are read using a strict per-domain name allowlist (e.g., the youtube/google domains have ~100 cookies in total but we only read ~15 needed by yt-dlp). Analytics / advertising / other-service cookies are never read.

Cookies are used only when the user clicks download, are never stored by the extension, and are never sent to any remote server we operate. They are passed only locally to the desktop client.

5. Permissions Reference

Permission	Use
`webRequest`	Read-only monitoring of network requests on whitelisted sites to detect downloadable media stream URLs (HLS / DASH / MP4 etc.). Does not modify, block, or redirect.
`downloads`	Override blob URL default UUID filenames with human-readable titles; optionally surface download progress.
`storage`	Cache per-tab sniffed media metadata in `chrome.storage.session`, automatically cleared on browser close.
`tabs`	Read the active tab URL to associate detected media with the correct page; listen to tab close events to clean up cache.
`scripting`	On user popup interaction only, inject a tiny snippet into the active tab to read og:image / video.poster as a download UI thumbnail. Not used for general DOM injection.
`cookies`	See "Cookie Permission" above.
`declarativeNetRequestWithHostAccess`	Rewrite Referer header for media CDN requests on whitelisted sites, required to bypass anti-hotlinking that would otherwise return HTTP 403.
`nativeMessaging`	Communicate with the user's locally-installed VidGet Pro desktop client. Local communication only, never via the internet.
`contextMenus`	Add a single "Download with VidGet Pro" item to the link right-click menu. Shown only on link contexts, never on pages / selections / images / other contexts.
`host_permissions <all_urls>`	Allowlisted sites stream media through CDN domains chosen dynamically per session (separate from the page hostname); webRequest needs cross-origin visibility to capture the actual media URL. Requests originating from non-allowlisted pages are silently dropped — never logged or uploaded.

6. Companion Desktop Client

The VidGet Pro Desktop Client is a companion native application that the user installs separately. It receives download tasks from the extension and communicates directly with video source servers to perform the download. The desktop client does not upload any user data to the VidGet Pro project.

7. Rights & Contact

Users can remove the extension at any time via chrome://extensions/; local cache is destroyed immediately.
For privacy-related concerns, please use the "Developer Contact" link on our Chrome Web Store listing.

8. Policy Updates

Updates to this policy will be announced via release notes. Continued use indicates acceptance.