Consumer Health Data Privacy Policy

01Scope

This policy applies to consumer health data that AFORCE collects, receives, or processes through the AFORCE OS mobile application and related membership features. It supplements our general Privacy Policy; where the two differ with respect to consumer health data, this policy governs.

“Consumer health data” means personal information that is linked or reasonably linkable to a consumer and that identifies a consumer’s past, present, or future physical or mental health status, as defined under applicable law.

[Pending confirmation — counsel]: confirm which consumer-health-data laws apply based on the go-to-market plan and user geography (for example, Washington My Health My Data Act, Nevada SB 370, and comparable state statutes), and tailor the defined terms, rights, and timelines accordingly.

02Consumer Health Data We Collect

The AFORCE OS app is designed to work with wellness signals and logged behavior to present informational readiness and habit tracking. Categories of consumer health data may include:

• Hydration and intake you log in the app;
• Wellness signals derived from Apple Health / HealthKit that you choose to share, which may include heart rate variability (HRV), sleep duration, and resting heart rate;
• App-generated indicators computed from the above (for example, readiness and recovery indicators). These are informational estimates, not clinical measurements.

[Pending confirmation — product/engineering]: confirm the exact, current inventory of health-data fields the app collects or derives, and remove any category above that the shipping app does not actually process. This inventory must reflect verified product behavior, not marketing descriptions. The AFORCE marketing website (drinkaforce.com) does not itself collect consumer health data; the simulated values shown in website interface illustrations are sample data, not real user data.

03Sources of Consumer Health Data

• You — data you enter or log directly in the app;
• Apple Health / HealthKit — only the categories you explicitly authorize, on your device, through the operating system’s permission controls.

[Pending confirmation — product/engineering]: confirm all sources (device sensors, optional third-party integrations, etc.) actually used by the shipping app and list only those.

04Purposes for Collection and Use

Consumer health data is used to operate the features you request — for example, to display readiness and habit information, to surface suggested wellness actions, and to maintain your history within the app.

[Pending confirmation — counsel/product]: enumerate each specific purpose and confirm none fall outside what the consumer authorized. Confirm whether any processing occurs for analytics or product improvement and, if so, describe it and the controls available.

05Categories of Consumer Health Data Shared

[Pending confirmation — engineering/vendor review]: confirm whether any category of consumer health data is shared or disclosed to any third party, and if so, list each category. Do not state a category is or is not shared until verified against code, configuration, and executed vendor agreements.

Not sold; not used for advertising — [Pending verification before this statement is made public]: AFORCE intends to state that it does not sell consumer health data and does not use it for advertising or targeted advertising. This statement will be finalized and published only after code, configuration, and vendor review confirm it end-to-end for the app and its backend. (The marketing website itself loads no advertising, analytics, or session-replay trackers and transmits no health data to any advertising pixel; the app and its backend require separate confirmation.)

06Categories of Third Parties and Processors

[Pending confirmation — engineering/vendor review]: list the categories of processors that receive or handle consumer health data on AFORCE’s behalf (for example, cloud hosting, authentication, or infrastructure providers), and confirm each is bound by a data processing agreement limiting use to providing services to AFORCE. Do not name a processor until its role and contract are verified.

07Your Authorization and Consent

Where required by law, AFORCE will obtain your affirmative, opt-in consent before collecting or sharing consumer health data, separately from any general terms acceptance. Consent is not a condition of purchasing AFORCE products, and Apple Health / HealthKit access is optional.

[Pending confirmation — product/counsel]: confirm the in-app consent flow captures a durable record of consent (version, timestamp, and scope) and that separate authorization is obtained for any collection and any sharing, as applicable law requires.

08Apple Health / HealthKit Handling

If you choose to connect Apple Health, the AFORCE OS app requests access only to the specific data categories needed for the features you use, through Apple’s on-device permission controls. You can review and revoke this access at any time in the iOS Settings ’ Privacy & Security ’ Health controls, or within the app.

AFORCE handles HealthKit data in accordance with Apple’s requirements, including that HealthKit data is not used for advertising or other use-based data mining beyond providing health and fitness services, and is not disclosed to third parties for advertising or marketing.

[Pending confirmation — engineering]: confirm the app’s HealthKit entitlement usage, the exact categories requested, and full compliance with the applicable Apple Developer Program License Agreement and App Store Review Guidelines for HealthKit before this section is finalized.

09Retention

[Pending confirmation — engineering/counsel]: state the retention period(s) for each category of consumer health data, and the criteria used to determine them. Do not state a retention period until verified against actual data-lifecycle behavior.

10Access

Subject to applicable law, you may request to access the consumer health data AFORCE holds about you. See How to Exercise Your Rights.

11Deletion

Subject to applicable law, you may request deletion of your consumer health data. You may also delete data you logged, and disconnect Apple Health, within the app.

[Pending confirmation — engineering]: confirm the deletion mechanism, its scope (including any backups and processors), and completion timelines.

12Withdrawal of Consent

You may withdraw consent to the collection or sharing of consumer health data at any time. You can revoke Apple Health access through iOS controls, disconnect integrations in the app, or contact us using the details below. Withdrawal does not affect processing that already occurred before withdrawal.

13Appeals

Where applicable law provides a right to appeal a decision on a rights request, you may appeal by contacting us at the address below. We will respond within the timeframe required by the applicable law.

[Pending confirmation — counsel]: confirm appeal availability, method, and response deadlines for each applicable jurisdiction.

14How to Exercise Your Rights

To make an access, deletion, or consent-withdrawal request, or to appeal a decision, contact us using the details in the Contact section. We will verify your request as required by law and respond within the applicable timeframe. You may designate an authorized agent where the law permits.

[Pending confirmation — counsel/ops]: confirm the verification method, response deadlines, and whether a dedicated request form or toll-free method is required in any applicable jurisdiction.

15Changes to This Policy

We may update this policy from time to time. Material changes will be reflected by updating the version and effective date above and, where required by law, by providing additional notice. Your continued use of the Services after an update takes effect constitutes acceptance of the revised policy to the extent permitted by law.

16Contact Information