Legal
Jason Abbamonte LLC, a Texas limited liability company doing business as swithAI ("swithAI," "we," "us," or "our"), is responsible for the personal data described in this policy. Last updated October 10, 2026.
swithAI is intended for adults aged 18 and older. By creating an account, you represent that you are at least 18 years of age.
We do not knowingly collect personal information from anyone under 18. If we become aware that we have collected information from a person under 18, we will delete that account and its associated data.
If you believe a person under 18 has provided us with personal information, contact us at support@getswith.com and we will take steps to remove it.
Profile information you provide: your display name, age, city, language preference, fitness level, fitness background, fitness goals, activity level, dietary preferences, low-impact preference, and, if you choose to set it, a body type for the calorie estimate. That last choice is optional and is used only to select which of two calorie formulas the app runs; it is offered as Female, Male, or Prefer not to say, and skipping it or choosing Prefer not to say keeps the app on its general formula.
Wellness data you log: workout logs (exercises, sets, reps, weight, and self-reported effort ratings), daily food and beverage intake, macro totals (including fiber, sugar, and added sugar), hydration logs, activity logs, mood entries, and sleep records.
Supplement logs: the name, dosage, serving size, schedule, frequency, and any notes you record for supplements you choose to track. These entries are yours alone — we do not verify, endorse, or review them, and no healthcare professional sees them.
Health readiness answers: whether you have medical conditions that affect exercise, and whether you are currently under medical supervision for activity restrictions. This is the most sensitive information we collect. It is used to tailor exercise suggestions — for example, to offer low-impact alternatives — and is stored with the rest of your profile.
Photographs: images you capture or select for food logging and grocery item recognition. See 'Third-Party AI Processing' below — these leave your device.
Account identifier: a Firebase user identifier.
Purchases: swithAI is offered through two subscriptions, swithAI and swithAI Plus, bought through the App Store or Google Play. The purchase is processed by Apple or Google, and we never receive your payment card details. We use RevenueCat to verify which of the two subscriptions, if either, your account holds. RevenueCat receives your account identifier and the purchase records the store issues for it — the product, its dates and its status — together with the routine technical data needed to process a request (device type, operating system, app version and IP address), and we read that status from RevenueCat to decide what the app shows you. If you never subscribe, no purchase record exists for you.
Favorites and app preferences: favorite exercises, favorite cardio activities, accent color, daily water goal, and custom macro targets.
Goals and plans: if you set a goal on the Goal screen, we store the goal record — its type, the target amount and direction, the start and target dates, the pace you chose and its rating, the goal's parameters, and the custom nutrition targets the goal replaced, so they can be put back when it ends — the plan built from it (the daily calorie and macro targets, the weekly training, activity and wellness targets, and the reason for each revision), each day's skip, replace, move, modify and mark-complete choices, and each week's summary decision. None of these records contains a value read from Apple Health or Health Connect: the health figures the Goal screen shows and the readiness comparisons it uses are read and kept on your device only, as described under Readiness data below. The day-by-day completion record, the meals suggested for each day, and the per-day health summaries the Goal calendar shows are kept only on your device and are not sent to our application backend.
Apple Health and Health Connect data: if you grant permission, the app can read from the health platform on your device. On iOS, the app can read ten types from Apple Health: your daily step count, active energy, water intake, sleep, your most recent weight and height, and the four readiness types described below. On Android, the app can read the same ten types from Health Connect. Permission is asked for each type separately, and the app reads only the types you allow. On Android, Health Connect also limits how far back an app can read: it returns roughly the 30 days before you first granted permission and everything recorded after that, so any history the app shows over a longer window fills in over time from that date. For sleep, the app reads the night's recorded sleep stages and stores both the total hours slept and the minutes in each stage — deep, REM and core — in your account records, and shows that breakdown in the app. Values read this way are stored in your own account records alongside the data you enter by hand, and each one is labelled as coming from the health platform so you can tell the two apart. The app never writes anything back to Apple Health or Health Connect.
Body measurements: your weight and height, if you choose to provide them. Both are optional, and the app works without them. You can type them into your profile on any platform. On iOS you can instead have the app read the most recent weight and height recorded in Apple Health, and on Android the most recent recorded in Health Connect; it does so only when you tap the control on the profile screen, and only if you allow those two types when the health platform asks. They are stored with the rest of your profile in metric units and shown to you in the units you entered. We use them in four ways today. Your weight sets your daily water target. Your weight, height and age, together with the body type choice described above, set your daily calorie target through the Mifflin-St Jeor equation when all four are present; if any is missing, the app uses its general formula instead. Your weight also scales the calorie burn estimates shown on the Activity page. Your weight and height together are shown as a body mass index on the Data tab of the Activity Coaching screen; that figure is calculated on your device from the two numbers you provided and involves no new collection. The app does not currently use your weight or height to estimate the energy you expend during runs, walks, hikes or rides recorded on the Activity Coaching screen.
Location and recorded runs: if you grant location permission, the app reads your device's precise location in two situations only — while you are recording a run, walk, hike or ride on the Activity Coaching screen, and when you tap the locate control to center the map on where you are. When you save a run we store its route as a series of coordinates with timestamps, together with the start and end time, duration, distance, and activity type. The app asks for 'While Using the App' permission only and never accesses your location in the background; recording stops when you leave the tracking screen.
Readiness data from Apple Health and Health Connect: if you allow them, the app can read four further types: heart rate, heart rate variability, resting heart rate, and workouts recorded by any app, from Apple Health on iOS and from Health Connect on Android. They are used to show the Readiness section on the Data tab of the Activity Coaching screen (your most recent values, your own 7-day and 28-day averages, and how the latest value compares with them) and the heart rate recorded during a finished run. Every value is read from the health platform on your device each time it is shown, and any average is calculated there. The raw readings and the averages are not uploaded to or stored on our application backend. On Android, because of the history limit described above, the 7-day and 28-day averages can take up to four weeks after you first grant permission to fill in. The Readiness section also shows your sleep; that comes from the sleep reading described above, whose nightly total is stored in your account records like your steps, active energy and water intake. You control this access through the health platform: the permission sheet asks for each type separately, and the app reads only the types you allow. On iOS you can turn any of them off at any time in the Health app under Sharing, Apps & Services, swithAI, or in iOS Settings under Health, Data Access & Devices, swithAI. On Android you can turn any of them off at any time in Health Connect under App permissions, swithAI; the Readiness section also offers a button that opens that screen. Turning a type off stops the app reading it, and because nothing read this way was stored, there is nothing of it to delete. The app does not read body-composition data such as body fat. The only body measurements we hold are the weight and height described above, and only if you choose to provide them.
For clarity, and so this policy and our App Store privacy labels describe the same practices, here is how the above maps to Apple's categories:
• Contact Info — email address, used for account sign-in and support, and the display name you choose for your profile
• Health & Fitness — workouts, nutrition and hydration logs, supplement logs, mood, sleep, activity, health readiness answers, and your weight and height if you provide them. The heart rate, heart rate variability, resting heart rate and workout data the app reads from Apple Health on iOS stays on your device and is not collected under this or any category
• User Content — photographs you capture for food and grocery recognition
• Identifiers — Firebase user identifier, your app account identity, and a push notification device token that Apple and Google issue for your device (obtained by Firebase on your device; we do not receive or store it). The account identifier is also passed to RevenueCat to look up your subscription
• Purchases — the swithAI and swithAI Plus purchase records the App Store or Google Play issues (product, dates and status), held by RevenueCat and linked to your account; we never receive payment card details
• Precise Location — your device's location while you record a run or tap the locate control, and the route coordinates of the runs you save, linked to your account
• Usage Data — screen views, feature interactions, and session duration
• Other Data — your age, and the optional body type choice described above, used to set your daily calorie target
• Crash Data — crash reports sent to Firebase Crashlytics when the app crashes, used to find and fix crashes. Not linked to your identity: we never attach your account, your name or any of your logged data to a crash report
We do not use any of these categories for tracking across apps or websites owned by other companies, and we do not use them for third-party advertising.
We collect usage data to help improve the app: screen views, feature interactions, and session duration.
This data is sent to our own application backend (the Internet Computer canister described under 'Where It's Stored'), not to a third-party analytics vendor such as Google Analytics, Firebase Analytics, or a mobile attribution SDK. No advertising or tracking network receives it. You can opt out of usage analytics at any time in Settings.
Your data is used to personalize your wellness experience — to generate workout plans, nutrition guidance, meal plans, and activity recommendations tailored to your profile and goals, and, from the body measurements you choose to provide, to set your daily water target from your weight, to set your daily calorie target from your weight, height, age and body type choice when all four are present, and to scale the calorie burn estimates on the Activity page from your weight — from the readiness types you allow in Apple Health on iOS or Health Connect on Android, to show your readiness, your trends against your own averages and the heart rate of a finished run, all on your device — to show your position on the map and to record and replay the routes of runs you save, and to operate your account and support requests.
We do not use your data for advertising, for cross-app tracking, or for building profiles for any purpose beyond delivering the app's features to you.
Several features send your data to OpenAI for processing. This is not limited to training recommendations. The features that transmit data are:
• Training adaptations — your exercise history, sets, reps, weight, and self-reported effort ratings
• Food photo recognition — the photograph itself
• Grocery item photo recognition — the photograph itself
• Free-text nutrition estimation — the food or meal description you type
• Meal planning — when you generate a meal plan, your fitness level, fitness goals, dietary preferences and daily calorie target
PHOTOGRAPHS LEAVE YOUR DEVICE. When you use food or grocery photo recognition, the image you capture or select is transmitted off your device and processed by a third-party AI vision model in order to identify the item. If a photograph contains anything you do not wish to transmit — people, documents, or your surroundings — do not use the photo recognition features for that image; you can always enter the item by text or search instead.
Data is transmitted for the sole purpose of generating a response to your request. We do not use it to train any AI model of our own. We do not control OpenAI's handling of data submitted to their API, and we make no representation here about their retention or model-training practices; please review OpenAI's privacy policy directly at https://openai.com/policies/privacy-policy.
We use Firebase Authentication, a service provided by Google LLC, to sign you in.
If you sign in with Apple, Firebase receives your Apple user identifier and the email address Apple releases to us. If you choose Apple's 'Hide My Email' option, that will be a private relay address rather than your real one, and we will only ever see the relay address. If you sign in with email and password, Firebase receives your email address and your password credentials; we never see or store your password ourselves.
Firebase issues a user identifier that we store with your profile so your account can be recognized across sessions and devices.
Notification registration: the Firebase software included in the app registers your device with Apple's push notification service and Google's Firebase Cloud Messaging when the app starts. This does not show a permission prompt and does not allow the app to display notifications; the app does not currently send push notifications. As part of that registration Google receives a device token that identifies this installation of the app. We never read that token, and it is not sent to or stored on our application backend.
Google acts as a service provider for these functions. See Google's privacy policy at https://policies.google.com/privacy and Firebase's privacy documentation at https://firebase.google.com/support/privacy.
If you create an assistant API key in Settings, under Data & Privacy, Connect your AI assistant, anyone holding that key can do the following in your account: add entries (workouts, foods, cardio, activity, mood, sleep and mindfulness sessions), read back your entries of those types for a given day, and delete them. Adding activity for a day replaces that day's step and active-minute totals. Entries added this way are stored, shown and deleted like the entries you log yourself. A key can only reach your own account.
The key is meant for an AI assistant service you choose. That service's handling of your data, including the key, what you tell it and anything it reads back from swithAI, is governed by its own privacy policy, which we do not control. swithAI does not send your data to it on its own; it only answers requests made with your key.
Keep your key private. You can revoke it at any time in the same place in Settings, and a revoked key is refused immediately.
Your wellness and profile data is stored on the Internet Computer blockchain through canister smart contracts. This means it is decentralized and not held on a traditional centralized server. The runs you save are stored there too: the route coordinates and timestamps, start and end time, duration, and distance of each one. So are your goal and its plan, your day-by-day plan choices, and your weekly plan decisions; none of them contains a value read from Apple Health or Health Connect.
Your data lives in the canister's state on the Internet Computer. When you delete your account, or delete an individual item such as a saved run, it is removed from that current state, as described below. The nodes that run the canister keep older blocks only briefly, as part of operating the network, and there is no permanent ledger copy of canister data.
On iOS, the app generates a cryptographic key pair on your device the first time it runs and stores it in the operating system's app preferences storage. This key is what authenticates your device to the application backend — in practice it functions as the credential for your account data.
The key is held on your device. Deleting the app, erasing the device, or losing the device may mean the key is no longer available. We do not hold a copy of it and cannot reconstruct it for you.
We do not sell or rent your personal data to anyone, and we do not share or transfer it to any third party for their own commercial purposes, for advertising, or for cross-app tracking.
We do share data with a small number of service providers, strictly so they can perform a function of the app on our behalf. Each one receives only what that function needs:
• OpenAI — the AI processing described above. Receives the photographs you capture for food and grocery recognition, the food or meal text you type, the workout, dietary and profile data used for training adaptations, and, when you generate a meal plan, your fitness level, fitness goals, dietary preferences and daily calorie target.
• USDA FoodData Central — food and nutrition lookup. Receives the food search text you type. It does not receive your identity or any other profile data.
• FatSecret (platform.fatsecret.com) — food search and nutrition lookup. Receives the food search text you type and the identifiers of the foods you open. It does not receive your identity or any other profile data.
• Google LLC (Firebase and Google Maps) — authentication, crash reporting (Firebase Crashlytics), push notification registration (Firebase Cloud Messaging), and the map on the Activity Coaching screen (Google Maps SDK). Receives your sign-in identifiers and the device token described under 'Account, Sign-In & Notifications'; a crash report when the app crashes, on iOS and on Android alike, with technical details about the crash and your device — the stack trace, the device model, the operating system version and the state of the app at that moment; and, whenever the map is on screen, the requests needed to draw it: our Maps API key, the app's identifier, and the area of the map being shown. While you record a run the map follows you, so that area reflects where you are. A crash report carries none of your account details, none of your health or activity data and no location, and we attach no identifier of our own to it. The route line is drawn on your device, and your saved routes are stored only on our application backend, not sent to Google. Google's own privacy policy applies to the map: https://policies.google.com/privacy.
• RevenueCat — subscription verification for swithAI and swithAI Plus. Receives your account identifier and the purchase records the App Store or Google Play issues for your subscription: the product, its dates and its status. Like any service the app calls over the internet, it also receives the routine technical data needed to process a request, such as your device type, operating system, app version and IP address. It does not receive your payment card details, which stay with Apple or Google, and it does not receive any of your health, activity or nutrition data. RevenueCat's privacy policy is at https://www.revenuecat.com/privacy.
That is the complete list of third parties that receive your data, and for each one the complete description of what it receives; where a provider receives data through more than one path, as Google does through Firebase and through the map, every path is listed. Each provider handles what it receives under its own privacy policy, which we do not control.
An AI assistant service you connect with your own assistant API key is not on this list: it reads your data only through requests made with your key, as described under 'AI Assistant Connections'.
Some features involve no third party at all: for example, the workout recommendations the coach offers on the Training screen are computed entirely on your device; nothing about them is sent to anyone.
You have the right to request deletion of your account and all associated personal data at any time through the app settings or by contacting us at support@getswith.com. We will process deletion requests within a reasonable timeframe.
You may also request a copy of the data we hold about you, or ask us to correct information that is inaccurate. Deleting your account removes all of your data from our application backend, including every run you have saved and its route, and your goal, its plans, your plan choices and your weekly plan decisions; the copies of those goal records kept on your device are removed at the same time. The one exception is our free-trial registry: we keep a record of your email address and account identifier so that a free trial cannot be taken again. Deletion does not retroactively affect data already transmitted to a service provider listed above, which is governed by that provider's own policy.
You can also delete individual runs at any time from the Routes tab of the Activity Coaching screen, without deleting your account.
Deleting your account does not cancel a swithAI or swithAI Plus subscription. The subscription belongs to your App Store or Google Play account, so cancel it there; see 'Subscriptions' in our Terms of Service.
Apple Health and Health Connect access is separate from your account. You grant and revoke each type in the Health app or in iOS Settings on iOS, and in Health Connect under App permissions on Android, as described under 'What We Collect', and the heart rate, heart rate variability, resting heart rate and workout values the app reads there are never held on our application backend, so there is nothing of them to delete from it. The steps, active energy, water intake, and the nightly sleep totals and per-stage minutes synced from the health platform are stored in your account records and are deleted with it.
The data controller for the purposes of this policy is Jason Abbamonte LLC d/b/a swithAI, a Texas limited liability company.
To exercise any right described above, to ask how your data is handled, or to send us a privacy notice, contact us at support@getswith.com.