PulseFit 运动健康 隐私政策
更新日期：2026年10月11日。统一 AI 服务说明适用于 1.1.10 及之后版本；旧版说明见下文。
PulseFit 运动健康是 ASUKANOVA 提供的运动、恢复与健康节奏管理应用，用于帮助用户查看每日恢复分、7 日运动记录、训练负荷趋势、睡眠恢复信号、AI 分析和 Apple Watch 同步信息。我们重视健康数据的敏感性，并以隐私优先原则设计产品。
当前版本支持两种使用方式：通过邮箱验证码创建的本机账号，或“仅此设备使用”模式。应用不提供云端健康账号，也不会将健康数据云同步。
我们处理的信息
- 健康指标：在用户授权后，应用可能读取 Apple Health / HealthKit 中的睡眠、心率、HRV、步数、活动能量、训练记录、正念分钟、呼吸、体重、体脂、BMI、血氧、血压、体温、血糖、营养和水分等用于恢复分析的健康数据。原始健康样本仍由 Apple 健康管理。
- 用户输入：用户在应用中填写的心情、压力、疲劳、疼痛、训练感受或其他日常记录内容，主要保存在本机。
- 本机账号与安全信息：邮箱地址用于注册验证；邮箱与本机密码哈希保存在设备 Keychain 中。密码不会以明文保存。1.1.10 及之后版本无需用户保存 AI Key，统一服务的密钥只保存在服务器端。
- 邮箱验证码信息：注册验证服务会接收邮箱地址、用途和验证码请求，用于发送和验证一次性验证码。验证码有效期为 15 分钟，成功验证后立即删除；用于限流和安全审计的请求日志保留不超过 24 小时。
- 粗略位置与天气：仅在用户允许位置权限并使用天气功能时，应用使用保留两位小数的粗略位置。WeatherKit、反向地理编码和本机天气缓存均使用该粗略位置，不保存精确住址。
- 应用设置与设备同步：隐私模式、Apple Watch 同步、状态提醒、通知偏好、多语言显示、本机历史、Widget App Group、Watch Connectivity 快照和其他应用配置主要保存在本机或用户自己的 iPhone 与 Apple Watch 之间。
使用目的
- 展示今日进度、每日恢复分、7 日运动记录、健康趋势和日常建议。
- 帮助用户理解睡眠、活动、训练负荷、HRV、压力和主观感受之间的关系。
- 在 iPhone 和 Apple Watch 上同步用户自己的健康管理体验。
- 提供用户主动开启的本地通知、状态智能提醒和恢复提示。
- 在用户主动请求注册时发送和验证邮箱一次性验证码。
- 维护应用安全、排查问题和回应支持请求。
HealthKit 数据
PulseFit 运动健康只会在用户明确授权后访问 Apple Health / HealthKit 数据。OTP 注册验证服务不会接收 HealthKit 原始数据。应用的健康摘要、趋势和分析结果主要保存在本机；用户可以随时在 iOS 设置或健康 App 中管理或撤销授权。HealthKit 数据不会用于广告，不会出售给第三方，也不会用于跨 App 或网站追踪。
本机存储与设备同步
当前版本不提供云端健康账号或健康数据云同步。用户设置、打卡记录、聊天记录、趋势历史、提醒配置、AI 配置、天气缓存和大部分健康摘要保存在本机。Widget App Group 和 Watch Connectivity 仅用于用户自己的设备之间展示应用数据。
AI 健康教练
1.1.10 及之后版本：AI 服务由 PulseFit 统一提供。只有在用户主动同意“AI 数据授权”后，整理后的健康摘要、近期趋势、用户记录和最近几轮对话才会通过 PulseFit 服务器转发给外部 AI 模型服务，用于生成运动、恢复、睡眠和生活方式建议。应用不会发送 HealthKit 原始样本。用户可随时关闭授权，停止后续发送并继续使用本机功能；旧版自定义服务的授权不会自动沿用。
PulseFit 转发服务不将健康摘要、对话或回答保存到数据库，也不记录请求正文。为控制滥用，服务处理请求 IP，并保存按日散列后的 IP 标识与请求计数；下一日收到请求时清理旧日计数。这些计数不包含健康数据。模型服务在生成回答时会处理收到的摘要和对话，因此云端 AI 不等同于完全离线处理。
1.1.9 及之前版本：用户需主动配置网关与 AI Key 并启用服务，摘要和最近对话直接发送到用户选择的网关，Key 保存在本机 Keychain。升级后的统一服务不再使用该本机 Key。所有 AI 建议仅供一般信息参考，不构成医疗诊断、治疗方案、处方建议或急救指导。
广告与追踪
PulseFit 运动健康不使用广告追踪，不使用健康数据进行广告定向，不出售健康数据或个人数据，不进行跨 App 或网站追踪。
宣传网站访问与下载按钮统计
访问 PulseFit 宣传网站时，服务器会记录请求 IP、浏览器的 User-Agent、请求时间、路径和响应状态，用于网站安全、故障排查与访问统计。主站使用独立访问日志；来源信息仅记录来源网站的 origin（协议、域名和端口），不记录来源页面的完整路径或查询参数。推广来源、媒介和活动代码仅从预设白名单中取值，不保存任意推广参数。
中文和英文宣传页还会统计 App Store 下载按钮的点击，包括页面语言、按钮位置（页首、主展示区或页尾）以及上述白名单渠道。这代表商店链接被点击，不代表应用已经下载或安装。网站统计不使用应用内的健康数据、健康摘要或对话，不设置跨站识别标记或持久追踪 Cookie。页面可能用 sessionStorage 在当前浏览器页面会话内保存白名单渠道；页面会话结束时由浏览器清除。浏览器开启 Do Not Track 或 Global Privacy Control 时，页面不发送新增下载点击统计，但服务器仍会产生必要的访问与安全日志。
点击商店链接后，Apple 会依照其隐私政策处理商店访问。未启用上述隐私信号且页面脚本可用时，链接会向 Apple 传递预设渠道参数，用于提供汇总的活动与下载统计；参数不包含健康数据或网站访客标识。
统计后台仅读取服务器上的访问日志，不把访问者 IP 发送给第三方地理位置查询服务，也不为此创建持久 IP 地理位置缓存。日志按日轮换，保留当前文件及最多 14 份历史轮换文件。IP 和请求信息可能识别或关联访问者，因此这些日志并非完全匿名；它们不用于广告定向或跨站追踪。
数据删除
用户可以在应用的“设置”中使用“删除本机账号和本机数据”。该入口会删除本机账号凭据、聊天记录、趋势历史、提醒、AI 配置、天气位置缓存、Widget 数据和 Apple Watch 快照；也会清除应用管理的其他本机健康摘要和记录。Apple 健康中的原始 HealthKit 数据不会被该入口删除，用户需要在 Apple 健康或系统设置中单独管理。删除应用也会移除应用沙盒中的数据。邮箱验证码成功验证后立即删除，限流日志不超过 24 小时。
儿童隐私
PulseFit 运动健康不是面向 13 岁以下儿童设计的应用。如果我们发现错误收集了儿童相关个人信息，将采取合理措施删除。
医疗免责声明
PulseFit 运动健康不是医疗器械，不用于诊断、治疗、缓解或预防任何疾病。如果你有疼痛、疾病、异常症状或紧急情况，请及时咨询医生或当地急救服务。
政策更新
我们可能会根据产品功能和法律要求更新本政策。更新时会注明日期；本次更新日期为 2026 年 10 月 11 日，补充了宣传网站访问与下载按钮统计说明。新版 AI 说明在使用 1.1.10 及之后版本时适用。
联系我们
隐私或支持相关问题，请联系：admin@asukanova.top
PulseFit Privacy Policy
Updated October 11, 2026. Managed AI details apply to version 1.1.10 and later; earlier versions are described below.
PulseFit is an exercise, recovery, and health-rhythm management app provided by ASUKANOVA. The current version supports either a locally stored account verified by email OTP or a device-only mode. It does not provide a cloud health account or cloud health-data synchronization.
Information We Process
- Health data: With permission, the app may read sleep, heart rate, HRV, steps, active energy, workouts, mindfulness, respiratory rate, body measurements, oxygen saturation, blood pressure, body temperature, blood glucose, nutrition, and hydration data from Apple Health / HealthKit for recovery analysis. Original samples remain managed by Apple Health.
- User entries: Mood, stress, fatigue, pain, training feedback, and other daily notes, primarily stored on the device.
- Local account and security data: Email is used for registration verification. Email and the local password hash are stored in the device Keychain. Passwords are not stored in plaintext. Version 1.1.10 and later require no user-supplied AI key; the managed service key stays on the server.
- Email OTP: The registration service receives an email address, purpose, and one-time code request. Codes expire after 15 minutes and are deleted after successful verification. Rate-limit and security logs are retained for no more than 24 hours.
- Approximate location and weather: When the user grants permission and uses weather features, the app uses a coarse location rounded to two decimal places. WeatherKit, reverse geocoding, and the local weather cache use that coarse location.
- Local settings and device sync: Privacy settings, notifications, history, Widget App Group data, Watch Connectivity snapshots, and other app configuration are primarily stored locally or transferred between the user’s own iPhone and Apple Watch.
How We Use Information
- To show daily progress, recovery scores, workout records, trends, and lifestyle suggestions.
- To relate sleep, activity, training load, HRV, stress, and subjective feedback.
- To provide the user’s own iPhone and Apple Watch experience.
- To send local notifications and registration OTP emails requested by the user.
- To protect, troubleshoot, and support the app.
HealthKit and AI
PulseFit accesses HealthKit only after explicit permission. The OTP service does not receive raw HealthKit data. In version 1.1.10 and later, after the user allows AI data use, prepared health summaries, recent trends, user notes, and recent conversation turns are sent through PulseFit servers to an external AI model service to generate suggestions. Raw HealthKit samples are not sent. Users can turn off AI consent to stop further sending and keep using on-device features. Consent for an earlier custom provider is not automatically reused.
The PulseFit relay does not save health summaries, conversations, or answers in its database or log request bodies. To limit abuse, it processes the request IP and stores a daily hashed IP identifier and request counts. Old daily counts are cleared when a request arrives on a later day. These counts contain no health data. The model service processes the submitted summaries and conversations to generate answers; cloud AI is not fully offline processing.
In version 1.1.9 and earlier, users explicitly configure and enable their own gateway and AI key. Summaries and recent conversations go directly to that gateway, and the key is saved in the device Keychain. The managed service no longer uses that local key after upgrading. AI output is general information, not medical diagnosis, treatment, prescription, or emergency guidance.
Local Storage, Deletion, and Tracking
The current version does not offer cloud health accounts or cloud health-data synchronization. Most app data stays on the device. “Delete local account and data” removes the local account credential, chats, trends, reminders, AI configuration, weather cache, widget data, and Watch snapshots. It does not delete original HealthKit data stored in Apple Health. PulseFit does not use advertising tracking, sell health data, or track users across apps or websites.
Promotional Website Visits and Download-Button Statistics
When you visit the PulseFit promotional website, the server records request IP addresses, browser User-Agent information, request times, paths, and response status codes for security, troubleshooting, and visit statistics. The main website uses a separate access log. Referrer information is limited to the referring website’s origin (scheme, domain, and port), without the referring page’s full path or query parameters. Promotion source, medium, and campaign codes are accepted only from predefined allowlists; arbitrary promotion parameters are not retained.
The Chinese and English promotional pages also count clicks on App Store download links, including the page language, button position (header, hero, or footer), and the allowlisted channel information above. A click does not establish that the app was downloaded or installed. These website statistics do not use in-app health data, health summaries, or conversations, and do not set cross-site identifiers or persistent tracking cookies. The page may use sessionStorage to retain allowlisted channel information within the current browser page session; the browser clears it when that page session ends. When Do Not Track or Global Privacy Control is enabled, the page does not send the new download-click events. Necessary server access and security logs still apply.
After you follow a store link, Apple handles the store visit under its own privacy policy. When the privacy signals above are not enabled and page scripts are available, the link passes predefined channel parameters to Apple for aggregate campaign and download statistics. These parameters contain no health data or website visitor identifier.
The statistics dashboard reads server access logs only. It does not send visitors’ IP addresses to third-party geolocation services or create a persistent IP geolocation cache for this purpose. Logs rotate daily, retaining the current file and up to 14 historical rotated files. IP addresses and request information may identify or link visits to a visitor, so these logs are not fully anonymous. They are not used for targeted advertising or cross-site tracking.
Contact
For privacy or support questions, contact admin@asukanova.top.