App privacy

Closed TestFlight beta, version 1.0 build 69. Updated October 13, 2026. This page describes the beta app. The website waitlist has a separate privacy notice.

FORGE records workouts, meals, activity, progression, journal entries and optional photos to help you track fitness and consistency. No FORGE account is required for the core app. Profile and contact information, workout and meal logs, journal entries, progress photos and optional profile selfies are stored in the app on your device. FORGE does not operate an account-based cloud sync service. Device backups and platform services are controlled by your Apple settings and Apple's policies.

If you grant Apple Health access, FORGE reads steps and active energy. It does not write HealthKit records in this build. You can manage permissions in Apple's Health settings. These readings support your activity progress and streaks.

Astra is optional. Before an AI request, FORGE asks permission to send the relevant fitness context or selected meal image. Astra sends your question, limited conversation history and structured workout/fitness context through FORGE's server to OpenAI. That context can include your goals, training schedule, targets, recent workouts and daily nutrition/activity summaries, including Health-derived steps when available. The structured context does not include your saved name, age, contact email or journal. Anything you type into a question is part of that question and is sent to the provider.

Meal-image requests send the image you choose after confirmation. Progress photos and profile selfies are not automatically sent to Astra. FORGE removes unneeded image metadata and applies image size/format limits before accepting meal uploads. Estimates are approximate and require your confirmation before becoming a saved meal.

The FORGE API processes request content in memory and does not maintain a database of your questions, workouts or images. The hosting platform may process technical request information such as IP address, route, timing and status. OpenAI requests use store:false. Standard API abuse-monitoring logs may still be retained by OpenAI, generally for up to 30 days under its standard policy; exceptions can apply. Clearing FORGE's local data does not delete provider or platform logs. See OpenAI data controls.

Astra access codes are stored in the iOS Keychain. The server verifies their digests; your access code is not included in the model's fitness context. The OpenAI API key stays on the server and is not included in the app.

FORGE includes no advertising or cross-app tracking SDK in this build. The optional marketing checkbox is unchecked by default. Your optional email and preference remain local in this beta; entering them does not send an email or subscribe you to a list.

You can export your local records and import a backup, manage individual records, or reset local data from More. Private media is held separately from JSON records; check the export screen for its current scope before relying on a backup. Remove the separate Astra access code using the native lock control. When storage is unavailable, FORGE reports failed writes; restore access and retry before assuming a change was saved.

Apple handles TestFlight participation, installs, diagnostics and feedback under its policies. If you submit beta feedback or a screenshot, the developer can receive the information you choose to send. Contact the beta administrator through your invitation or TestFlight feedback for support and data questions. Use TestFlight’s Send Beta Feedback or the administrator contact in your beta invitation for privacy questions.