隐私政策
本政策适用于 Footprint 足迹 iPhone App 及其内建识别服务。开发者联系邮箱：tinuv.yang@gmail.com。
你的日常记录
当前发行版的运动、饮食、贴纸和能量记录保存在设备上，不作为个人记录库上传到我们的服务器。小组件通过设备上的共享容器读取必要摘要。设备备份和 Apple 服务的数据处理由你的系统设置及 Apple 政策决定。
健康与路线
经你授权后，App 从 Apple 健康读取运动、能量和相关路线，用来展示训练、能量变化和足迹。你可以在系统设置中管理权限；启用相关写入后，餐食热量与营养也可保存到 Apple 健康。我们不将健康数据用于广告定向，也不出售健康数据。
照片识别
主体提取与贴纸制作在设备上进行。热量与营养识别需要联网：照片、备注、用餐时间和语言会经我们的网关发送到所配置的模型供应商，以生成热量与营养估算。本版本只提供内建识别服务。
识别服务与供应商需要处理这些请求以生成结果；请勿提交无关的敏感信息。原始照片不作为个人饮食记录库上传。服务运营可能产生连接与故障日志，不应将在线识别理解为完全离线。
订阅与识别额度
购买由 Apple 处理，我们不会收到你的付款卡信息。App 使用 RevenueCat 管理订阅方案、购买和恢复。RevenueCat 会处理匿名用户标识、购买记录与凭证，以及设备和系统版本、语言、币种等必要信息，用于验证购买、恢复权益和订阅服务统计。我们不向 RevenueCat 发送运动、健康或食物照片。详见 RevenueCat 隐私政策。
为验证订阅和管理服务额度，网关处理经 Apple 签名的交易、原购买标识、App 生成的设备 UUID、首次使用时区和识别使用记录。设备 UUID 与识别会话保存在钥匙串中。免费次数按该设备标识记录，不会每日重置。
反馈与网站访问
你主动提交反馈或测试申请时，服务会处理所提交内容与联系方式。访问本网站及在线服务会产生提供服务所需的网络请求信息，例如 IP 地址和错误日志。本静态网站没有广告或第三方分析脚本。
管理与删除
你可以在 App 中删除记录或清空本机资料，并在系统中撤回健康、照片等权限。卸载 App 不一定删除钥匙串标识，也不会自动取消 Apple 订阅。有关服务端订阅验证或使用记录的访问、更正、删除请求，请通过上述邮箱联系；我们会在核验请求后处理，并说明因交易验证或安全要求需要保留的内容。
政策更新
如果数据处理方式发生变化，我们会更新本页日期和内容。
Privacy Policy
This policy covers the Footprint iPhone app and its built-in recognition service. Contact the developer at tinuv.yang@gmail.com.
Your records
The current release stores activity, meal, sticker and energy records on your device. They are not uploaded to our servers as a personal record library. Widgets read necessary summaries from an on-device shared container. Device backups and Apple services depend on your system settings and Apple's policies.
Health and routes
With your permission, the app reads workouts, energy and related routes from Apple Health to display activity and footprints. You can manage permissions in system settings. If you enable the relevant write permissions, meal calories and nutrients can also be saved to Apple Health. We do not use health data for advertising targeting or sell health data.
Photo recognition
Subject extraction and sticker creation run on your device. Calorie and nutrient recognition requires a connection: the photo, notes, meal time and language pass through our gateway to configured model providers to generate calorie and nutrient estimates. This version offers built-in recognition only.
The recognition service and provider process requests to generate results. Do not submit unrelated sensitive information. Original photos are not uploaded as a personal meal library. Operating the service may generate connection and error logs; online recognition is not an entirely offline feature.
Subscriptions and service usage
Apple processes payments; we do not receive your payment card details. The app uses RevenueCat to manage subscription plans, purchases and restoration. RevenueCat processes an anonymous user identifier, purchase records and receipts, and necessary technical information such as device and operating-system versions, language and currency to validate purchases, restore access and provide subscription analytics. We do not send workout or health records or food photos to RevenueCat. See the RevenueCat Privacy Policy.
To validate subscriptions and manage usage, the gateway processes Apple-signed transactions, original purchase identifiers, an app-generated device UUID, your initial time zone and recognition usage records. The device UUID and recognition session are stored in Keychain. Free usage is recorded against that device identifier and does not reset each day.
Feedback and this website
When you submit feedback or a testing request, we process the content and contact details you provide. Requests to this website and our services generate network information needed to operate them, such as IP addresses and error logs. This static website has no advertising or third-party analytics scripts.
Control and deletion
You can delete records or clear local data in the app and revoke permissions in system settings. Uninstalling the app may not remove Keychain identifiers and does not cancel an Apple subscription. Contact us to request access, correction or deletion of server-side subscription verification or usage records. We will verify the request and explain any records that must be retained for transaction verification or security.
Changes
We will update this page and its date when our data practices change.