← Forge by FitDaily

Privacy Policy

Last updated: September 30, 2026

This Privacy Policy explains how Forge by FitDaily ("Forge," "we," "us," or "our") handles information when you use the Forge by FitDaily application and the website at fitdaily.app. Forge is built privacy-first: most of your personal data stays on your device. Please read this policy together with our Terms of Service.

The short version. New users can use Forge without an account, and app data is stored on the device by default. Account creation and sign-in are not offered in version 1.0, but people who were already signed in continue to sync their manually entered profile, food logs, workouts, and settings with their existing account. That account data is linked to its email address and account ID. Imported Apple Health and Health Connect records are excluded from sync. AI features ask for consent before the text and photos needed for that feature are sent through our backend to OpenAI. We never sell personal data, use it for third-party advertising, or send Apple Health or Health Connect data to AI providers.

1. Information We Collect

a. Data you create in the app

Profile details, food logs, workout history, manually entered weight entries, saved meals, preferences, personal records, and training settings are stored locally on your device. No account is required to use the core app. In the web version this data lives in browser storage; in the iOS and Android apps it lives in the app's private on-device storage. Account creation and sign-in are not offered in app version 1.0. If you were already signed in to a Forge account, your manual app data continues to sync with that account through our cloud database provider; the records are associated with your account email and account ID. A name entered in your profile is included in that synced profile. Device notification settings and imported Apple Health or Health Connect records are not backed up.

b. AI request content

When you use AI features, the text of your request is sent to the Forge backend, which forwards it to a third-party AI provider, currently OpenAI, to generate a result. This may include meal descriptions, workout parameters, goals, equipment, and progress summaries that you choose to submit. If you choose the optional nutrition-label photo feature after a barcode miss, the label image is sent to the same provider to read the serving size and nutrition facts. Forge does not save those label photos. Please do not submit medical records, government identifiers, or other sensitive information you do not want processed by an AI service. No data read from Apple Health or Health Connect is sent to AI providers.

c. Nutrition reference services

Food logging may use public nutrition references. Barcode lookup sends the barcode number to Open Food Facts to look up packaged-food nutrition. Some food estimation flows may use USDA FoodData Central context for reference nutrition. Barcode camera video is not recorded, saved, or transmitted; only the detected barcode number is used for lookup. A nutrition-label photo is processed only when you explicitly choose that fallback, is transmitted securely to the AI provider for that request, and is not saved by Forge.

d. Server logs and reliability data

To operate, secure, debug, and improve the Service, our backend records technical logs such as request type, status, latency, timestamps, item counts, and rate-limiting information. Security logs may include an IP address. AI debugging logs may include a short truncated preview of request text and nutrition-result summaries. Our hosting provider may also retain network/request metadata. These logs are not guaranteed to be anonymous. We use them only for operations, security, and quality improvement. We also count production AI requests by request type, and record how many AI model calls and tokens each used, without a per-user identifier and without any request text, to monitor service usage and cost. These operational logs and aggregate counts are separate from optional in-app usage analytics.

e. Email address

For existing Forge cloud-backup accounts, we process the account email address to authenticate the account and the account ID to associate synced records with it. Account creation and sign-in are not offered in app version 1.0. If you join a waitlist, newsletter, beta list, or contact support, we use the email address and message you provide to respond or send product updates. You can unsubscribe from marketing emails at any time.

f. Analytics

We use Google Analytics on the website to understand aggregate page usage, such as page views and general device/browser type.

The app records first-party usage events only if you opt in under Profile - Settings - Usage analytics. These events may include app opened, onboarding completed, a meal was logged and by which method, or a workout was generated or completed. They use a persistent random app-generated identifier, so activity from the same installation can be associated across visits. This is pseudonymous data, not a guarantee of anonymity. Events carry counts or category labels, coarse acquisition information, and a device-language tag such as en-US so we can decide which translations users need. They do not include the food or drink you describe, weight or measurements, calorie or macro numbers, workout text, Health data, email, or precise location. You can withdraw consent by turning this setting off, and analytics remains off if your browser sends a Do Not Track signal.

g. Apple Health and Health Connect

The installed iOS app can connect to Apple Health if you grant permission. Forge may read body weight, sleep analysis, resting heart rate, step count, and active energy burned, and may write body weight entries that you log.

The installed Android app can connect to Health Connect if you grant permission. Forge may read body weight, sleep session, resting heart rate, step count, and active calories burned, and may write body weight entries.

Health data is used only in memory inside the app to display stats, personalize progress, and compute readiness context. Imported Health records are re-read from the system health store and are not saved in Forge's local browser storage or device backup. Health data is never uploaded to Forge servers, shared with third parties, sent to AI providers, or used for advertising or analytics. You can revoke Health permissions anytime in your device settings.

h. Microphone, camera, and notifications

If you tap Speak your meal, Forge requests microphone and speech-recognition access. Your operating system or browser speech service transcribes what you say, and Forge places the transcript in the meal field for you to review. Forge does not record or store the microphone audio. The reviewed transcript is handled like a typed AI request if you choose to estimate it.

If you use barcode scanning, Forge requests camera access to read product barcodes. The camera feed is not recorded or saved. If you choose the optional nutrition-label fallback, Forge may use your camera or selected photo to read the Nutrition Facts panel; that image is processed for the request and is not stored by Forge. If you enable reminders, Forge may request notification permission to remind you to log meals or check in.

i. Payment information

If we offer paid subscriptions or features, the price and applicable purchase terms will be shown before payment. Payments may be processed by the Apple App Store, Google Play, or another payment processor. We do not collect or store full payment card details.

2. How We Use Information

We do not use your on-device food, workout, weight, or Health data to train AI models, and we do not sell or rent your personal information.

3. How We Share Information

We share information only with service providers that help us run the Service and only as needed: OpenAI for AI requests; Supabase for optional account authentication, cloud backup, and first-party event storage; Open Food Facts for barcode lookups; USDA FoodData Central for nutrition context; Google Analytics for website analytics; Vercel for hosting and server logs; and an email service provider if you join a list or contact us. We may also disclose information if required by law or to protect rights, users, or the public. We do not sell personal information and do not share it for cross-context behavioral advertising.

4. Your Choices

5. Data Retention and Loss

On-device data stays on your device until you delete it, clear browser/app storage, or uninstall the app. If you enable cloud backup, your manual app data remains in that account until you reset it or delete the account. Clearing browser data, reinstalling the app, or switching devices may remove local-only data that was not backed up. Server logs are retained on a rolling basis for operations and security. Newsletter emails are retained until you unsubscribe or ask us to delete them.

Not storing a label photo in Forge does not mean our AI provider retains nothing. OpenAI's standard API abuse-monitoring logs may retain submitted content, including text and images, for up to 30 days, with exceptions described in its data controls documentation. We do not claim Zero Data Retention for Forge. Turning off usage analytics stops future optional events; it does not automatically erase historical events or operational logs. Contact support for help with a deletion request; we may need information that lets us locate the relevant records.

6. Security

We use reasonable safeguards, including HTTPS and keeping AI provider API keys on the server only. No storage or transmission method is perfectly secure, so we cannot guarantee absolute security.

7. Children's Privacy

Forge is intended only for adults age 18 or older and is not directed to children. We do not knowingly collect personal information from children.

8. Changes

We may update this policy from time to time. The latest version will be posted here with an updated date.

9. Contact

Questions or privacy requests: [email protected], or use the Forge by FitDaily support page.