生效日期：2026 年 9 月 18 日 · 适用版本：Four-leaf Clover Authenticator Chrome 扩展程序
1. 谁负责此扩展程序
Four-leaf Clover Authenticator 由 Chrome Web Store 中列出的开发者发布。开发者联系邮箱：iskfcu@gmail.com。本扩展程序不运营用于接收验证器账户数据的开发者服务器。
2. 扩展程序在本机处理的数据
• 验证器账户：账户标签、TOTP/HOTP 密钥及生成验证码所需的参数，保存在当前 Chrome 配置文件的扩展存储中；账户记录使用设备密钥加密。验证码在本机生成。
• 设置与网站自动化规则：主题、语言、账户排序、用户明确保存的网站来源、字段选择器和规则状态，保存在本机。用户选择保存的固定填写值在设备端加密。
• 当前标签页地址：弹窗打开时读取当前标签页地址，并仅在本机用于匹配账户；不会将该地址上传，也不保存验证码复制历史。
• 本地备份：最近的账户备份保存在浏览器本地 IndexedDB 中。导出的文件只写入用户选择的下载位置；启用密码保护的导出文件使用用户在导出时设置的密码加密。
• 会话数据：解锁期间使用的临时密钥保存在 Chrome 会话存储中，不作为跨设备同步数据。
3. 页面访问与自动填充
默认情况下，扩展程序不会持续访问任意网页。只有用户主动创建网站规则并向 Chrome 授予相应网站访问权限后，扩展程序才会在该网站运行本地页面辅助脚本，定位用户绑定的字段并执行用户配置的验证码或表单填写操作。自动登录的点击动作仅在用户配置并触发时短暂使用 Chrome 调试接口，随后立即断开。扩展程序不会读取 Cookie，也不会把页面内容、验证码或填写值发送给开发者服务器。目标网站接收用户提交的信息后，将按其自身的隐私政策处理。
4. 可选的 Chrome Sync
跨设备同步默认关闭。用户必须主动开启密码保护和同步后，扩展程序才会把加密后的账户记录及必要的保险库元数据交给 Chrome Sync，由 Google 账号在设备间同步。开发者不会获得同步内容。用户可在设置中关闭同步；扩展程序会请求移除其写入的同步记录。Chrome Sync 的服务处理另受 Google 隐私政策约束。
5. 时间校验的第三方请求
验证码窗口可在打开时检查设备时钟，并在缓存过期后尝试请求公开时间服务。只有用户此前授予时间校验所需的可选网站权限后，这些请求才会成功发送；用户也可从设置中主动发起检测。请求目标为：
• time.akamai.com
• cloudflare.com
• timeapi.io
这些服务会收到正常 HTTPS 请求所必需的网络信息，例如 IP 地址、请求时间和浏览器网络头信息。扩展程序不会在时间请求中加入账户名称、密钥、验证码、网站规则或表单值。第三方服务如何保留网络日志，由相应服务提供方的政策决定。
6. 数据共享、广告与分析
开发者不出售或出租扩展程序内的数据，不将这些数据用于广告或跨站追踪，也不运营接收账户数据的服务器。除用户选择的 Chrome Sync 外，扩展程序只会为时间校验向上文列出的时间服务发送普通网络请求；不会把验证器账户数据共享给这些服务。
7. 保存期限与删除
本机数据会保留在当前 Chrome 配置文件中，直到用户在扩展程序内删除相应账户、规则或设置，或清除扩展程序数据。关闭同步时，扩展程序会删除其写入 Chrome Sync 的同步副本。卸载前如需立即删除同步副本，请先在扩展程序设置中关闭同步并确认清理完成；Google 对 Chrome Sync 数据的保留和删除另受 Google 政策控制。
8. 安全
数据默认保留在本机；账户记录和本地备份使用设备密钥加密。密码保护会为保险库增加由用户密码保护的密钥封装，并允许安全同步。任何本机扩展都无法防御用户设备上已运行且取得同等用户权限的恶意软件；请妥善保管设备、扩展密码和恢复码，并谨慎处理明文导出文件。
9. Chrome Web Store Limited Use
Four-leaf Clover Authenticator 对用户数据的使用限于提供 TOTP/HOTP 生成、用户主动配置的网站填充、备份和用户主动开启的加密同步。扩展程序不会将数据用于广告、信用评估、出售或与无关目的共享。数据不用于超出扩展程序单一明确功能范围的用途。
10. 联系开发者
隐私问题或数据请求：iskfcu@gmail.com。
Four-leaf Clover Authenticator Privacy Policy
Effective date: September 18, 2026 · Applies to the Four-leaf Clover Authenticator Chrome extension.
1. Controller
Four-leaf Clover Authenticator is published by the developer named on its Chrome Web Store listing. Developer contact: iskfcu@gmail.com. The extension does not operate a developer server that receives authenticator account data.
2. Data processed locally
• Authenticator accounts: account labels, TOTP/HOTP secrets, and parameters needed to generate codes are stored in the current Chrome profile's extension storage. Account records are encrypted with a device key; codes are generated locally.
• Settings and website rules: preferences, saved site origins, field selectors, and rule states are stored locally. User-saved fixed fill values are encrypted on the device.
• Current tab address: when the popup opens, it reads the current tab's address and uses it locally to match accounts. The address is not uploaded or retained as browsing history.
• Local backups: recent account backups are held in local browser IndexedDB. Exported files go to a location chosen by the user; password-protected exports use the password chosen during export.
• Session data: temporary unlock keys are held in Chrome session storage and are not synced between devices.
3. Website access and autofill
The extension does not continuously access arbitrary websites by default. Only after a user creates a site rule and grants Chrome access to that site does the extension run its local page helper there, locate user-bound fields, and perform configured code or form filling. The automatic-login click uses Chrome's debugger interface only when the user has configured and triggered that action, and detaches immediately afterward. The extension does not read cookies or send page contents, codes, or fill values to a developer server. The destination website handles submitted information under its own privacy policy.
4. Optional Chrome Sync
Cross-device sync is off by default. Only after the user enables password protection and sync does the extension send encrypted account records and necessary vault metadata to Chrome Sync for replication through the user's Google Account. The developer cannot access the synced contents. Turning sync off asks the extension to remove its sync records. Google’s privacy policy governs Google’s handling of Chrome Sync data.
5. Third-party time requests
The popup can check the device clock and try public time providers when its cache expires. These requests can succeed only after the user has granted the optional time-check host permissions; the user can also request a check from Settings. The endpoints are time.akamai.com, cloudflare.com, and timeapi.io. Providers receive ordinary HTTPS request information needed to serve the request, such as an IP address, request time, and browser network headers. The extension does not include account names, secrets, codes, site rules, or form values. Each provider's policy governs its network-log retention.
6. Sharing, ads, and analytics
The developer does not sell or rent extension data, use it for advertising or cross-site tracking, or operate a server that receives account data. Other than user-selected Chrome Sync, the extension makes ordinary network requests only to the time providers listed above; it does not share authenticator account data with those providers.
7. Retention and deletion
Local data remains in the Chrome profile until the user deletes the relevant account, rule, or setting in the extension, or clears extension data. Turning sync off removes the extension's sync records. To remove a synced copy before uninstalling, turn sync off in Settings and verify cleanup first; Google's retention and deletion of Chrome Sync data is governed by Google's policies.
8. Security
Data stays local by default; account records and local backups are encrypted with a device key. Password protection adds a password-wrapped vault key and permits encrypted sync. No local extension can defend against malware already running with the same user privileges. Secure your device, extension password, and recovery code, and handle plaintext exports carefully.
9. Chrome Web Store Limited Use
Four-leaf Clover Authenticator uses user data only to provide TOTP/HOTP generation, user-configured website autofill, backups, and encrypted sync explicitly enabled by the user. It does not use data for advertising, credit decisions, sale, or unrelated sharing, or for purposes outside the extension's single stated purpose.
10. Contact
Privacy questions or data requests: iskfcu@gmail.com.