〔FULL/SET〕
ProductPrivacySupportYour data
PRIVACY POLICY

Your health history stays yours.

FULL/SET is designed as a local-first iPhone application. This policy explains what the app accesses, why it needs that access, where information is stored, and the choices available to you.

Effective August 3, 2026 · English policy

1. Who operates FULL/SET

FULL/SET is an independently developed fitness and personal health-data organization application operated by Junhao Huang. Privacy questions can be sent to privacy@junhao-h.com.

2. What FULL/SET accesses

Apple Health

With your permission, FULL/SET reads supported activity, workouts, steps, active energy, distance, heart rate, resting heart rate, heart-rate variability, and sleep data. If you separately grant write permission and choose a migration or synchronization action, FULL/SET can add eligible Fitbit workout, sleep, energy, distance, and available heart-rate records to Apple Health.

Google Health and Fitbit

When you choose to connect Fitbit, FULL/SET requests read-only Google Health access for:

  • activity and fitness sessions;
  • sleep sessions and available sleep stages;
  • available health measurements such as heart rate, resting heart rate, HRV, oxygen saturation, respiratory rate, sleep temperature derivations, and VO2 max;
  • paired-device settings used for device model, battery, and last-sync diagnostics.

Available fields vary by device, account, region, and service availability.

Information you add

You may add local workout photos, places, goals, language preferences, and manual records. Workout photos are re-encoded to remove original EXIF and location metadata before FULL/SET stores them.

3. How information is used

FULL/SET uses authorized data only to provide and improve features visible to you: a unified health timeline, workout and sleep detail, trends, recovery context, duplicate checks, local reports and exports, sync diagnostics, and optional user-authorized Apple Health write-back.

Google Limited Use. FULL/SET's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

FULL/SET does not sell health data, use it for advertising, provide it to data brokers, or use it for unrelated profiling or eligibility decisions.

4. Where information is stored

FULL/SET does not currently operate a developer-controlled health-data server or FULL/SET cloud account. Supported health records, derived summaries, user-added information, and synchronization state are stored on your iPhone. Google OAuth refresh tokens are stored in iOS Keychain. Local health files use iOS file protection. Short-lived Google access tokens are kept in memory while needed.

Apple Health remains the system repository for Apple Health data. Google and Fitbit remain the source services for their records.

5. When information leaves the app

FULL/SET communicates directly with Google's OAuth and Google Health API services when you authorize or refresh Fitbit data. The app communicates with Apple Health through HealthKit on your device. If you choose to share or export a report, iOS presents the system share interface and you decide the destination.

FULL/SET does not include a health-data advertising SDK or send health values to a developer-operated analytics service.

6. Retention, disconnection, and deletion

Imported Fitbit data remains in FULL/SET's protected local storage until you disconnect Fitbit and clear its local cache, delete the app, or use another applicable deletion control. Disconnecting removes the Google authorization token stored by FULL/SET, cached Fitbit health records, locally retained Fitbit archive records, and local Fitbit synchronization identifiers.

Disconnecting does not delete records from Google or Fitbit and does not delete copies already written to Apple Health. You manage those records in their respective services. You can separately revoke FULL/SET's Google access from your Google Account connections settings.

Deleting FULL/SET from your iPhone removes its application container according to iOS behavior. Apple Health records are managed separately in the Health app.

7. Your choices

  • Choose which Apple Health read and write permissions to grant.
  • Connect or disconnect Fitbit at any time.
  • Preview eligible Fitbit records before writing them to Apple Health.
  • Delete local photos, places, and manual records.
  • Export supported summaries under your control.
  • Revoke FULL/SET access in Google Account settings.

8. Security

FULL/SET minimizes requested permissions, uses read-only Google Health scopes, OAuth authorization code flow with PKCE, iOS Keychain for refresh tokens, and iOS file protection for local health files. No method of storage is risk-free, but the product is designed to avoid unnecessary server-side collection.

9. Children, medical use, and changes

FULL/SET is not directed to children under the minimum age required to manage the relevant Apple or Google account. It is a fitness and personal-data organization product, not a medical device and not a substitute for professional medical advice.

This policy may change when FULL/SET adds a new data source or processing feature. The effective date will be updated and material changes will be disclosed before the changed practice applies.

10. Contact

For privacy questions or deletion help, contact privacy@junhao-h.com. Please do not email OAuth tokens, screenshots containing detailed health values, or raw health exports.

〔FULL/SET〕

Fitness across devices. Built local-first for iPhone.

PrivacySupportData & disconnectionTerms

© 2026 FULL/SET. Apple Health and Fitbit are trademarks of their respective owners.