Privacy policy
Updated November 17, 2026
Your workout data
Sabel stores your history and notes, plans, goals, schedules, blocks, saved reviews, unfinished workouts and preferences on your device. It also stores your weigh-ins on your device, typed in by you or read from Apple Health if you turn that on, and your sex if you choose to enter it. They are used for your weight trend, a protein target, a weekly check-in and strength comparisons. Your weigh-ins are included in the export file you make yourself, the app never uploads your weigh-in history to an iCloud backup, and Delete training data, under Your data on the You tab, removes them. The most recent weight you type in yourself is also kept as your bodyweight preference, which is included in an iCloud backup if you turn backup on; weights read from Apple Health are never included. The app does not send this data to the developer and contains no advertising or custom usage-analytics SDKs.
Your food log
In the Plus edition, Sabel keeps your food log on your iPhone, in a file of its own. It holds each food you log with its name, amount and nutrients and when you ate it, the foods you make yourself, your favourites, your calorie, protein, carbs and fat target, and the height, birth year and activity level you give for a starting estimate. The bundled food lists are read on your iPhone, and searching them sends nothing. The app never uploads your food log to an iCloud backup and does not send it to the developer. It is included in the export file you make yourself and, like all app data, may be included in your iPhone's device backups. Delete training data, under Your data on the You tab, removes it.
Barcode scanning and lookups
In the Plus edition, Scan on the Food tab uses the camera to read the barcode on a food's pack. Sabel asks for camera access only when you open the scanner. It keeps no camera image and sends none; only the digits of the barcode are used, and you can always type them instead. A barcode is looked up in your own foods first, then in products saved on your iPhone, then in the bundled food list, and none of that sends anything. The Open Food Facts lookup is not in the App Store edition: there, a barcode in none of them offers Describe it, which opens Describe a meal for you to write what the product is, and Create food, and nothing is looked up online. In private test builds of Sabel, if it is in none of them, Sabel asks once whether to look it up on Open Food Facts, and nothing is looked up until you say yes. You can change your answer at any time on the You tab, under Food. One lookup is one request to Open Food Facts over HTTPS. It sends the barcode, your iPhone's IP address, as any web request does, the name and version of the app with the contact address carlelelid@gmail.com, as Open Food Facts asks, and the time of the request. It sends no account, cookie, device or advertising identifier, no search text and nothing from your log. Open Food Facts' privacy page lists IP logs kept for 3 years. A product the lookup finds goes through the same data checks as the bundled foods and is then kept on your iPhone, in the food file, and never in an iCloud backup. Sabel keeps no record of a barcode that was not found, of a failed lookup, of your IP address or of your requests. Delete training data, under Your data on the You tab, removes the products kept and your answer along with your food log.
Describing a meal
In the Plus edition, the App Store edition included, Describe a meal on the add sheet estimates a meal from a few words you write. It needs Plus. The first time you tap Estimate, Sabel asks whether to use AI, and nothing is sent until you say yes. Your answer is kept on your iPhone; you can change it at any time on the You tab, under Food, and Delete training data, under Your data on the You tab, removes it. After a yes, each tap of Estimate sends one request over HTTPS to Sabel's own server at sabel-strength-planner.vercel.app, and so does each answer you tap to a question about the meal, at most two, and each change you ask for under Check the meal, at most five. It sends what you wrote, at most 280 characters, the app's language, the name and version of the app with the contact address carlelelid@gmail.com, and Apple's signed record of your Plus purchase, which holds the purchase's transaction identifiers, the product and its dates, or, in owner builds, the owner token, so the server can check that Plus is active. An answer also sends the estimate the server sent back last and each question with your answer. A change you ask for sends what you wrote for it, at most 280 characters, your earlier changes to the same meal, and the meal as it stands on the card, your own foods and your own edits on it included. Your iPhone's IP address reaches the server, as with any web request. Only that meal is sent, nothing else from your log, and no device or advertising identifier. It is sent only to estimate and correct the meal. The server passes it to OpenAI, which reads it and sends back the foods, amounts and estimated calories. Sabel keeps none of it: the server does not keep what you wrote, the estimate, your answers, your changes, the reply or the purchase record, and its log line holds only the time, the result (whether the request worked, was refused or failed, or that OpenAI refused it), how many foods came back, whether a question was asked, which turn of the meal it was, how many changes were asked for and, when it happens, that a charge to the weekly count was lost. Vercel, which runs the server, and OpenAI handle the request under their own privacy policies. On your iPhone each food is then checked against Sabel's own food lists: where a food there agrees with the estimate its numbers are used, and otherwise the AI's estimate is, marked as one. Nothing is logged until you choose to. A row you change yourself, its food, amount or numbers, stays on your iPhone and is not sent, unless you then ask Sabel for a change, when the meal as it stands goes with it.
Weekly AI usage
Describe a meal, and the cloud Coach where the app has it, share a weekly limit, and the week starts on Monday at 00:00 UTC. To keep it, Sabel's server keeps, per subscriber, what that week's AI requests have cost and how many of them failed, and for two minutes how many requests came in the last minute. They are filed under an identifier the server makes from the purchase's original transaction identifier with its own secret key, never the purchase record itself. None of what you wrote and no estimate is in them, and the week's count is deleted by itself 8 days after it is first written. Each answer to Describe a meal, and to the cloud Coach where the app has it, also tells the app how much of the week is used and when it resets, which the app keeps only in memory while it runs and forgets when you withdraw your yes or delete training data. Reading the count is one request over HTTPS to Sabel's server, made only after you have said yes to Describe a meal or, where the app has it, to the cloud Coach: when Describe a meal opens, when AI usage opens (from the You tab, Describe a meal or the Coach), on each refresh there, and when the Coach or its page on the You tab opens, switches to a cloud mode or gets your yes again. It sends Apple's signed record of your Plus purchase or, in owner builds, the owner token, the name and version of the app with its contact address, and, as any web request does, your iPhone's IP address. Reading it counts nothing, and the server's log line for it holds only the time, the outcome and the status code.
Coach
The Coach, a chat that answers questions about your training, is only in private test builds of Sabel, not in the App Store edition. Where it is offered, it can run on your iPhone, on Apple's on-device model, and then sends nothing: your questions, the answers and the training data it reads (your program, recent workouts, weigh-ins you typed and your food log) stay on the phone. Weights and activity read from Apple Health are not given to it. The conversation is kept only in memory while the Coach is open; it is not saved, exported or backed up. In those builds the Coach can also answer through Sabel's own server, only after you agree to that in the Coach's own question, which is asked again when what it says changes: each question then sends the question and the app's language, the earlier questions in that conversation the server answered with their answers, a training summary that is not your whole log (today's date and your weight unit, your program, next workout and its rules, latest workouts, bodyweight trend, workouts this week against the plan, weeks in a row and the weekly average, plus your food log and how you compare with others if you use them), Apple's signed record of your Plus purchase with its transaction identifiers or the build's own owner token, and the name and version of the app with its contact address. The server checks the proof and passes the question, the earlier turns and the summary to OpenAI, which writes the answer, so the Coach can answer questions the model on your iPhone can't. Sabel does not store them, and Apple Health readings are never part of them. Each cloud answer counts toward the weekly AI limit (see Weekly AI usage). The Coach is free.
Apple Health
On supported devices running iOS 26 or later, you can choose to connect Apple Health. With your permission, Sabel records strength-training workouts, active energy and heart rate, and reads heart rate and active energy to show workout information. You can use workout logging without granting Health access. Manage permissions in Apple's Health settings. Turning off recording does not delete records already saved in Health. You can also turn on "Read weight from Apple Health" on the Apple Health page of the You tab, separately from recording workouts. Sabel then asks to read your body mass and nothing else, adds those readings as weigh-ins to Body, on the You tab, and never writes weight to Health. Removing a weigh-in in Sabel hides it there and leaves it in Health, and turning the switch off keeps the weigh-ins already added. You can also turn on "Count activity from Apple Health". Sabel then asks to read your active energy, adds up each day's total as Apple Health counts it, and uses it on the iPhone to move your daily calorie target with how much you moved compared with your usual day. Those totals are read when they are needed and are never stored, included in an export or a backup, or sent.
Lock Screen
Live Activities can display workout details and heart rate on your Lock Screen and Dynamic Island. Manage their visibility in iPhone settings.
Sharing and backups
Exporting your log shares a copy with the destination you choose. App data may be included in device backups, and Health data may sync through Apple according to your settings. Those services handle data under their own policies.
Complete file exports include history and notes, plans, goals, schedules, blocks, saved reviews, unfinished workouts, weigh-ins, your weight goal, your food log if you have one and portable preferences, including optional bodyweight and sex. Keep these files private. Opening or cancelling the share sheet does not itself create a durable backup.
iCloud backup is off until you turn it on, on the iCloud backup page of the You tab. When it is on, Sabel saves a copy of your training to the private CloudKit database of the iCloud account you are signed in with, and updates it after you log. A copy holds your workout history and notes, program choices, plans, goals, schedules, training blocks, saved reviews, an unfinished workout and your preferences, including the bodyweight and sex you entered yourself and any names and notes you typed. Names and notes can contain anything you type, so leave out health details you do not want in a backup. Apple Health data is never included: not weights read from Apple Health, not heart rate, not active energy, and nothing about whether you connected Health. Your weigh-in history and your food log are not included either. The only weight a backup holds is the most recent one you typed in yourself.
Turning backup on is a choice for this iCloud account. If a later version of Sabel changes what a backup holds, it asks you again before it uploads anything. Turning backup off stops new uploads and keeps existing copies; an operation already submitted may finish. Restoring a copy does not turn automatic backup on. Up to five copies are kept. Apple provides the storage. The app uses an opaque account identifier on your iPhone to detect account changes. There is no separate Sabel account server, and the app does not send backups to the developer. Training works offline. Checksums detect corruption, not authenticity. Backup and recovery never require Plus.
Deleting data
Deleting the app (rather than offloading it) removes its local data but does not remove iCloud backups. Change program keeps your workout history. Delete iCloud backups on the iCloud backup page of the You tab removes cloud copies and turns automatic backup off, which stays off until you turn it on again, and retains data on the device. Delete all Sabel training data removes history, plans, goals, schedules, blocks, reviews, unfinished workouts, preferences and recovery copies on this iPhone and in the selected iCloud account, and removes your weigh-ins, weight goal and food log from this iPhone. If cloud deletion fails, local data is kept. Without cloud capability, Delete training data affects only this iPhone. Delete Health records separately in Apple Health; exported files and system device backups must be managed at their destinations.
Purchases
Apple processes optional subscriptions; StoreKit displays price and any eligible trial. Logging, history, Apple Health, saved-plan execution, complete export/import, deletion, iCloud backup and recovery remain free after Plus ends. Logging food is free. Barcode scanning, saved meals and recipes, the starting estimate, the weekly food check-in and Describe a meal need Plus; after Plus ends your food log, saved meals and recipes stay on your iPhone, logging food keeps working, and you can still export and delete them. Sabel reads verified StoreKit purchase status to unlock paid features. It has no purchase backend. It does not transmit transaction identifiers to developer-operated servers, except that Describe a meal and AI usage, once you say yes to Describe a meal or, where the app has it, to the cloud Coach, send Apple's signed record of your purchase with each request so Sabel's server can check that Plus is active and count the week's AI use, and the server keeps none of the record (see Weekly AI usage). In private test builds the Coach's answers through Sabel's server send it too. Apple handles billing under its own privacy policy.
Support
If you email carlelelid@gmail.com, your email address and the information you choose to send are used to respond to your request. Send feedback in the app opens your email app with a last line naming the app version, build, edition, iOS version and kind of iPhone (for example iPhone18,1, never your iPhone's name); you can delete it before you send, and nothing is sent until you send the email yourself. Do not send workout or Health data unless it is needed for the issue. Support correspondence is retained only as needed to handle the request and related follow-up; contact the same address to request deletion.
Changes
This policy will be updated when the app's data practices change. Contact carlelelid@gmail.com with privacy questions.
Local diagnostics
Sabel keeps up to 200 recent technical events for seven days on your device, including screen visits, operation timings and fixed error categories. Reports include the app, build and operating system versions. They contain no workout contents, Health readings, account identifiers or raw error messages. This local report is never automatically forwarded. Under Your data > Privacy & diagnostics on the You tab, you can inspect, share or clear it. The local cache is excluded from device backups and may be removed by iOS. Fixed technical event names are also written to Apple's device logging system, whose retention is managed by iOS.
Remote error reporting
Remote reporting is disabled in the App Store edition and in owner beta builds, even when an existing receipt is present. Installing this edition does not delete previously received reports. Earlier development editions may allow limited technical error reporting to Sentry's EU service to help the developer investigate subscription-verification failures. It is off by default, requires an explicit choice, and lasts only until the current app process exits. You can stop it immediately in Privacy & diagnostics without affecting training. No offline queue or automatic retry is used. Stopping cancels pending transmission but cannot recall reports already received.
Reports contain a fixed failure category, app version/build, event time, random event ID, environment and a random recovery reference for that consent period. They do not contain workout contents, Health information, bodyweight, sex, raw errors, device or account identifiers, screen history, screenshots or replay. This is not automatic crash, hang or uptime monitoring. The receiving network necessarily sees your IP address; Sentry is configured to remove IP and geographical fields from stored error events. These reports are pseudonymous, not guaranteed anonymous. The developer can access received reports through Sentry. Sentry processes the service data under its own privacy and retention terms: https://sentry.io/privacy/
Your diagnostic reports
Choose Turn off and save current recovery receipt in Privacy & diagnostics before each support request or uninstalling this iPhone. Saving the receipt stops new reporting. If you later enable reporting again, save a fresh receipt; an older copy will not include later reports. It contains secret proof of access and the event IDs for reports attempted by this installation, not the remote reports themselves. The receipt is kept separately from training data, excluded from backups, and retained after reporting is turned off or training data is deleted. Each installation needs its own receipt; without one we may be unable to locate or authorize access to your reports. Treat exported receipts as sensitive.
Use Request diagnostics export or Request diagnostics deletion to contact carlelelid@gmail.com and attach your saved receipt. Opening email does not submit a request. Support verifies the receipt, provides the available stored events or requests their removal from active Sentry storage, checks the result and confirms the scope by email. Turn reporting off on all relevant installations before requesting deletion. Reports still being processed require a follow-up check. Provider backups, alert emails, support correspondence and exported copies have separate lifecycles; turning off reporting or deleting training data does not erase these copies. Ask support about those copies as part of your request. This is a support-assisted process, not an automatic completion guarantee.
Product analytics
No custom feature-use analytics is sent by this app. Apple provides aggregate App Store information such as downloads and territories. Apple's optional usage sharing is controlled through Apple settings, not in this app. We do not treat download totals as a count of distinct people.
This website counts page views with Vercel Web Analytics. It records the page, referrer, approximate location, browser, operating system and device type, and does not set third-party cookies. Vercel says visits are not tied to an individual and its visitor hash is discarded after 24 hours. The app itself does not include it.
Optional website measurement
Website measurement is off until you allow it. If you opt in, this website sends only a fixed page name, an App Store button location or a sample-start/sample-completion event, and a separate random removal token for that action. It does not send entered weights, reps, workout contents, free text, URL query parameters or a visitor identifier. Browser Do Not Track and Global Privacy Control also keep these action counts off.
The server keeps daily counts and temporary removal metadata in a private Vercel Blob store. The stored metadata is a hash of each random token and its counter category; separate actions have separate tokens and are not grouped into a visitor profile. Counts and metadata are kept for 30 UTC days, with daily cleanup. Vercel processes network requests to host the website and collector and may retain service logs separately.
Use Website measurement in the footer to turn collection off, export the fixed action descriptions and removal receipts held in this browser, or turn it off and remove those contributions from active storage. The removal button covers receipts on this browser and domain. Turning it off alone does not remove earlier counts. If removal fails, the receipts stay here and the page offers retry; it does not claim completion. Receipts are saved before submission, so an attempted action may not have reached the server. Removal also blocks a delayed request from adding that action later.
The allow/off preference and receipts are kept in this browser’s local storage. Clearing browser storage removes those local copies and may make earlier contributions impossible to locate before they expire. Exported receipts are proof that authorizes removal; keep them private. Browser exports, service logs and provider backups have separate lifecycles and are not erased by removing active counter contributions.
This choice controls these optional website action counts, separately from the Vercel page analytics described above. Apple campaign links measure attributed App Store results under Apple’s reporting rules. None of this website measurement is included in the iPhone app.