FORGEAlarmPrivacy Policy · Updated October 29, 2026
Forge works without an account, advertising, third-party analytics, or an app-operated cloud service. Workout progress is stored locally.
Forge does not send personal data to the developer, operate an account or analytics server, sell personal data, or track you across apps or websites. It does not contact tracking domains. The on-device processing and iOS-managed alarm features are described below.
When you start an exercise challenge, Forge uses the camera and an on-device MediaPipe pose model, with Apple's Vision framework as a fallback, to detect body-joint positions. Deterministic movement logic counts repetitions. Camera frames and body-pose results are processed on the device. Forge does not record, save, upload, or transmit camera frames or body-pose results.
After a completed session, you can request a general reminder. When available, Apple’s on-device Foundation Models framework selects from authored reminders using the exercise, camera position, repetition count and session type. Camera images, body landmarks, alarm labels and personal identifiers are not supplied to the language model. If Apple Intelligence is unavailable, Forge shows a standard reminder. This feature does not assess your form or control counting or alarms.
Forge stores alarm time, label, exercise, repetition goal, sound choice, and enabled state in its private preferences. It also supplies schedules and alarm identifiers/exercise metadata to Apple's AlarmKit so iOS can deliver alarms and display the exercise and goal on system alarm surfaces, including the Lock Screen and Dynamic Island. Those details may be visible to someone who can see your screen, subject to iOS settings. Forge keeps repetition totals, completion days and local alarm outcome history (completed or stopped early). Alarm history includes alarm labels, scheduled and resolved times, stop reasons, and identifiers used to avoid duplicate results. These records are stored in the app’s local preferences. Forge does not keep camera frames or body-pose histories. Forge does not provide its own cloud synchronization or backup service. iOS-managed device backups and device transfers may include the app's local preferences, depending on your settings. Removing the app removes app-managed data according to iOS behavior; it does not necessarily delete existing backups.
In versions that support Apple Health, after completing a real alarm challenge you may choose to save a workout to Health. Forge requests permission to write Workouts when you choose to save; it does not read Health data. The workout includes the exercise, repetitions, and the elapsed challenge time, including setup and pauses. Forge does not estimate calories or heart rate. Practice and stopped-early challenges are not exported. To support an uncertain save or an explicit retry, Forge stores the exercise, repetition count, start and end times, and a hashed occurrence identifier in its local preferences until the save succeeds. It keeps an export-status identifier to help prevent duplicates. Health retains saved workouts under your Health settings even if you delete Forge. Forge does not backfill earlier challenges.
Forge requests Camera permission to count exercise repetitions and Alarm permission to schedule alerts through Apple's AlarmKit framework. You can change either permission in iOS Settings.
Forge does not knowingly collect personal information from children or anyone else.
If you open a sound source/license or support link, the destination opens through the system browser. That website handles the visit under its own privacy policy. Opening a link is separate from Forge uploading camera or workout data.
Updates will be published on this page with a revised effective date. For privacy questions, email contact@sanchaygumber.com.