隐私政策
适用版本：SevenMirror Extension v0.1.21。政策修订日期：2026-10-08。
1. 适用范围与发布者
本政策说明 SevenMirror 浏览器扩展的数据处理，以及与配套 Android 应用和 SevenMirror 服务之间的数据流。
扩展发布者为 GitHub 用户 huaxianyan，项目入口为 SevenMirror-Project。
你选择的服务可以由你自行部署，也可以由其他运营者提供。服务运营者的日志、备份、保留期限和其他处理活动，还需查看其说明。
2. 处理哪些数据
- 你选择同步的通知：来源应用、标题、正文、展示图片信息、可用操作，以及用户输入的回复。
- 设备与连接信息：设备显示名称、设备及工作区标识、服务地址、配对输入、连接凭据和设备身份密钥。
- 功能设置与状态：应用和接收设备选择、展示偏好、快捷操作规则、通知版本和待处理操作状态。
通知内容可能包含联系人信息、个人通讯、健康信息、财务支付信息或地点信息，取决于你选择的应用和原通知内容。
扩展不读取普通网页内容、浏览历史或其他网站的 Cookie，也不监测网页上的键盘和鼠标活动。
3. 数据用途与控制
这些数据用于配对、授权、通知同步、展示、操作、回复，以及你启用的快捷规则共享。
你可以在 Android 端选择同步应用和接收浏览器，也可以暂停同步或调整选择。浏览器的服务访问授权按你填写的服务地址申请。
扩展没有广告或第三方分析 SDK。我们不出售用户数据，不将数据用于定向广告、无关分析或信用与贷款资格判断。
4. 传输、共享与安全
通知、操作与回复内容在发送端加密，由获准的接收设备解密。启用规则共享时，服务接收加密的规则数据。
中继服务处理连接授权、设备标识、路由与投递状态等必要元数据。服务及其网络运营者还可能处理 IP 地址、访问时间和连接日志。
普通远程服务连接使用 HTTPS，本机回环地址允许 HTTP。端到端加密覆盖业务内容，不覆盖全部网络元数据。
浏览器本地会保存解密后的通知内容。部分通知、回复和连接凭据以可恢复的明文保存，本地数据并非全部静态加密。
请保护浏览器配置、系统账号和备份，谨慎选择接收设备及服务运营者。加密传输不能消除端点访问或系统备份带来的风险。
5. 保留与删除
通知和必要的同步状态保存在浏览器本地。通知移除后，版本对账所需的历史记录仍可能保留，目前没有独立的产品级通知历史清理入口。
待处理操作记录的保留期限为 30 天，过期记录在后续存储活动中清理。这不是所有通知数据的统一保留期限。
暂停同步、调整接收选择或撤销服务访问，主要控制后续处理，已提交的数据和历史记录仍可能存在。
卸载扩展或删除对应浏览器配置可以移除扩展的本地数据。浏览器备份、系统通知历史、其他接收端副本，以及服务端记录需分别处理。
服务端数据的保留和删除由相应运营者负责。请联系你使用的服务运营者，确认其日志、备份和删除办法。
6. 本隐私页面
页面本身不设置 Cookie，不加载第三方脚本、字体或统计服务。本页通过 GitHub Pages 托管，GitHub 可能为提供托管和安全服务处理访问 IP 地址等请求信息。
托管平台的处理方式见 GitHub 隐私声明。
7. 联系与政策更新
隐私问题可通过 项目 Issues 联系发布者。Issues 是公开渠道，GitHub 的处理方式见 GitHub 隐私声明。
请只提交一般咨询，避免公开通知内容、回复、配对输入、密钥或连接凭据。如需私下沟通，请先请求合适的私密联络渠道。
功能或数据处理发生变化时，我们会更新本页的适用范围与修订日期。部署方应将更新后的政策与实际服务行为保持一致。
Privacy Policy
Applies to SevenMirror Extension v0.1.21. Policy revision date: October 8, 2026.
1. Scope and publisher
This policy describes data handling by the SevenMirror browser extension and its data flow with the companion Android app and SevenMirror service.
The extension publisher is GitHub user huaxianyan. The project is available at SevenMirror-Project.
You may host your own service or use one provided by another operator. Consult that operator's information about logging, backups, retention, and other processing activities.
2. Data processed
- Selected notifications: source app, title, text, display-image information, available actions, and replies you enter.
- Device and connection information: device names, device and workspace identifiers, service address, pairing input, connection credentials, and device identity keys.
- Settings and state: app and receiving-device selections, display preferences, quick-action rules, notification versions, and pending-action state.
Notification content may include contact details, personal communications, health information, financial or payment information, or location information, depending on the apps you select and the original notifications.
The extension does not read ordinary web-page content, browsing history, or other websites' cookies, or monitor keyboard and mouse activity on web pages.
3. Purposes and controls
Data is used for pairing, authorization, notification syncing and display, actions, replies, and quick-rule sharing that you enable.
You can select apps and receiving browsers in the Android app, pause syncing, or change selections. Browser access to the service is requested for the service address you enter.
The extension includes no advertising or third-party analytics SDK. We do not sell user data or use it for targeted advertising, unrelated analytics, or creditworthiness and lending decisions.
4. Transmission, sharing, and security
Notification, action, and reply content is encrypted on the sending device and decrypted by authorized receiving devices. When rule sharing is enabled, the service receives encrypted rule data.
The relay processes necessary metadata such as connection authorization, device identifiers, routing, and delivery state. Service and network operators may also process IP addresses, access times, and connection logs.
Ordinary remote-service connections use HTTPS. HTTP is permitted for local loopback addresses. End-to-end encryption protects business content, not all network metadata.
The browser stores decrypted notification content locally. Some notifications, replies, and connection credentials are stored in recoverable plaintext. Not all local data is encrypted at rest.
Protect your browser profile, system account, and backups, and choose receiving devices and service operators carefully. Encrypted transmission does not eliminate risks from endpoint access or system backups.
5. Retention and deletion
Notifications and necessary syncing state are stored locally in the browser. Historical records needed for version reconciliation may remain after a notification is removed. There is currently no dedicated product-level notification-history clearing control.
Pending-action records have a 30-day retention period. Expired records are cleaned up during subsequent storage activity. This is not a uniform retention limit for all notification data.
Pausing syncing, changing receiving-device selections, or revoking service access primarily controls subsequent processing. Previously submitted data and historical records may remain.
Uninstalling the extension or deleting its browser profile can remove the extension's local data. Browser backups, system notification history, copies on other receiving devices, and service-side records need to be handled separately.
The relevant service operator is responsible for service-side retention and deletion. Contact the operator you use for its logging, backup, and deletion procedures.
6. This privacy page
This page itself sets no cookies and loads no third-party scripts, fonts, or analytics. This page is hosted on GitHub Pages. GitHub may process request information such as visitor IP addresses to provide hosting and security services.
See GitHub's Privacy Statement for the hosting platform's practices.
7. Contact and policy updates
Contact the publisher about privacy through project Issues. Issues are public. GitHub's practices are described in its Privacy Statement.
Submit only general questions. Avoid posting notification content, replies, pairing input, keys, or connection credentials publicly. If private communication is needed, first request an appropriate private contact channel.
When features or data handling change, we will update this page's scope and revision date. Deployers should keep the published policy consistent with actual service behavior.