Fortior is local-first. Account sign-in, Cloud sync, hosted third-party AI, and sharing with a human coach are separate capabilities with separate controls. We do not sell personal data, serve ads, or track you across apps or websites.
The app stores your profile, workouts, notes, recovery, meals and nutrition, body measurements, health metrics, lab entries, and derived analytics in an account-scoped database on your device. Progress-photo originals and nutrition photos you choose to keep stay in protected app storage and are excluded from ordinary Cloud sync and data exports. Temporary nutrition-capture photos are discarded after use or expiration.
If you create or sign in to an account, Supabase receives an account identifier and the sign-in details supplied by your chosen method, which may include an email address and display name. Fortior uses that account for authentication, recovery, account linking, security, entitlements or coach sponsorship, and authorization and rate limiting for hosted features. Signing in does not turn on Cloud sync.
If you separately enable Cloud sync, Fortior sends app records over encrypted connections to Supabase so they can synchronize across your devices. Access controls scope hosted records to your account. A random per-install identifier travels with synced events so Fortior can order, deduplicate, and safely replay them; it is not an advertising identifier and is never used to track you. Turning Cloud sync off stops future synchronization; it does not by itself delete records already synchronized to your account.
With Cloud sync on, Fortior also sends the ratio between catalogue lifts you train together, for example leg press to back squat, with the number of paired sessions behind it. No loads, dates, or custom exercises are included. Other athletes never see your ratios; the app downloads only the median ratio for a pair once five or more athletes contribute to it, which improves first-time load suggestions for everyone.
Hosted features retain bounded account-linked quota or reservation counts and coarse allow-listed status, latency, request-size, provider-usage, and validator-result buckets for authorization, abuse prevention, reliability, and cost control. Each hosted AI or online food lookup request also leaves an account-linked usage entry: the feature, provider and model, token and image counts, latency, outcome, subscription tier, and an estimated provider cost. These records exclude raw notes, prompts, meals, health values, photos, credentials, and provider response bodies and are not used for advertising or tracking. When an account is permanently deleted, its usage entries lose the account link and remain only as anonymous cost totals.
If you are signed in and Share usage analytics is on in Settings, the app sends daily counts of the features you use, such as finished workouts, meals logged by method, Ask Fortior messages, cardio sessions, and Progress categories viewed, with the app version. For Ask Fortior, the counts also show whether each answer came from Fortior AI or from your phone, with a short reason code when it came from your phone, and never include your question, the answer, or your data. It also sends a profile summary made only of categories: your goal, main sport or activity, experience level, display mode, Personal or Coach mode, platform, and system version. Fortior derives your subscription tier from its own entitlement records rather than from the app.
Fortior uses these records to understand which features are used, by which kinds of athletes, and what they cost to run. They contain no workouts, meals, notes, health values, or text you type, are not shared with advertisers or used for tracking, and are deleted with your account. Nothing is sent while you are signed out, and turning the setting off stops sending and deletes counts not yet sent from this device.
Online food search sends the search needed for that action to Fortior's hosted food-catalog service. When a valid barcode has no cached match, the app may send only that barcode in a read-only request directly to Open Food Facts. Like any direct internet request, Open Food Facts receives the device's network address and standard connection information; it does not receive your Fortior account ID, meal, photos, notes, or corrections from this lookup.
Open Food Facts results are visibly attributed and stored in a device-local cache. The app treats a cached result as fresh for seven days; an expired row may remain on this device and can be refreshed by a later lookup. Fortior does not search that community database as you type, upload product or image contributions to it, or add its provider catalogue records to your account's Cloud sync database. A meal you log keeps only the nutrition snapshot you reviewed.
Ask Fortior is Your AI coach. Hosted answers and other AI analysis remain off until you accept an in-app disclosure or deliberately tap an AI action with that disclosure beside it. A hosted request requires a signed-in account but does not require or enable Cloud sync. Fortior sends only the question-scoped information needed for that request: your question, a bounded recent conversation, and selected evidence for the categories you allow under Ask Fortior data access, such as training, nutrition, recovery, or health context. That evidence is prepared on this device, with or without Cloud sync. This evidence can name the exercises you log, including custom exercises you create, but it never includes other names you type, such as program, template, or event names, or the text of your notes. The same choices apply to AI post-workout explanations, “Why this weight” explanations, and AI monthly reviews, and for these features a category you turn off is never shared with the AI provider. Other AI features don't use these choices: while AI is on, workout notes you save are sent with their set details for Fortior AI to tag, weekly review summaries send that week's set counts and number of new bests, and program explanations and swap suggestions send the program with your goal, experience, equipment, and constraints. Fortior AI in Coach Workspace follows the permissions you grant Your Coach instead, as described below. A photo or screenshot is included only when you tap the action that names AI analysis for the images you selected. An InBody scan sends either one photo of the printout or up to three screenshots from the InBody app.
Requests pass through the Fortior Supabase backend to a contracted AI provider. Fortior currently uses Anthropic or OpenAI depending on the feature and server configuration. The selected provider receives the bounded request content described above; Fortior does not send your email address or Supabase user ID as a separate provider identifier. Selected images are resized and bounded before analysis. Fortior does not persist private Ask Fortior transcripts as cross-session chat history. OpenAI requests disable provider-side response storage. A structured memory suggestion or action proposal remains reviewable and does not change canonical data unless a permitted person deliberately confirms it.
Fortior requires service providers that receive personal data to protect it consistently with this policy and applicable Apple requirements, and limits their use to providing the services described here.
After you log an AI-estimated meal, Fortior automatically queues a text-free calibration record. It contains only bounded numeric provider, model, prompt, and confidence codes; estimated mass and nutrient ranges; final quantities and nutrition values; and yes-or-no edit, correction, add, or remove signals.
The record excludes the photos; food names; serving descriptions; your correction text; meal name, notes, and time; location and locale; and every account, email, meal, component, request, and device identifier. It has no timestamp. The local retry row never enters Cloud sync or data export and is removed after successful delivery.
Submission requires a signed-in account for authorization and abuse prevention, but Fortior stores no account or meal link with the accepted calibration record. Because that link does not exist, accepted anonymous records cannot later be found or deleted by meal or account; deleting a meal or account removes any still-pending local row. Fortior uses these records for human-reviewed quality evaluation; they do not automatically change the production model and the photos are not used for model training.
If you accept a relationship with a human trainer, the trainer appears as Your Coach — [Name] and uses Fortior for Coaches / Coach Workspace. A coach can receive only the categories and history range you grant. The controls are independent and can include:
The permitted information is used for coach review, validated program changes, comments, and any coach-sponsored entitlement. If Your Coach uses Fortior AI in Coach Workspace, the AI provider receives only information from the categories and history range you grant that coach; your coach permissions control it, not your Ask Fortior data access choices. Private Ask Fortior conversations are never included by default. Only a specific review, report, or proposal artifact you deliberately share can enter Coach Workspace.
You can change, pause, or revoke coach permissions in Settings. Fortior applies a revocation on your device immediately and sends it to the server; server-side access stops when the revocation reaches the server. New coach reads and Coach tools then fail, and affected coach-side caches are removed or expired. Relationship status, authorship, program revisions, comments, sponsorship changes, and audit history may remain for accountability without restoring access to the underlying revoked categories.
HealthKit access is optional and controlled by Apple permissions. Granted data is used only for app functionality and personalization, never advertising or sale. HealthKit-derived information leaves the device only through a Cloud sync you enable; a hosted AI request after you turn on AI, which uses only the categories you allow under Ask Fortior data access; a category or artifact you explicitly share with Your Coach; or an export you initiate. Whoop, Oura, and Strava connect only when authorized and may be disconnected in Settings. Disconnecting stops future imports; existing imported records remain until you remove them.
For a supported outdoor activity, Fortior records or imports precise route coordinates only with the relevant permission. The route is used to show your map and calculate activity distance and pace, not to track you across apps, advertise to you, or sell your location. A saved route remains on device by default and leaves it only through a Cloud sync you enable or an export you initiate. Fortior excludes route geometry from Ask Fortior and human-coach review payloads.
Local records remain until you remove them, permanently delete the account, or remove the app and its data. Synced records remain in your account when Cloud sync is merely disabled. Ask Fortior transcripts are not retained as cross-session chat history, while confirmed proposals and their audit records remain part of your account history. Revoked coach relationships can retain the limited accountability history described above.
Use Settings to export app data, remove this phone's data, disable Cloud sync or AI, revoke integrations or coach access, and permanently delete a signed-in account. Permanent account deletion removes the hosted auth account and account-linked records, provider credentials, sync state, and this account's local store, and requests Sign in with Apple token revocation when applicable.
For support or privacy requests, use the Fortior support and feedback form. The Fortior support page lists common fixes. Do not include health records, progress photos, credentials, or other sensitive information in a support message.