Privacy Policy
OZRK Fit keeps your logs in an encrypted database on your iPhone. If you sign in, selected records are also saved to your private cloud account. Apple Health data is read on your device and is not uploaded.
1. Who is responsible
OZRK LLC, PO Box 283, Greenland, AR 72737 (“we”, “us”) provides the OZRK Fit app and decides how the data described here is used. Privacy contact: ozrkapp@gmail.com.
2. Summary
- You can use much of the app without an account; that data stays on your device.
- With an account, your records sync to a private account protected by row-level security so that each account can reach only its own rows.
- Apple Health data is not uploaded by the app. The app has no advertising or analytics SDKs, and we do not sell personal data.
- Photos for food estimates are sent once for analysis; our code does not store or log them. If a version offers “Keep this photo for 7 days” and you turn it on, that photo is also stored privately and deleted automatically 7 days after you saved it; the foods and nutrition you confirmed stay in your history.
- You can export your records, delete entries, withdraw permissions in iOS Settings, and delete your account in the app.
3. What data the app handles
3.1 Stored on your device (always)
Your records are kept in an encrypted local database (SQLCipher); its key is held in the iOS Keychain on that device. This includes: workouts, templates and plans; runs (including GPS route points); food, water and body-measurement logs; goals; your training profile; saved foods and meals; symptom and recovery check-ins; your appearance choice; the cached weather reading and chosen weather place; cached product lookups; your lifestyle log (see 3.3); a cached summary of the Apple Health values you allowed; and the record that you accepted our Terms and Privacy Policy (document versions, time, and that you confirmed the minimum age). iOS device backups that you make (for example to iCloud) are controlled by your device settings and may include app data.
3.2 Saved to your cloud account — only if you create an account and sign in
| Data | Why |
|---|---|
| Email address, password (handled by our authentication provider, Supabase Auth; the app does not store it), display name. Sign-in is by email and password only; accounts require email verification | Create and secure your account, send verification and password emails |
| Age confirmation: the time you confirmed you are at least 13 years old, and whether the account has been restricted for being under that age. We do not collect your date of birth or any identification | Apply our minimum-age rule and keep under-age accounts from using the service |
| Preferences: units, preferred activity, experience level, equipment, training days, onboarding status; goals (weekly workouts, daily calories) | Personalize the app and sync it between devices |
| Training profile: goals, equipment, schedule, activity level, age in years (optional), eating style, allergies and exclusions you type, and injury or limitation details and clinician restrictions you enter (health-related, sensitive) | Choose exercises and defaults more cautiously |
| Workouts, templates, custom exercises, workout feedback and symptom/recovery check-ins (health-related) | History, progress, safety guidance, reports |
| Runs: date, duration, distance, GPS route points and the weather recorded with the run | Run history and records |
| Food entries (names, calories, macros, meal, time, source) and daily water count; body measurements you enter | Nutrition and progress tracking |
| Meal photos, only if you turn on “Keep this photo for 7 days” (private storage, access only by your account through short-lived links, deleted by an automatic job 7 days after the upload time; the upload time and deadline are set by our server) | Show the photo next to the meal for a week |
| Progress photos you choose to upload (private storage folder per account; allowed types JPEG/PNG/HEIC/WebP up to 10 MB) | Your own progress comparisons |
| Subscription entitlement, if a subscription is ever offered and purchased: whether Premium is active and when it expires (not your payment details) | Unlock Premium server features |
| Usage counters for photo estimates: a per-day count and per-request reservation records (request id, day, status) | Enforce daily limits and avoid double charging |
3.3 Kept on your device only
- Lifestyle log (for example caffeine, alcohol, medication, illness, stress) and its associations with recovery trends — not synced, not shared, not used for analytics.
- Apple Health data you allow the app to read: workouts, sleep, step count, active energy, resting heart rate, heart rate variability, body weight, and walking/running distance. These are read on the device to show recovery and activity and are cached on the device; the app has no code that uploads them. If you turn it on, the app can also write workouts, workout routes and walking/running distance that you record in the app to Apple Health.
- Saved foods and meals, cached weather and product lookups, and the cached Health summary.
- BMI calculator inputs (the height and weight you type there; age comes from your training profile) — kept in the encrypted local store, never synced, and removed by “Clear this device” and account deletion.
- Appearance: your theme and accent choice, and — only if you pick one — a background picture. You choose it with the iOS photo picker; the app saves a cropped, reduced copy in its own storage on your phone. It is never uploaded. Your photo library is not changed. Removing the background deletes the copy.
- Shopping list, reminders and badges: items, stores and notes you type, the reminder times you set, and badges earned from your own logged activity. Not synced and not shared.
- Reminder notifications are scheduled on your phone by iOS. They do not use a push server and nothing about them is sent to us. iOS asks for permission when you add your first reminder; you can turn them off in the app or in iOS Settings.
- Home Screen widget: if you add the widget, the app saves a small snapshot (today’s Calorie goal, Calories logged and remaining) in an App Group container shared only with the OZRK Fit widget on the same phone. It contains no food names, health values, location or account details, and is cleared when you clear the device or delete your account.
- Calendar: “Add to calendar” opens the iOS event screen with a planned workout filled in. The event is created only if you tap Save there; the app does not read your calendar.
3.4 Processed temporarily and not stored by our code
- Meal photos, if you use the photo-estimate feature (a Premium feature that may not be available in every version): resized on your phone, sent to our server over HTTPS, forwarded to an AI model provider, and the estimate is returned. The picture is not saved to your food log. By default our server code does not write it to storage or logs, and the temporary file on your phone is deleted after the result is shown or when you leave the screen. Optional 7-day copy: if a version offers “Keep this photo for 7 days” and you switch it on, the app uploads the resized picture (location and camera metadata removed) after you confirm the meal; it is checked by an automated photo-safety service, stored in a private folder only your account can open, and removed by a scheduled job 7 days after the upload, or sooner if you tap “Delete photo now” or delete your account. The foods, portions, nutrition values, their sources and your corrections stay in your food history after the picture is gone; the app then shows that the picture has expired.
- Location coordinates for weather and place search (see section 7).
- Generic food search (USDA FoodData Central), once switched on in a release: the words you search are sent to our server, which asks USDA using our own access key and returns the result. The key is never in the app. We do not store the search text; USDA receives our server’s address, not yours. This feature is built but not yet deployed or active.
- Feedback and bug reports are composed in the app and handed to your own mail app. Nothing is sent until you press Send in Mail, the message contains only what you see in the preview (emails, tokens and coordinates are removed from the text, and optional app version, iOS version, locale and theme), and we have no feedback server.
3.5 Not collected
The app contains no third-party analytics, advertising, attribution or crash-reporting SDKs and does not read your contacts or advertising identifier. Planned features such as reading nutrition labels or ingredient lists from photos are not active; if they are switched on later, this policy will be updated first.
4. Why we use data
To provide the features you use (logging, plans, safety guidance, charts, sync, subscription access, photo estimates, weather); to secure accounts and prevent abuse (sign-in, rate limits, quotas); to communicate with you about your account (verification and password emails); to meet legal obligations; and to keep the service reliable. We do not use your data for advertising and do not use it to train AI models.
5. Legal bases (for people in the EEA, UK and similar regions)
Where such laws apply we rely on: performing our contract with you (providing the app and your account); your consent (for example health-related details you choose to enter, location, Apple Health and camera/photo permissions, which you can withdraw in iOS Settings or in the app); our legitimate interests in security and reliability; and compliance with legal obligations.
6. Health, fitness and sensitive information
Information about injuries, limitations, symptoms, medication, body measurements, and Apple Health values is sensitive. You choose what to enter. We use it only to operate the features you use. We do not use it for advertising and do not share it with anyone except the processors in section 8 acting on our instructions. Lifestyle log entries and Apple Health data stay on your device (section 3.3).
Photos for food estimates reach an AI model provider (currently Anthropic) through our server. The provider’s retention of API inputs: Anthropic’s published terms for API customers state that inputs and outputs are automatically deleted from its systems within 30 days (longer only if flagged for enforcement of its Usage Policy, where the law requires it, or under special agreements), and that API inputs and outputs are not used to train its models by default (Anthropic privacy centre, checked 17 October 2026).
7. Location and weather
- Run tracking uses your device’s location at high accuracy while you record a run, and can continue with the screen locked only while a run you started is active (iOS shows its location indicator). Route points are part of the run record: on your device, and in your account if you sign in.
- Weather uses approximate device location only if you tap to allow it (or a city you search for). The app rounds coordinates to about 1 km before sending them to Open-Meteo to get conditions and sunrise/sunset; the weather saved with a run uses the same rounding. Place searches send your search text to Open-Meteo’s geocoding service. Like any internet request, the provider can also see your IP address. Open-Meteo states that its server logs, which may contain coordinates, are removed after 90 days. The last reading and chosen place are cached on your device.
- If you decline location, the app does not ask repeatedly; you can choose a place by name instead or change the permission in iOS Settings.
8. Who else handles data
| Provider | What it receives | Why |
|---|---|---|
| Supabase | Account and synced records (3.2), authentication emails, standard request logs; region: United States (AWS us-east-2, Ohio) | Authentication, database, private file storage, server functions |
| AI model provider (Anthropic, via our server) | The meal photo you submit for an estimate and a fixed instruction, if you use that feature | Estimate calories and macros |
| Apple | Purchases (StoreKit) if offered, Apple Health access on your device, device location services; crash and diagnostic reports if you share them with developers | Subscriptions, device features |
| Open-Meteo | Rounded coordinates or place-search text, plus your IP address | Weather, sunrise/sunset, place search |
| USDA FoodData Central (nutrition database held on our server, and searches through our server when switched on) | The words you search for in generic food search. USDA sees our server, not your device | Generic food composition data (public domain, CC0) |
| Open Food Facts | Barcodes or search words you look up, plus your IP address | Product data |
| Expo (EAS Update) | On every launch the app checks Expo’s update service, which receives standard request data such as your IP address and the app and runtime version | Delivering app updates |
| Cloudflare (this website) | When you open these legal pages, standard web request data such as your IP address and browser type reaches Cloudflare, which serves the pages. The pages set no cookies and run no analytics or scripts, and request logging for this site is switched off in its configuration | Serving the Terms, Privacy Policy and Support pages |
We do not sell personal data or share it for cross-context behavioral advertising. We do not use Apple Health data for advertising or data mining. We may disclose information if required by law or to protect rights and safety. Sharing you start yourself (for example exporting your records through the iOS share sheet) is under your control.
9. How long data is kept
- On your device: until you delete it, use “Clear this device”, or delete the app.
- In your cloud account: while your account exists. When your account is deleted we remove your files from private storage and then delete your authentication record; the database ties each record to the account so that it is deleted with it.
- Optional 7-day meal photos: deleted 7 days after upload by a scheduled job (a failed deletion is retried automatically); copies in database backups or provider logs expire on those systems’ own schedules, which we have not yet verified. Photos sent for estimates: not stored by our code unless you chose the 7-day option. Anthropic’s published terms for API customers state that inputs and outputs are automatically deleted from its systems within 30 days (longer only if flagged for enforcement of its Usage Policy, where the law requires it, or under special agreements), and that API inputs and outputs are not used to train its models by default (Anthropic privacy centre, checked 17 October 2026). Our own agreement with the provider may differ.
- Weather and product look-ups: Open-Meteo states that it removes individual server log files after 90 days; Open Food Facts states that it keeps IP and log data for up to 3 years.
- Backups: The provider does not keep project backups on the plan we currently use. We may keep manual exports of our database for recovery; data of accounts you delete is removed from those exports within 30 days of deletion.
- Server and platform logs: Our database provider keeps standard request logs for about one day on the plan we currently use; this may be longer if we change plans.
- Legal records: we may keep limited information where the law requires it.
Deleting your account does not delete copies held by other companies under their own policies (for example Open-Meteo, Open Food Facts, Expo or Apple), and data may remain in backups and logs until they expire.
10. Security
Local data is stored in an encrypted database whose key is kept in the iOS Keychain; sign-in sessions are kept in the Keychain; the app talks to our servers over HTTPS; cloud tables use row-level security so each account can access only its own rows; private photos are in a non-public storage bucket; and server functions verify your sign-in before acting. No system is perfectly secure, and we cannot guarantee absolute security. Protect your device with a passcode and keep your password private.
11. Your choices and rights
- In the app: edit or delete entries; export your records (Profile › Data & account, and “Share these numbers (CSV)” in Analytics); turn off lifestyle categories; change permissions for camera, photos, location and Apple Health in iOS Settings; sign out; delete your account.
- By request: depending on where you live you may have the right to access, correct, delete, restrict or object to processing, receive a portable copy, withdraw consent, and complain to a data-protection authority. Email ozrkapp@gmail.com from the address registered to your account. We may need to verify your identity before acting.
- California residents: we do not sell or share personal information as defined by California law.
12. Deleting your data
Step-by-step instructions, including what to do if you cannot open the app, are on the support page.
13. Children and teenagers
The app is intended for people aged 13 and older and is not directed to children under 13. It does not verify age. When you accept our documents and when you create an account it asks you to confirm that you are at least 13; accounts are not created without that confirmation, and an age below 13 cannot be saved in your profile. We do not ask for your date of birth or identification.
If an account is reported as, or found to be, under 13, it is restricted: its stored records stop being readable or changeable through the app and the photo-estimate feature is switched off for it. Nothing is deleted automatically; the person (or, on request, a parent or guardian) can delete the account and its data at any time, and we will delete data of a child under 13 that we learn about when asked or when our reviewed process requires it. If you believe a child has given us data, contact ozrkapp@gmail.com.
If you are under 18, some laws give you or your parent or guardian additional rights over your data (for example to access, correct or delete it) and may require parental involvement or consent. You can use the deletion and export choices in section 11 at any time, or ask us at the address above. The app does not currently include a parental-consent process.
14. International transfers
Our providers may process data in other countries, including the United States. Where the law requires safeguards for transfers, we rely on the mechanisms the providers offer.
15. Changes
When this policy changes we publish a new version (shown at the top) and the app asks you to review and accept it before you continue. The version you accepted and the time are stored on your device.
16. Contact
OZRK LLC · PO Box 283, Greenland, AR 72737 · ozrkapp@gmail.com