Privacy Policy

Pack privacy

Pack is a daily workout check-in app for private crews of up to seven friends. Supabase anonymous authentication automatically creates a private guest account. No email address, password, or registration form is required. Your display name and activity are linked to that guest-account identifier, even though a real name is not required. Pack's guest account is separate from a FOOM Athlete or Coach account.

What Pack stores and why

• Guest-account ID and display name to identify you within Pack and protect access to your data.
• Crew membership, crew name, and six-character invite code so friends can join and share a private crew.
• Daily check-ins, including YES, REST, or NO status, day, and timestamp, to show the crew's activity and streak.
• One-way messages, including text, sender, recipient, day, and timestamp, to deliver encouragement. A member who records YES can send one message of up to 160 characters per eligible teammate per day. Recipients cannot reply.
• Spotlight activity, including who adds their name to a shared “Waiting on you” card for the last teammate still pending or on NO.
• Safety information, including blocked guest accounts, reported-message copies, participant identifiers, sender names, report reasons, optional details, timestamps, and moderation decisions, to investigate reports and enforce messaging restrictions.

Pack does not request location, contacts, photos, microphone access, or Apple Health data. It has no advertising, tracking, third-party analytics SDKs, subscriptions, or AI processing. Messages appear in the app; Pack does not send push notifications. Message text and optional report details contain whatever information you choose to enter.

Who can see messages and crew activity

Crew members can see each other's display names, check-ins, and shared spotlight activity. Within the app, private message text is available to its sender and recipient. If a recipient reports a message, its contents, participant identifiers, and report details are also shared with authorized Pack moderators. Other crew members cannot see the report. Database access policies enforce these boundaries. There are no public profiles, public feeds, or discovery features.

Reporting, blocking, and filtering

Server-side rules check message text for objectionable language before storage. Filtering cannot identify every harmful message or context. Use the … menu on a received message to select Report message or Block sender. Reporting hides the message from your inbox and submits a copy with your report to a private review queue. Authorized moderators can hide content from app users and suspend messaging privileges.

Blocking hides that sender's messages and spotlight nudges and prevents new nudges between the two accounts. Blocks follow guest accounts when members leave and rejoin crews; check-ins remain visible. Manage or remove blocks under crew settings → Blocked Senders. Reported messages remain hidden from the reporter after unblocking. Message text is not sent to a separate AI moderation provider. See Pack's community rules.

Storage, retention, and deletion

Supabase provides Pack's authentication and managed database storage. App connections use encrypted HTTPS and WSS. Supabase processes data on our behalf under its privacy policy.

Guest accounts, memberships, and check-ins remain until deleted. Messages and spotlight activity leave the dashboard when the local day changes; that does not delete their stored records. Ordinary message and spotlight records remain until either participant leaves or switches crews, deletes their account, or the crew is deleted.

Blocks, reported-message copies, and moderation records are tied to guest accounts and can remain after leaving or switching crews. This preserves reports for review and prevents rejoining from bypassing a block or restriction. Hiding a message through moderation does not erase its stored record. Deleting either participant's guest account deletes their associated blocks and reports, including the reports' audit records. Deleting a restricted account also deletes its messaging restriction and associated moderation history.

To delete your current membership, check-ins, and associated messages and spotlight activity, choose Leave Group in crew settings. The guest account and its safety records remain. If you are the last member, the crew is also deleted. To delete the complete guest account and its associated app and safety data, choose Delete Account & Data in crew settings, or Delete Account on the create-or-join screen. Crews with other members remain, without a link to the deleted creator account.

These controls delete records from the live service. Supabase may retain backup copies for its configured disaster-recovery retention period; see its backup documentation. Uninstalling Pack does not delete the guest account or server records, and iOS may retain credentials in Keychain. Use the in-app deletion control before uninstalling if you want that data removed.

If you email Pack support, we receive your email address, message, and any attachments you choose to send and use them to respond. For privacy requests, report follow-up, or appeals of a messaging restriction, contact matt@algorithmicresearchgroup.com. Pack's dedicated privacy policy · Pack support.

Hill Reps privacy

Hill Reps is a separate hill-repeat recorder for iPhone and Apple Watch. It does not create a FOOM account or send run records to FOOM-operated servers. It has no advertising, analytics SDKs, AI processing, or coach sharing. The account and meal-photo services elsewhere in this policy do not apply to Hill Reps.

Location, elevation, and motion

During an active run, Hill Reps uses device location, including precise location when permitted, to record your route, measure distance, and help identify hill repeats. It stores workout times, route coordinates, available altitude and accuracy readings, elevation samples, hill counts, splits, and any inclusion or exclusion decisions you make. Location recording can continue when the screen is locked during an active run.

With Motion & Fitness permission and supported hardware, Hill Reps uses relative-altitude readings from the device's barometer to improve elevation measurements. It may request motion-activity access to enable that permission; activity classifications are not kept as part of your run history. These signals are processed on your device. You can use GPS-only recording if motion access is unavailable or declined.

Local storage, iCloud, and your paired devices

Active run recovery checkpoints and completed runs are stored on your device. When iCloud is available, completed run records and deletion markers sync through your private CloudKit database under your Apple account. A paired iPhone and Apple Watch can also exchange completed runs, record identifiers, revisions, and deletion markers through Apple's WatchConnectivity service. We cannot access those records through FOOM's servers. Apple operates these services under its own privacy terms.

Hill Reps separates cached histories by iCloud account. Switching accounts or signing out does not erase the earlier account's local records; they can reappear when that account is used again. Apple Maps is used to display routes and may process map-service requests under Apple's privacy terms.

Apple Health

With your permission, Hill Reps on Apple Watch uses a HealthKit workout session for background recording and saves the completed workout to Apple Health. Distance, route, and elevation details may be included where available and permitted. Hill Reps does not request read access to your existing Health records, and does not send Health data to FOOM-operated servers, advertisers, or AI providers.

Your controls and deletion

Change Location, Precise Location, Motion & Fitness, and Health permissions in your device settings. Hill Reps' Run setup screen explains how to find them. Withdrawing permission may reduce accuracy or prevent recording; it does not automatically erase earlier records.

Delete a run from its detail screen to remove it from Hill Reps. Deletions propagate to iCloud and paired devices when connectivity is available. Deletion markers are retained to prevent old copies from returning. Any workout already saved to Apple Health remains there and must be managed separately in Health. Removing the app alone is not a request to delete its iCloud history: a reinstall may restore synced runs. Delete unwanted runs in the app and allow sync to finish before uninstalling.

If you email support, we receive the address, message, and any screenshots or other information you choose to send. Avoid sending route or Health information you do not want to share. Contact matt@foomfitness.com with privacy questions.

Quiet Run privacy

Quiet Run is a separate outdoor run recorder for iPhone and Apple Watch, with Quiet Run and Mile by Feel modes. It does not require a FOOM account or send run records to FOOM-operated servers. There are no advertising or analytics SDKs, AI processing, social feeds, or coach sharing in Quiet Run. Its records are separate from Hill Reps and the other FOOM apps. Hiding numbers during a run changes what is displayed, not what is recorded.

Location, elevation, and recording

With your permission, Quiet Run uses location during an active run to record route coordinates and timestamps, measure distance, and calculate post-run pace and splits. It also stores available speed, altitude, accuracy and elevation readings, run start and end times, recording mode, and derived terrain summaries. Mile by Feel compares your recorded distance with one mile. Location recording can continue while the screen is locked during an active run; the app stops recording location when you end or discard the run.

With Motion & Fitness permission and supported hardware, the barometer provides relative-altitude readings for elevation estimates. Quiet Run may request motion-activity access to enable this permission; activity classifications are not stored in run history. GPS altitude can be used when barometric readings are unavailable. Route filtering, elevation analysis, and post-run statistics are calculated on your device. Distance, pace, elevation, and heart-rate summaries are estimates, not medical assessments.

Local storage, private iCloud history, and paired devices

Recovery checkpoints and completed runs are stored on your device. When iCloud is available, completed run records, including the app’s recorded route and terrain data, revisions, and deletion markers, sync through your private CloudKit database under your Apple account. A paired iPhone and Apple Watch can exchange completed runs, identifiers, revisions, and deletion markers using Apple’s WatchConnectivity service. These app-recorded run records are separate from the Health readings described below. We do not receive these records on FOOM servers.

History is separated by iCloud account. Runs made while signed out can join the account you sign into; matching local notes and effort labels follow those runs on that device. Switching between iCloud accounts does not copy an earlier account’s notes into the new account. Earlier account histories can remain locally and reappear when that account is used again. Apple operates iCloud and WatchConnectivity under its own privacy terms. Apple Maps displays routes and may process map-service requests under Apple’s privacy terms.

Apple Health and heart rate

With permission, Quiet Run on Apple Watch uses a HealthKit workout session for screen-off recording and saves the completed running workout to Apple Health. Recorded heart rate, distance, route, and elevation gain may be included where available and permitted. Recording a run on iPhone alone does not measure heart rate or export that run to Health.

Quiet Run requests read access to Workouts and Heart Rate to display effort after a run. It queries workouts tagged with the matching Quiet Run identifier and their associated heart-rate samples, not workouts from other apps. Readings are used on demand for average and recorded peak heart rate, an iPhone chart, sample coverage, and time in optional custom heart-rate zones. These readings stay in HealthKit and memory while the report is in use; they are not copied into Quiet Run’s files, CloudKit backup, or WatchConnectivity messages. We do not send Health readings to FOOM servers, advertisers, or AI providers.

Health permission is optional for iPhone reports. On Watch, permission to save workouts supports recording while the screen sleeps. You can decline individual Health permissions, although that may limit recording or report details. Apple does not tell the app whether individual read permissions were denied, so missing data can also mean no readings are available or Health syncing has not finished. Apple’s own Health storage and sync are controlled separately from Quiet Run’s iCloud run history.

Private notes, effort, and custom zones

Optional run notes, Easy / Steady / Hard effort labels, and custom heart-rate zone boundaries are stored in protected, account-separated files on the device where you enter them. They are excluded from device backups and are not sent through CloudKit or WatchConnectivity. They do not automatically appear on your other devices. Custom zones are user-defined ranges, not Apple’s automatic zones, and are not written to Health. Quiet Run does not read your date of birth to calculate zones.

When a local run joins an iCloud account, its matching notes and effort labels move with it on the same device. Existing edits in that account take precedence. Protected original copies can remain if the transfer fails or conflicts with newer edits, so they are not lost. This does not upload the notes. Removing the app can permanently remove local-only notes, effort labels, and zone settings, even if iCloud later restores the run itself.

Your controls, retention, and deletion

Run setup explains Location, Precise Location, Motion & Fitness, and Watch Health access. You can change permissions in device settings or Health. A saved report offers Connect Health and Refresh Health data when readings are unavailable. Withdrawing permission does not automatically delete existing records. You can edit or clear a note, change an effort label, and change or remove custom zones in the app.

Quiet Run keeps completed run history until you delete it. To delete a run, open it in History and choose Delete run. This removes the app’s run and its matching local reflection for that account; the deletion propagates to iCloud and paired devices when connectivity is available. Deletion markers and records of which account owns a transferred note can be retained to prevent old copies from returning or moving into another account. Workouts already saved to Apple Health remain there and must be deleted separately in Health. Removing the app alone does not delete iCloud history. Delete unwanted runs and allow sync to finish before uninstalling; reinstalling can otherwise restore synced history. Earlier account data remains separate.

If you contact support, we receive the email address, message, and attachments you choose to send, and use them to respond. Avoid including private route or Health information unless you want to share it. Contact matt@foomfitness.com for privacy questions. About Quiet Run · Quiet Run support.