隐私政策
飞鸿 Fion · Android
| 项目 | 说明 |
|---|---|
| 日期 | 2026 年 11 月 21 日生效 |
| 应用 | Fion(飞鸿,Android 版) |
| 开发者 | HYPAI ORG |
| 邮箱 | support@hypai.org |
1. 适用范围与开发者主体
本隐私政策由 HYPAI ORG(下称「我们」)制定,适用于 Android 应用 Fion(飞鸿)(下称「飞鸿」)。飞鸿将你的 Android 手机新收到的短信与未接来电转发至你自行配置的 Bark 推送服务器。
安装飞鸿、授予系统权限或开启转发功能,即表示你已知悉本隐私政策所述的数据处理规则。飞鸿不需要也不提供账号注册功能。
2. 访问的个人及敏感数据与用途
飞鸿仅访问实现核心转发功能所必需的本机数据。
| 访问数据 | Android 权限 | 用途与限制 |
|---|---|---|
| 新短信的发件人号码、正文与接收时间 | RECEIVE_SMS | 生成并发送短信推送。飞鸿不读取历史短信收件箱。 |
| 未接来电的号码、来电时间、所属 SIM 标识与该号码当天未接次数 | READ_CALL_LOG | 生成并发送未接来电推送。飞鸿忽略已接与拨出通话。 |
| SIM 卡号码、运营商名称、卡槽序号与显示名称 | READ_PHONE_STATE、READ_PHONE_NUMBERS | 标明接收短信或未接来电的 SIM 卡。飞鸿不拨打、接听或管理通话。 |
飞鸿仅在你授予对应权限、开启转发开关且保存有效 Bark 配置后执行转发。若你撤销 READ_CALL_LOG 权限后再次授权,飞鸿可能补发撤权期间产生的未接来电。
HYPAI ORG 不为飞鸿运营任何后端服务器,不收集任何用户数据。我们不接收、访问、出售、出租或共享你的短信正文、通话记录、SIM 卡信息或设备标识符。飞鸿不含第三方广告 SDK、统计分析、崩溃上报或自动版本检查。
3. 数据传输去向与第三方服务
飞鸿仅按你配置的投递路径向设备外部传输推送数据。
- 你配置的 Bark 服务器。飞鸿通过 HTTPS(
POST /push)将每条推送发往你在「设置 › Bark 推送设置」填写的服务器。若该服务器返回 HTTP 重定向,飞鸿会跟随跳转,请求可能到达该服务器指定的其他主机。 - 默认服务器与自建服务器。默认服务器
api.day.app由 Bark 项目独立运营,与 HYPAI ORG 无关。自建服务器由你自己或你选定的托管方运营。 - Apple 推送通知服务(APNs)。Bark 服务器通过 Apple Inc. 运营的 APNs 将通知送达你的 Apple 设备。
推送离开你的手机后,其处理、日志记录、保留与删除均由对应 Bark 服务器运营方及 Apple Inc. 的隐私政策约束。HYPAI ORG 无法控制第三方服务器,也无法访问或删除其上的数据。转发敏感内容前,请先查阅所用 Bark 服务器及 Apple Inc. 的隐私政策。
4. 本机存储的数据
为保证转发与重试正常运行,飞鸿仅在你的 Android 手机本地保存以下数据。
- 应用设置。Bark 服务器地址、Device Key、可选 AES 加密密钥与加密参数、转发开关、推送模板、提示音、提醒级别、归档开关、应用语言与开机自启设置。
- 转发统计。已转发短信数、已转发未接来电数、失败次数、平均耗时,以及含 SIM 卡名称与运营商的分卡计数。
- 离线重试队列。因网络异常或服务器临时不可达而未发出的推送内容,包含渲染后的标题、正文、SIM 标签、时间戳与消息 ID。
- 内部运行状态。引导完成标记、最近处理的通话记录 ID 水位,以及本地生成的用于计算去重消息 ID 的密钥。
5. 数据安全措施
飞鸿在传输与本机存储两个环节采取以下保护措施。
- 传输加密。飞鸿向所配 Bark 服务器发送推送时强制使用 HTTPS。
- 可选端到端内容加密。配置 AES 密钥(支持 AES-128、AES-192 或 AES-256,以及 CBC、GCM 或 ECB 模式)后,飞鸿在推送离开手机前于本机加密通知内容(标题、正文、分组、提示音、提醒级别与归档标记)。
device_key、去重消息id及随机向量iv(使用 CBC 或 GCM 模式时)保持明文,用于 Bark 路由与客户端解密。只有持有该 AES 密钥的一方(通常为你的 Bark 应用)能解密通知内容。 - 本机沙盒隔离与禁止备份。全部本地数据仅存于 Android 系统隔离的应用私有存储中。飞鸿关闭了 Android 云备份(
allowBackup="false")与设备间数据迁移,本地设置、密钥、统计与离线重试队列不会经系统备份或换机迁移离开手机。
6. 数据保留与删除政策
- HYPAI ORG 服务器。保留期为零,我们不接收也不存储任何用户数据。
- 离线重试队列。队列中的推送在投递成功或被 Bark 服务器永久拒收后立即删除。超过 24 小时仍未发出的推送在重试时自动丢弃。
- 设置、统计与运行状态。保留于你的手机本地,直至你主动修改、重置、清除或卸载。
- 第三方服务器。已发出的推送在第三方服务器及 APNs 的保留与删除期限由对应服务运营方决定。
你可以随时按以下步骤删除全部本机数据。
- 在飞鸿「设置 › 重置统计数据」清空全部转发统计。
- 在 Android 系统设置中清除飞鸿的存储空间,或直接卸载飞鸿,以永久删除全部本机设置、密钥、统计、运行状态与离线重试队列。
7. 你的控制权与隐私权利
你始终对本机数据的访问与转发拥有直接控制权。
- 随时在飞鸿内关闭短信转发或未接来电转发。
- 随时在「系统设置 › 应用 › 飞鸿 › 权限」撤销任意运行时权限。
- 随时将默认服务器
api.day.app替换为自建 Bark 服务器,或启用 AES 加密后再转发敏感内容。
依据你所在司法辖区的适用法律(包括欧洲经济区、英国及美国加利福尼亚州的相关隐私法规),你可能享有知情、访问、限制处理、删除个人数据及撤回同意的权利。由于 HYPAI ORG 不在自有服务器存储你的任何数据,你可以直接通过上述本机操作行使删除权与撤回权,也可以联系我们提出隐私请求。
8. 儿童隐私
飞鸿不面向 13 周岁以下儿童(或你所在司法辖区规定的同等最低年龄以下未成年人)。HYPAI ORG 不会在知情的情况下收集儿童的个人数据。
9. 隐私政策变更
当飞鸿的数据处理方式或适用法律要求发生变化时,HYPAI ORG 可能更新本隐私政策。更新后的版本将在同一网址发布,并同步更新生效日期。
10. 联系我们
如对本隐私政策有任何疑问、合规咨询或隐私权利请求,请通过以下方式联系我们。
- 开发者主体。HYPAI ORG
- 隐私联系邮箱。support@hypai.org
如仅反馈不含个人隐私的技术缺陷,也可以在 https://github.com/HypaiORG/Fion/issues 提交 Issue。请勿在公开 Issue 中粘贴任何个人或敏感数据。
| Item | Details |
|---|---|
| Effective Date | November 21, 2026 |
| Application | Fion (Android) |
| Developer Entity | HYPAI ORG |
| Privacy Contact | support@hypai.org |
1. Scope and Developer Entity
This Privacy Policy explains how HYPAI ORG ("we", "us", or "our") handles personal and sensitive user data in the Android application Fion. Fion forwards incoming SMS messages and missed call notifications from your Android device to a Bark push server that you configure.
By installing Fion, granting runtime permissions, or enabling forwarding, you acknowledge the data practices described in this Privacy Policy. Fion does not require or support user account registration.
2. Personal and Sensitive Data Accessed
Fion accesses only the device data required to deliver its core forwarding functionality.
| Data | Permission | Purpose & Limit |
|---|---|---|
| Incoming SMS sender, message text, and timestamp | RECEIVE_SMS | Build and send the SMS push. Fion never reads your SMS inbox. |
| Missed call number, timestamp, SIM reference, and daily missed count | READ_CALL_LOG | Build and send the missed call push. Answered and outgoing calls are ignored. |
| SIM phone number, carrier, slot index, and display name | READ_PHONE_STATE, READ_PHONE_NUMBERS | Identify which SIM received the alert. Fion never places, answers, or manages calls. |
Fion accesses and forwards SMS messages and missed calls only after you grant the corresponding permissions, enable forwarding, and save a valid Bark server configuration. If you revoke READ_CALL_LOG and grant it again later, Fion may forward missed calls recorded during the period when access was revoked.
HYPAI ORG operates no backend server for Fion and collects no user data. We do not receive, access, sell, rent, or share your SMS content, call logs, SIM details, or device identifiers. Fion includes no third-party advertising SDKs, analytics trackers, crash reporting tools, or automatic update checks.
3. Data Transmission and Third-Party Services
Fion transmits notification data outside your device only through the delivery path you configure.
- User-Configured Bark Server. Fion sends each push notification over HTTPS (
POST /push) to the server entered inSettings › Bark push settings. If that server returns an HTTP redirect, Fion follows the redirect, which may route the request to another host chosen by that server. - Default and Self-Hosted Servers. The default server
api.day.appis operated independently by the Bark project, not by HYPAI ORG. Any self-hosted Bark server is operated by you or your chosen host. - Apple Push Notification service (APNs). The Bark server relays the notification to your Apple devices through APNs, operated by Apple Inc.
Once a push notification leaves your device, its handling, logging, retention, and deletion are governed by the operator of your chosen Bark server and Apple Inc. HYPAI ORG has no control over third-party servers and cannot access or delete data stored on them. Review the privacy policies of your Bark server operator and Apple Inc. before transmitting sensitive content.
4. Data Stored on Your Device
Fion stores the following data solely on your Android device to operate reliably.
- Application settings. Your Bark server address, Device Key, optional AES encryption key and cipher settings, forwarding toggles, push templates, notification sound, notification level, archive preference, language, and boot auto-start preference.
- Forwarding statistics. Total forwarded SMS count, missed call count, failed delivery count, average delivery latency, and per-SIM delivery counts with SIM display name and carrier.
- Offline retry queue. Rendered push title, body, SIM label, timestamp, and message ID for notifications that fail temporarily due to network or server errors.
- Internal runtime state. Onboarding completion flag, the last processed call-log record ID watermark, and a locally generated secret used to compute deduplication message IDs.
5. Data Security
We apply technical safeguards in transit and on your device to protect sensitive user data.
- Encryption in transit. Fion enforces HTTPS when connecting to the configured Bark server.
- Optional end-to-end payload encryption. When you configure an AES encryption key (AES-128, AES-192, or AES-256 in CBC, GCM, or ECB mode), Fion encrypts the notification payload (title, body, group, sound, notification level, and archive flag) on your device before transmission. The
device_key, deduplication messageid, and initialization vectoriv(when used by CBC or GCM) remain unencrypted so Bark can route and decrypt the notification. Only a party holding your AES key, normally your Bark app, can decrypt the payload. - On-device isolation. All local data is stored exclusively inside Fion's Android private app storage, isolated by the operating system. Android cloud backup (
allowBackup="false") and device-to-device data transfer are disabled so settings, keys, statistics, and queued notifications do not leave your device through system backup or migration.
6. Data Retention and Deletion
- HYPAI ORG servers. Zero retention, because HYPAI ORG receives no user data.
- Offline retry queue. Queued notifications are deleted immediately upon successful delivery or permanent rejection by the Bark server. Undelivered items older than 24 hours are discarded automatically during retry.
- Settings, statistics, and runtime state. Retained on your device until you change, reset, clear, or remove them.
- Third-party servers. Retention and deletion of delivered pushes depend on your Bark server operator and Apple Inc.
You can delete your local data at any time using the following steps.
- Reset forwarding statistics in Fion under
Settings › Reset statistics. - Delete all locally stored settings, keys, statistics, runtime state, and queued notifications by clearing Fion's app storage in Android settings or uninstalling Fion.
7. Your Controls and Privacy Rights
You retain direct control over data access and forwarding at all times.
- Disable SMS forwarding or missed call forwarding inside Fion at any time.
- Revoke any runtime permission in
Android Settings › Apps › Fion › Permissions. - Replace the default server
api.day.appwith a self-hosted Bark server or enable AES encryption before forwarding sensitive messages.
Depending on your jurisdiction, including the European Economic Area, the United Kingdom, and California, you may have rights to know, access, restrict, or delete personal data and to withdraw consent. Because HYPAI ORG stores no user data on its own servers, you can exercise deletion and withdrawal directly on your device using the controls above, or contact us with any privacy request.
8. Children's Privacy
Fion is not directed to children under 13 years of age, or the equivalent minimum age in your jurisdiction. HYPAI ORG does not knowingly collect personal data from children.
9. Changes to This Privacy Policy
HYPAI ORG may update this Privacy Policy when Fion's data practices or applicable legal requirements change. Any update will be published at the same web address with a revised effective date.
10. Contact Us
For privacy questions, compliance inquiries, or requests regarding this Privacy Policy, contact HYPAI ORG directly.
- Developer Entity. HYPAI ORG
- Privacy Contact Email. support@hypai.org
For non-confidential technical bug reports only, you may also open an issue at https://github.com/HypaiORG/Fion/issues. Do not post personal or sensitive data in public issue trackers.