爽动隐私政策

更新日期:2026 年 11 月 19 日。运营者:Hang Su。联系邮箱:shawn.suhang@gmail.com。

爽动帮助你查看健康和运动记录,并可选择使用跑友排行。在 Oura 服务配置完成并显示可用入口后,还可以独立授权读取原始睡眠评分。首发免费、无内购,仅提供通过 Apple 登录社交账号。健康和运动的本机展示不要求创建社交账号。

1. Apple 健康与本机数据

经你授权,爽动读取 Apple 健康中的睡眠、心率、HRV、静息心率、血氧、呼吸率、腕温、体重、最大摄氧量、步数,以及运动时间、距离、活动能量、步幅、功率、步频和路线等记录,用于展示、历史查询和统计。你可以选择允许的类别,也可以在系统设置中撤回读取权限。爽动不向 Apple 健康写入记录。

除你主动开启的跑量分享字段外,这些健康记录在设备上处理。心率、睡眠分期和运动路线不上传至爽动社交服务器。运动详情的本机缓存受到 iOS 文件保护并排除系统备份。地图底图通过 Apple 的地图服务提供,受 Apple 对其服务的隐私规则约束。

2. 登录、昵称、头像与社交关系

使用 Apple 登录时,我们接收用于验证身份的授权信息,以及 Apple 在你允许时提供的姓名。我们保存账号标识、昵称、会话信息和加密的 Apple 授权凭据,支持登录与删除账号;首发不请求 Apple 邮箱。

登录社交功能后,昵称及你选择的个人头像会同步到爽动服务器,无论跑量分享是否开启。头像在本机裁剪并重新编码后,仅上传缩略图,不保留原照片的定位元数据。你可以修改昵称、恢复默认头像或删除社交账号。恢复默认头像后,下次成功同步会移除服务器头像。

我们保存你主动建立的好友关系、群组名称、成员关系和邀请信息。App 不读取你手机的通讯录或微信好友列表。公开邀请网页仅显示通用邀请信息;登录后的 App 会按屏蔽关系检查可见性,再显示邀请人的昵称或群组名称。请只向希望邀请的人分享链接。

3. 自愿开启跑量分享

跑量分享默认关闭。开启后,我们会上传真实跑步记录的记录标识、开始时间、距离和室内/户外标记,用于好友及群组排行。分享开启时,排行会展示昵称、头像和汇总跑量;不会向排行上传心率、睡眠或路线,也不会上传示例数据。

关闭跑量分享会删除在线数据库中已经分享的跑步记录,并停止后续跑步上传;账号资料和好友关系仍保留。当 Apple 健康提供明确的运动删除通知时,爽动会在本机排队,并在同一账号开启分享且成功联网同步时删除对应服务器记录。系统后台投递和删除通知的可用性可能受权限、设备状态及系统保留影响,不能保证即时或覆盖所有历史删除;你仍可关闭分享删除全部已分享跑步,或删除社交账号。

4. 可选的 Oura 连接

连接 Oura 需要你在 Oura 的页面独立授权。爽动请求 daily 权限,经服务器获取每日睡眠接口,并将日期和原始睡眠评分转发到你的设备。接口响应在请求过程中处理;评分不写入爽动服务器数据库,不用于好友排行,不被估算或伪造。

为维持连接,Oura 授权凭据加密保存并与爽动账号关联。你可以在爽动断开连接,删除在线连接凭据;服务器同时尝试向 Oura 撤销授权。如果网络故障导致上游撤销未完成,你也可以在 Oura 的应用管理中撤销授权。Oura 自己保存的原始数据由 Oura 管理。

5. 网络安全、服务商与用途

服务器处理连接 IP 地址并在内存中保留限流记录,用于防止接口滥用。目前这些内存记录在进程重启或容量清理时移除;不保证请求完成后立即清除。我们不将这些信息用于广告定位。官网及接口由腾讯云 Lighthouse 的中国香港和中国广州入口提供服务。主域名默认入口在香港;DNS 服务识别为“境内”线路的查询使用广州入口,www 子域名使用广州入口。DNS 判断受解析来源等因素影响,不保证与访问者实际所在地区完全一致。经广州入口的接口请求会在广州终止 HTTPS 连接,再经独立的 HTTPS 连接转发至香港处理,因此广州入口会在转发过程中处理连接 IP、请求内容和响应;其他接口请求由香港入口处理。社交应用服务和数据库仍位于香港。广州入口不设应用数据库、不缓存接口响应,关闭常规访问日志;严重运行错误日志可能包含连接 IP 或请求网址(包括查询参数)。香港反向代理访问日志用于安全与维护。上述运行日志按日轮换,保留最近 14 个轮换文件,并进行压缩;这不等于保证日志在 14 天内删除。Oura 授权回调路径不记录访问日志。

爽动不出售用户健康数据,不使用健康记录投放广告或进行跨 App 广告追踪。账号、头像、社交关系和跑量用于提供对应功能。服务涉及 Apple 身份验证和地图、可选 Oura 接口及服务器托管;各服务商按其职责处理必要信息。账号、头像、社交关系、共享跑量、举报与封锁记录存储于上述中国香港服务器。使用社交功能会直接或经广州入口将对应数据传输到中国香港;可通过支持邮箱咨询处理商及数据处理信息。

6. 保留、备份与删除

在线账号资料、社交关系和授权连接在你使用功能期间保留,直到你移除相应信息、断开连接或删除账号。跑步记录保留至关闭分享或删除账号。你可以在“社交”页面的账号菜单中选择“删除账号”并确认。成功删除会移除在线账号、头像、会话、身份绑定、好友关系、已分享跑步和连接凭据。你创建且仍有成员的群组会转交其他成员,空群组会删除。

服务器保留访问受限的本地数据库备份,按最近 7 次成功备份轮换;这不是“最多保留 7 天”的保证。已删除数据可能留在旧备份中,直到对应备份被轮换移除。备份用于服务恢复,不供日常功能访问。当前没有自动将历史删除请求重新应用到恢复备份的机制;恢复操作需要运营者在重新开放服务前核对并处理删除请求。

删除爽动社交账号不会删除 Apple 健康或 Oura 的原始记录,也不会自动删除设备上用于本机功能的头像或健康缓存。你可以恢复默认头像、在 App 内清理缓存(如该入口可用)或移除 App 删除本机文件。网络或第三方撤销服务失败时,账号删除可能未完成;请在 App 中重试,或通过上述支持邮箱联系我们。

7. 举报、屏蔽与人工审核

提交举报时,我们保存举报人账号、被举报用户或群组、类别、你的说明,以及提交时对应的昵称、头像或群名快照,用于调查和处理违规内容。举报不会公开给其他用户。只有有服务器管理权限的运营者可通过本地审核工具查看证据、记录处理原因、移除内容或限制社交账号。头像的大小和文件结构会检查,但不代表自动判断了图片内容;不良图片需要人工审核。

屏蔽关系保存在服务器,用于双方可见性保护。屏蔽名单只显示屏蔽时的昵称快照,不继续加载对方的新头像或昵称。解封不会自动恢复好友关系。删除账号会删除其屏蔽关系,移除举报中的活动账号关联,并清除该账号作为被举报目标时保存的昵称、头像快照、原目标标识及说明;该账号提交的举报说明也会清除。必要的分类、时间和人工处置审计记录仍单独保留。未处理举报在创建 180 天后定期清理;已处理举报及其审核记录在处理完毕 90 天后定期清理。人工移除内容的单向哈希值用于阻止相同内容再次上传,不保存原图片,也不与账号绑定。访问受限的备份仍按前述轮换规则保留。

8. 联系与更新

如需询问隐私、申请数据访问/删除或报告用户内容,请联系 shawn.suhang@gmail.com。我们会在此公布政策更新日期;实际新增的数据用途会在相应功能中向你说明。


PerkUp Privacy Policy

Updated: November 19, 2026. Operator: Hang Su. Contact: shawn.suhang@gmail.com.

PerkUp displays health and workout records, with optional social running leaderboards. Oura sleep scores require separate authorization and are available only when the service is configured and an available connection option is shown. The initial release is free, has no in-app purchases, and offers Sign in with Apple for social accounts. Local health and workout features do not require a social account.

1. Apple Health and on-device processing

With your permission, PerkUp reads sleep, heart rate, HRV, resting heart rate, blood oxygen, respiratory rate, wrist temperature, weight, VO₂ max, steps, workouts and related measurements such as time, distance, energy, stride, power, cadence and routes. These support display, history and statistics. You choose the permitted categories and can withdraw permission in system settings. PerkUp does not write records to Apple Health.

Except for running fields you explicitly choose to share, this health data is processed on your device. Heart rate, sleep stages and routes are not uploaded to PerkUp's social server. Local workout-detail caches use iOS file protection and are excluded from system backups. Apple provides map backgrounds under its own service privacy rules.

2. Sign-in, profile and social relationships

Apple sign-in supplies authorization information and, when you permit it, your name. We retain account identifiers, display name, session information and encrypted Apple authorization credentials for authentication and account deletion. The initial release does not request your Apple email address.

After social sign-in, your display name and chosen profile photo synchronize to PerkUp's server, even when running sharing is off. The app crops and re-encodes the image, uploads only a thumbnail, and does not retain the original photo's location metadata. You can edit your name, restore the default avatar or delete the social account. Restoring the default removes the server avatar on the next successful sync.

We retain friendships, group names, memberships and invitation information you create. We do not read your phone address book or WeChat friends. Public invitation pages show generic invitation information. The signed-in app checks blocking relationships before showing the inviter's display name or group name. Share invitations only with intended recipients.

3. Optional running sharing

Running sharing is off by default. If enabled, PerkUp uploads the record identifier, start time, distance and indoor/outdoor flag for actual runs. Friends and group leaderboards display your name, avatar and aggregated running totals while sharing is enabled. Heart rate, sleep, routes and demo records are not uploaded for these rankings.

Turning sharing off deletes shared runs from the live database and stops further run uploads; account profiles and social relationships remain. When Apple Health supplies an explicit workout deletion, PerkUp queues its identifier locally and removes the corresponding server record when the same account successfully synchronizes with sharing enabled. Background delivery and deletion availability depend on permissions, device state and system retention; immediate delivery or every historical deletion cannot be guaranteed. You can still turn sharing off to remove all shared runs, or delete your social account.

4. Optional Oura connection

You separately authorize Oura on Oura's website. PerkUp requests the daily scope, retrieves the daily sleep endpoint through its server, and relays dates and original sleep scores to your device. Responses are processed for the request; scores are not stored in the server database, used in rankings or estimated.

Encrypted Oura credentials are retained with your PerkUp account to maintain the connection. Disconnecting in PerkUp removes live connection credentials and attempts provider revocation. If network failure prevents revocation, revoke access in Oura's application settings. Oura manages the original data it stores.

5. Security, providers and purposes

The server processes connection IP addresses and retains rate-limiting records in memory to prevent abuse. Records are removed on process restart or capacity-based cleanup, rather than necessarily after each request. They are not used for advertising location targeting. The public website and API use Tencent Cloud Lighthouse entry points in Hong Kong and Guangzhou, mainland China. The apex domain defaults to Hong Kong; DNS queries classified by the DNS provider as the domestic (境内) line use Guangzhou, and the www subdomain uses Guangzhou. DNS classification depends on query source and other factors and may not match a visitor's physical location. For API requests that reach Guangzhou, incoming HTTPS connections terminate there and requests are forwarded over a separate HTTPS connection to Hong Kong. The Guangzhou entry point therefore processes connection IP addresses, request contents and responses in transit; other API requests are handled by the Hong Kong entry point. The social application service and database remain in Hong Kong. The Guangzhou entry point has no application database, does not cache API responses and has routine access logging disabled; critical operational error logs may include connection IP addresses or request URLs (including query parameters). Hong Kong reverse-proxy access logs support security and maintenance. These operational logs rotate daily and retain the latest 14 rotated files with compression; this is not a guarantee that every entry is deleted within 14 days. Access logging is disabled for the Oura authorization callback path.

PerkUp does not sell health data or use it for advertising or cross-app advertising tracking. Account data, photos, social relationships and shared runs enable their respective features. Apple authentication and maps, optional Oura APIs and server hosting process information needed for their roles. Account profiles, photos, social relationships, shared runs, reports and blocks are stored on that Hong Kong server. Using social features transfers the corresponding data to Hong Kong, either directly or through the Guangzhou entry point. Contact support for processor and data-handling details.

6. Retention, backups and deletion

Live account data, social relationships and connections remain while you use these features, until you remove the relevant information, disconnect or delete the account. Shared runs remain until sharing is disabled or the account is deleted. Use the account menu on the Social page to delete your account and confirm. A successful deletion removes the live account, avatar, sessions, identity bindings, friendships, shared runs and connection credentials. Groups with remaining members are transferred to another member; empty groups are deleted.

Restricted local database backups retain the latest seven successful snapshots; this is not a maximum retention promise of seven days. Deleted information may remain in older backups until rotation removes them. Backups are for service recovery, not routine feature access. There is currently no automatic mechanism to reapply historical deletion requests to a restored backup. Operators need to check and process deletion requests before reopening a restored service.

Deleting the social account does not erase original Apple Health or Oura records, or automatically remove local profile photos and health caches used by the app's local features. You can restore the default avatar, use any available in-app cache-clearing control, or remove the app to delete its local files. If network or provider revocation fails, account deletion may not complete; retry in the app or contact support.

7. Reports, blocks and human moderation

A report stores the reporter account, reported account or group, category, submitted explanation and a snapshot of the relevant display name, avatar or group name. These records support investigating and handling abuse and are not public. Authorized server operators can inspect evidence, record decisions, remove content or restrict social accounts using a local moderation tool. Avatar file size and structure are checked, but image subject matter is not automatically classified; harmful images require human review.

Blocking relationships are stored to protect visibility in both directions. A block list retains only the display-name snapshot from the time of blocking; it does not load new names or avatars. Unblocking does not restore friendship automatically. Deleting an account removes its blocks and live account references in reports. For reports targeting that account, saved profile-name/avatar snapshots, the original target identifier and explanations are cleared; explanations submitted by that account are also cleared. Necessary categories, timestamps and moderation audit records remain separately. Pending reports are periodically cleared after 180 days; resolved reports and their action history are cleared after 90 days. One-way hashes of manually removed content prevent identical reuploads without retaining the original image or an account association. Restricted backups follow the rotation policy above.

8. Contact and updates

For privacy questions, data access/deletion requests or user-content reports, contact shawn.suhang@gmail.com. Policy updates will show a revised date here, and new data uses will be explained in the relevant feature.