Appause 围绕一个承诺构建：你的分组、冷却设置和使用统计永远不会离开你的设备。唯一的例外是你主动发起的 Pro 激活和反馈，下文会写清楚它们发送什么。
本文说明我们收集什么、不收集什么，以及应用用到的权限。它为非技术读者而写；
如有疑问，可在项目仓库提交 Issue。
简体中文
我们收集什么
几乎没有。 Appause 不会收集或上传你的个人信息。你的应用分组、冷却时间、使用统计都仅保存在本机，绝不会离开你的设备。
- 没有账号、没有登录、没有注册。
- 应用在日常使用中不进行任何网络请求——没有分析统计、没有崩溃上报、没有广告，也没有任何第三方 SDK。
- 联网只出现在三种由你发起的场景：开始 Pro 试用、兑换授权码、发送反馈。开始试用或兑换时会发送一个「设备指纹」（本机密钥的 SHA-256 哈希）到激活服务器；服务器返回一张经过签名的许可证令牌，令牌在你的设备上本地校验，之后完全离线可用。服务器会保存这个指纹，以及开始试用或兑换的时间、到期时间和授权状态，用来保证每台设备只能试用一次、一个授权码最多绑定 3 台设备。指纹由 Appause 在本机生成，不包含姓名、手机号或硬件序列号，但在 Appause 卸载前保持不变，所以它是一个匿名的设备标识。服务器收不到你的分组、统计或你用了哪些应用。不会上传任何浏览记录、消息或使用行为。
- 反馈只有你主动选择时才会发送（设置 → 反馈），应用不会自动上传。发送前会展示留言、可选联系方式、设备/版本信息和诊断快照；诊断可能包含服务与权限状态、最近的前台应用和拦截状态、分组名称及应用包名，但不包含屏幕内容、聊天记录、账号信息或按时间排列的使用历史。你可以通过 Appause、系统邮件或预填的 GitHub Issue 发送同一份报告。
- 你的所有配置（应用分组、冷却时间、使用统计）都仅保存在本机的数据库（Room）和偏好存储（DataStore）中。
无障碍服务（AccessibilityService）的用途
Appause 使用系统的 AccessibilityService，仅用于检测当前前台运行的是哪个应用——通过读取其包名实现。
canRetrieveWindowContent 已设为 false。我们不读取你的屏幕内容，不截图，也不记录你输入或看到的信息。- 我们仅用包名来判断是否要为你配置的分组显示暂停界面。
- Appause 会自动排除自身、系统桌面和系统界面，不会拦截它们。
这是一个无障碍 / 习惯养成功能，不是监控或安全工具。
权限说明
| 权限 | 用途 |
|---|
| AccessibilityService | 如上所述，通过包名检测前台应用。 |
| 前台服务 (Foreground Service) | 在设备使用期间保持前台应用检测持续运行。 |
| POST_NOTIFICATIONS（Android 13+） | 显示常驻的「检测中」通知。 |
| INTERNET（联网） | 仅用于开始 Pro 试用、兑换授权码和发送反馈。日常使用不会联网，其余功能完全离线。 |
你对数据的控制权
- 你的分组、冷却设置和统计都在你的设备上。清除应用数据或卸载应用会永久删除这些内容。
- 如果你开始过试用或兑换过授权码，上面说的匿名授权记录会保留在激活服务器上，卸载应用不会删除它。
- 你可以随时在应用内查看或删除任意分组。
儿童
Appause 不面向儿童，也不会有意收集任何人的个人信息。除了你主动开始试用或兑换时留下的匿名授权记录，以及你主动发送的反馈，它不收集任何数据。
变更
本政策如有变更，更新版本将发布在仓库的 PRIVACY.md 与本页面。
联系方式
如有疑问，请在 GitHub 提交 Issue，或发送邮件至 rng2018520@gmail.com。
English
What we collect
Almost nothing. Appause does not collect or transmit your personal information. Your app groups, cooldowns, and usage stats are stored locally and never leave your device.
- There is no account, no login, and no registration.
- The app makes no network requests during normal use — no analytics, no crash reporters, no advertisements, and no third-party SDKs.
- The network is used in three situations, all of them things you start: starting the Pro trial, redeeming a code, and sending feedback. Starting a trial or redeeming a code sends a device fingerprint (a SHA-256 hash of an on-device key) to the activation server; the server returns a signed license token that is verified on your device and works offline afterwards. The server keeps that fingerprint together with the trial or redemption time, the expiry time, and the license status, so each device gets one trial and each code binds to at most 3 devices. The fingerprint is generated on your device and contains no name, phone number, or hardware serial, but it stays the same until Appause is uninstalled, so it is a pseudonymous device identifier. The server never receives your groups, stats, or which apps you use. It holds no browsing history, messages, or app usage.
- Feedback is sent only when you choose to (Settings → Feedback); the app never uploads it automatically. Before sending, the app shows your message, optional contact detail, device/app metadata, and a diagnostic snapshot. The snapshot may include service and permission state, recent foreground/interception state, configured group names, and package names. It does not include screen content, messages, account information, or a chronological usage history. You can send the displayed report through Appause, email, or a pre-filled GitHub issue.
- All configuration (your app groups, cooldowns, and usage stats) is stored locally in an on-device database (Room) and preferences store (DataStore).
How the Accessibility Service is used
Appause uses Android's AccessibilityService only to detect which app is currently in the foreground, by reading its package name.
canRetrieveWindowContent is set to false. We do not read your screen content, do not take screenshots, and do not record anything you type or see.- We only use the package name to decide whether to show the pause screen for a group you configured.
- Appause excludes itself, the system launcher, and system UI from interception.
This is an accessibility / habit-forming feature, not a monitoring or security tool.
Permissions
| Permission | Why it is needed |
|---|
| AccessibilityService | To detect the foreground app by package name (as described above). |
| Display over other apps | Optional compatibility fallback. Appause normally uses an accessibility overlay that does not need this permission. Enable it only if the pause screen does not appear on your device. |
| Foreground Service | To keep foreground-app detection running while the device is in use. |
| POST_NOTIFICATIONS (Android 13+) | To show the persistent "detection active" notification. |
| INTERNET | Only for starting the Pro trial, redeeming a license code, and feedback you explicitly choose to send through Appause. Not used during normal use. |
| Usage Access | Optional local foreground confirmation that reduces false triggers. No usage data leaves the device unless it is part of the diagnostic report displayed before user-initiated feedback. |
Your control over data
- Your groups, cooldowns, and stats live on your device. Clearing the app's data or uninstalling the app removes them permanently.
- If you started a trial or redeemed a code, the pseudonymous license record described above stays on the activation server; uninstalling does not remove it.
- You can review or delete any group at any time from within the app.
Children
Appause is not directed at children and does not knowingly collect personal information from anyone. Apart from the pseudonymous license record created when you start a trial or redeem a code, and feedback you choose to send, it collects no data.
Changes
If this policy changes, the updated version will be posted in PRIVACY.md and on this page.
Contact
Questions or concerns: open an issue on GitHub, or email rng2018520@gmail.com.