Hello WOD Privacy Policy
输入“/”快速插入内容
Hello WOD Privacy Policy
Hello WOD Privacy Policy
用户7655用户76555月6日修改
Effective date:2026-04-07
Last updated:2026-04-07
Important: This Policy explains how Hello WOD (this “App” or “we”) handles your personal information. The App is developed and operated by an individual developer (not a company). Processing is primarily on-device, and any transmission follows a minimum-necessary approach. We do not sell your personal information and do not use it for third-party commercial sharing or cross-scenario marketing profiles without your consent.
If you do not agree, please do not use the relevant features; you may still use other parts of the App that do not rely on such processing, where available.
1.
Scope and definitions
1.1 This Policy applies when you download, install, or use this App and related services on an iOS device.
1.2 Personal information means information recorded electronically or otherwise that relates to an identified or identifiable natural person (excluding information that has been anonymized).
1.3 Sensitive personal information means personal information that, if leaked or misused, may easily harm human dignity or endanger personal or property safety. Where the App processes health-related data, such information may qualify as sensitive under applicable law; we will seek separate consent where required (e.g., through the system Health authorization flow) and follow principles of specified purpose, minimum necessity, and separate consent.
2.
Personal information controller (individual developer)
2.1 The controller of personal information for this App is the individual developer (not a company or other organization). Where the App processes personal information of users in the People’s Republic of China, the developer remains subject to applicable obligations under laws such as the Personal Information Protection Law of the PRC (PIPL) and must inform you as described in this Policy.
2.2 Contact
•
Email (privacy matters / rights requests):
2.3 If you are a minor, please read this Policy with a guardian and use the App only with their consent.
3.
What we collect and why
We follow lawful, legitimate, necessary, and good-faith principles, and take into account requirements under applicable laws (including PIPL and rules relevant to generative AI services) and Apple App Store expectations for privacy disclosure and permission transparency.
3.1 Core features and profile data (primarily local)
Visibility: By default, such data is visible only to you. If you use sharing features, you choose what to disclose.
3.2 Photos and OCR / text extraction (no upload of original images)
3.2.1 When you use camera / photo intelligence features:
•
On-device processing: We use iOS capabilities (e.g., Apple Vision–related frameworks) to extract text from images on your device for organizing workout content.
•
Commitment: Original image files are not uploaded to servers controlled by the developer as a category of personal information (if the developer operates no such server, no such upload exists). We do not provide original images to third parties for purposes beyond what is needed for the feature.
3.2.2 After extraction, plain text and necessary derived fields may be shown or structured in the App and stored primarily locally as part of your records.
3.3 Generative AI (large language models): minimum transmission
3.3.1 When you use features that structure WOD text via a generative model:
•
We may send text already extracted on-device or that you typed ( not original images ) over the network to a generative AI provider （Volcano Engine,ByteDance）engaged by the developer, solely to produce structured workout fields (movements, sets, loads, etc.) inside the App.
•
We do not transmit original images; content is limited to what is minimally necessary for that operation.
•
We apply de-identification, field trimming, and redaction where feasible, and require providers to process information only to provide that feature and not for individual profiling or unrelated marketing (subject to agreements and the provider’s public terms).
3.3.2 You may decline by not using the feature and use manual entry instead.
3.4 Health data (HealthKit)
3.4.1 If you authorize Health data (e.g., sleep, heart rate, HRV, active energy), we read only within the scope you authorize and use it on-device for readiness / recovery–related calculations and display, as described in the product.
3.4.2 By default we do not bulk-upload raw health data to developer-controlled servers; if this changes, we will update this Policy and obtain consent as required.
3.5 iCloud sync (your Apple ID private space)
3.5.1 If you enable iCloud sync, relevant training data (e.g., WODs, skill progress, PRs—see in-app description) is stored in your Apple ID’s iCloud private database for multi-device sync and backup.
3.5.2 The developer does not sell such data; iCloud is provided by Apple under Apple’s terms and privacy policy. You can manage iCloud and app permissions in system settings.
3.6 Device and diagnostic information
For security, crash diagnosis, and product improvement, we may collect device and diagnostic information that does not identify you alone, and use it in de-identified or aggregated form where feasible. We do not use this to build cross-app ad profiles or sell it to unrelated third parties.
4.
Core principles: local-first, minimum transfer, limited sharing
4.1 Local-first: Core data such as training logs, skill paths, and PRs are stored primarily on your device; health-related computation is performed on-device as stated in the product.
4.2 Minimum transfer: We transmit only the minimal text set needed for LLM-based structuring; we do not transmit original images.
4.3 Third-party sharing (principles): Except as below, we do not provide your personal information to third parties for their marketing, cross-scenario profiling, or independent commercial purposes: (1) where we have your separate consent; (2) where required by law or competent authorities; (3) processors (e.g., cloud or AI inference) under contracts that limit purpose, duration, and method, with reasonable oversight; (4) transfer of the App or rights where the successor continues to be bound by this Policy or obtains consent as required.