LiteDownload 隐私政策 / Privacy Policy

最后更新 / Last updated: 2026-10-26

开发者 / Developer: song
联系邮箱 / Contact: soil@codot.si

中文

本政策适用于 Chrome 扩展 LiteDownload。LiteDownload 用于在工具栏弹窗或侧边栏中查看、启动、控制和清理 Chrome 下载。扩展不含广告、使用统计、跟踪器或开发者运营的数据接收服务；开发者不接收你的下载记录、文件内容或扫描结果。

1. 处理的数据与用途

• 下载信息：通过 Chrome 下载接口读取文件名及本机路径、下载和最终网址、大小、进度、状态、时间、错误与安全提示，以及文件图标，用于显示、搜索、通知及用户选择的下载操作。完整下载历史由 Chrome 管理；界面及本次会话会暂存完成这些功能所需的部分信息，不建立开发者服务器上的历史库，也不分析下载文件内容。
• 用户提供的下载地址：你粘贴、拖入、从右键菜单选取或在扫描结果中选择的地址，用于交给 Chrome 下载。批量任务的链接队列会临时保存到本机 Chrome 会话存储，任务结束或停止后清除队列。
• 页面资源信息：只有主动使用“扫描此页面”或相应右键菜单后，扩展才在获得临时授权的标签页中运行只读扫描。扫描涉及当前页面地址、可访问框架地址、链接和媒体地址、图片尺寸、媒体时长、类型与用于排除流媒体或受保护内容的属性；不读取页面正文、表单值或 cookie，不更改页面。扫描结果保存在界面内存中；右键扫描还可能由后台内存暂存，供侧边栏在约 60 秒的有效期内取用。取用后移除，未取用结果在后续清理或后台结束时释放。
• 设置：是否隐藏 Chrome 下载气泡、下载完成/失败/开始通知、是否询问保存位置、显示条数、语言、自动续传，共 8 项设置，以及是否已看过首次使用提示，使用 chrome.storage.sync 保存。
• 本次会话状态：筛选条件、通知去重、文件图标缓存（键中含下载 ID、文件路径和状态）、批量链接与进度、清理进度、自动续传计数及已耗尽记录，保存在 chrome.storage.session 或运行内存中，用于后台唤醒、避免重复通知及恢复界面。
• 二维码：在本机把所选下载地址编码成二维码，不把文件上传到手机或中转服务。扫描二维码的人可以读到该地址；如果地址中包含私有令牌，分享二维码也会分享该令牌。

2. 网络请求与接收方

扩展不向开发者或分析服务上传上述数据，也没有遥测、广告或远程代码。扩展页面的内容安全策略限制直接网络连接，但这不等于下载过程没有联网：当你开始下载、续传或开启的自动续传执行时，Chrome 会请求你选择的文件来源及其重定向目标。这些目标会按正常下载流程收到网络请求和必要的连接信息（例如 IP 地址、请求地址与浏览器适用的请求信息），并适用它们自身的隐私政策。不要下载或分享你无权访问的资源。

开启 Chrome 同步时，设置可能由 Google 同步到你的 Google 账号；开发者无法访问该账号或同步内容。下载队列、扫描结果和会话缓存不会通过扩展的同步存储上传。Google 同步适用 Google 隐私政策。

如果你主动发送支持邮件，开发者会通过邮件服务收到你的邮箱地址、邮件内容及你自行附上的信息，仅用于回复和处理支持请求；请勿发送密码、私有下载令牌或不必要的个人数据。

3. 保存期限与控制

下载历史和已下载文件由 Chrome 与操作系统保存，直至你删除。可以在 LiteDownload 或 Chrome 下载页移除历史记录；文件删除属于单独操作，清空时会提供是否同时删除文件的选项。删除文件不经过回收站，无法由扩展撤销。可续传的中断下载会在批量清空时保留。

会话存储保留到浏览器会话结束，或扩展重新加载、更新、停用/移除时由 Chrome 清除；运行内存在相应页面或后台结束时释放。部分缓存不会在单条下载记录删除的同一时刻立即清除。设置保留到你修改或由 Chrome 清除扩展数据为止；同步设置由 Chrome 和账号的同步设置管理。卸载不会自动删除已下载文件或 Chrome 的下载历史。

支持邮件仅为解决请求和必要后续沟通而保留；你可以通过下列邮箱请求删除。若法律要求保留，将按适用要求处理。

4. 用途限制与分享

开发者不出售或出租数据，不将数据用于广告、跟踪、信用评估、借贷决策或与下载管理及用户发起的支持请求无关的目的。除上述由用户操作触发的下载、Chrome 同步和主动支持邮件外，不向第三方提供数据。LiteDownload 对通过 Chrome API 获得的数据的使用遵守 Chrome Web Store 用户数据政策，包括 Limited Use 要求。

5. 更新与联系

处理方式变更时会更新本政策日期，并在新版发行说明中注明。对本政策、数据或支持邮件有疑问，请联系 song：soil@codot.si。

English

This policy applies to the LiteDownload Chrome extension, developed by song. LiteDownload helps you view, start, control and clear Chrome downloads from a toolbar popup or side panel. It has no advertising, analytics, trackers or developer-operated data collection service. The developer does not receive your download history, file contents or scan results.

1. Data handled and its purpose

• Download information: Chrome's downloads API provides file names and local paths, original and final URLs, sizes, progress, states, timestamps, errors, safety information and file icons. These support display, search, notifications and the operations you choose. Chrome maintains the full history; the interface and current session temporarily cache some information needed for these functions. There is no developer-hosted history database, and the extension does not analyze downloaded file contents.
• Download URLs you provide: Addresses pasted, dragged, selected from a context menu or selected from scan results are passed to Chrome's downloader. Batch queues temporarily store their URLs in local Chrome session storage and clear the queue when the batch finishes or is stopped.
• Page resource information: Only when you invoke Scan this page or its context-menu action does the extension run a read-only scan in a temporarily authorized tab. It reads the current page URL, accessible frame URLs, links, media URLs, image dimensions, media duration and type, and properties used to exclude streams or protected content. It does not read page body text, form values or cookies, or change the page. Results stay in interface memory. Context-menu results may also wait in worker memory for the side panel to retrieve within an approximately 60-second validity period. Retrieved results are removed; unused results are released during later cleanup or worker termination.
• Settings: Eight preferences (Chrome download bubble, completion/failure/start notifications, ask where to save, list size, language and auto-resume) plus the first-run notice flag are saved using chrome.storage.sync.
• Session state: Filters, notification de-duplication, file-icon cache keys (including download IDs, file paths and states), batch URLs/progress, clear-job progress, retry counts and exhausted-retry records are kept in chrome.storage.session or runtime memory to restore the interface and worker tasks and avoid duplicate alerts.
• QR codes: The selected download URL is encoded locally. Files are not uploaded to a phone or relay service. Anyone scanning the code can read the URL, including any private token it contains.

2. Network requests and recipients

The extension does not upload this information to its developer or an analytics service, and contains no telemetry, advertising or remotely executed code. Its content security policy restricts direct connections from extension pages. Downloads still use the network: when you start or resume a download, or an enabled automatic retry runs, Chrome requests the selected file source and any redirect destinations. Those destinations receive the normal download request and necessary connection information, such as your IP address, requested URL and applicable browser request information, under their own privacy policies. Download or share only resources you are authorized to access.

If Chrome sync is enabled, Google may sync preferences to your Google account. The developer cannot access that account or its synced data. Batch queues, scan results and session caches are not uploaded through the extension's sync storage. Google sync is covered by the Google Privacy Policy.

If you voluntarily send a support email, the developer receives your email address, message and any information you attach through the email service, solely to respond and resolve your request. Do not send passwords, private download tokens or unnecessary personal information.

3. Retention and controls

Chrome and the operating system retain download history and files until you delete them. Remove history in LiteDownload or Chrome's downloads page. File deletion is a separate choice: Clear offers an option to also delete files, warns that files bypass the recycle bin, and cannot undo deletion. Resumable interrupted downloads are retained during batch clearing.

Session storage lasts for the browser session, and is also cleared by Chrome when the extension is reloaded, updated, disabled or removed. Runtime memory is released when its page or worker ends. Some caches are not immediately cleared when one history item is removed. Preferences remain until changed or extension data is cleared by Chrome; synced preferences are governed by Chrome and your account's sync settings. Uninstalling the extension does not automatically delete downloaded files or Chrome download history.

Support correspondence is retained to resolve your request and necessary follow-up. You may request deletion using the contact below, subject to applicable retention requirements.

4. Limited use and sharing

The developer does not sell or rent data or use it for advertising, tracking, creditworthiness, lending or purposes unrelated to download management and user-initiated support. Other than user-directed downloads, Chrome sync and voluntary support emails described above, no data is provided to third parties. Use of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.

5. Changes and contact

Material changes to data handling will be reflected in this policy's date and the release notes. For questions about this policy, data or support messages, contact song at soil@codot.si.