Privacy Policy

Last Updated: March 25, 2026

The short version: Forge.OS is an offline-first app. Your workout data, nutrition logs, and personal records stay on your device. We don't have servers, we don't create accounts, and we don't track you.

Forge.OS ("the App") is developed by Heavy C Development Studio, LLC ("we", "us", "our"). This privacy policy explains how the App handles your data.

Data Storage

All data you enter into Forge.OS — workouts, templates, routines, training plans, exercises, nutrition logs, achievements, and preferences — is stored locally on your device using an on-device database. This data is never uploaded to our servers because we don't operate any servers.

If you delete the App, your data is permanently removed from your device.

Data We Do NOT Collect

We do not collect your name, email address, or any personal identifiers
We do not require account creation or sign-in
We do not track your location
We do not use analytics SDKs (no Firebase Analytics, no Amplitude, no Mixpanel)
We do not serve advertisements
We do not sell, share, or transfer your data to third parties for marketing purposes
We do not build user profiles or behavioral models

Device Permissions

The App may request the following device permissions, all of which are optional:

Health Data (iOS HealthKit / Android Health Connect)

What: Step count data only (read access)
Why: To display steps taken during your workout alongside your lifting stats
When: Only queried during an active workout session, for the duration of that session
Storage: Step counts are saved locally in your workout record
Sharing: Never sent off your device
You can deny this permission and the App functions normally without it

Camera

What: Camera access for image capture
Why: To scan nutrition labels (OCR) and to scan/generate QR codes for sharing templates and routines
When: Only activated when you explicitly open the nutrition scanner or QR scanner
Processing: Nutrition label text recognition is performed entirely on-device. No images are uploaded or sent to any server
You can deny this permission and use all other features normally

Music / Media Library (iOS)

What: Read-only access to currently playing track metadata (song title, artist, album name, album artwork)
Why: To record which song was playing when you hit a personal record (PR Anthem feature)
When: Only queried at the moment a new personal record is detected during a workout
Storage: Track metadata is saved locally in your PR record for display and sharing
Sharing: Only shared if you explicitly create and share a PR share card
You can deny this permission and PR detection still works — it just won't capture the song

Notifications

What: Permission to send local notifications
Why: Workout inactivity reminders, weekly summaries, and workout reminders
When: Scheduled locally on your device
Note: These are local notifications only. We do not use push notification services and cannot send you notifications remotely
You can deny this permission and all other features work normally

Third-Party Services

RevenueCat (Subscription Management)

The App uses RevenueCat to manage in-app purchases and subscriptions. When you make a purchase, restore a purchase, or when the App checks your subscription status, RevenueCat processes:

An anonymous user identifier (not linked to your name or email)
Purchase transaction data (what you bought, when, transaction ID)
Device type and OS version

RevenueCat does not have access to your workout data, nutrition logs, personal records, or any content you create in the App.

RevenueCat's privacy policy: revenuecat.com/privacy

Apple App Store / Google Play Store

Purchases are processed through Apple or Google's payment systems. We do not see or store your payment information. Apple and Google handle all payment processing under their respective privacy policies.

Google ML Kit (On-Device)

The nutrition label scanner uses Google ML Kit for text recognition. This processing happens entirely on your device. No images or text are sent to Google's servers.

QR Code & File Sharing

When you share a template, routine, or training plan via QR code or .Forge file, the data is encoded locally and shared directly with the recipient. No data passes through our servers. You control what is shared and with whom.

Share cards (PR cards, analytics snapshots) are generated as images on your device and sent through your device's native share sheet to the destination you choose.

Home Screen Widgets (iOS)

Widget data is stored in a shared app group container on your device (group.com.heavyc.forgeos) — a secure, sandboxed storage area that only the App and its widget extension can access. No widget data is sent off your device.

Children's Privacy

Forge.OS is not directed at children under 13. Since the App does not collect personal data from any user, no special provisions for children's data are necessary.

Data Export & Deletion

Export: You can export your data at any time via QR codes or .Forge files. Your data is yours.
Deletion: Deleting the App removes all data from your device. Since we don't store your data on any server, there is nothing for us to delete on our end.
Subscription data: If you need RevenueCat to delete your anonymous purchase history, contact us and we will submit a deletion request on your behalf.

Changes to This Policy

If we update this policy, we will update the "Last Updated" date above. Significant changes will be communicated through an App update or in-app notice.

Contact

If you have questions about this privacy policy or the App's data practices:

Email: [email protected]

Forge.OS is built on the principle that your training data belongs to you — not us, not advertisers, not the cloud. That's not a feature. It's the foundation.