Your data, your choices
Sweat AI is an independently operated workout app based in the United States. This policy explains how the Sweat iPhone app and its website handle information. Contact support@sweat-ai.com with privacy questions or requests.
The initial service is intended for adults aged 18 or older in the United States. We do not knowingly collect information from children. Contact us if you believe a child has provided personal information.
Workouts on your device
The app keeps workout names, dates, exercises, sets, weights, repetitions, plans, chat messages and activity records locally. Walk/run records may include steps, duration, distance, pace and precise routes. Signed-in accounts have separate local histories; signing out hides an account’s history rather than deleting it.
Local commands can work without cloud AI. Signing in does not enable cloud AI sharing or workout backup. Your device’s backup services may include app data according to your device settings.
Account and profile
Supabase processes your email address, account identifier, authentication/session information and service-access records. Resend delivers sign-in codes and processes the email address, email content and delivery records. Account services operate even when cloud AI is off. Session credentials are kept in the device Keychain and are excluded from workout exports.
The name and email you enter at account creation, optional contact phone, and saved profile details are stored in your Supabase account. Profile details can include training goal, experience, age, body weight with lb/kg units, usual training days and lifestyle. The contact phone is not currently used for SMS sign-in.
Tell Us About Yourself and the optional guided interview suggest supported details on the device. They are not a live conversation with a cloud model. You can type, skip questions or use on-device-only Apple dictation where available; spoken questions use Apple speech synthesis. Only fields you review and explicitly save go to Supabase. If you save routine or food notes in the lifestyle field, that text becomes part of your saved profile; it does not create meals or workouts. Unsaved answers are transient, and no separate interview transcript or audio recording is retained by Sweat. These full profile fields are not automatically included in AI requests or workout backups. Clear optional fields and save to remove them, or export a separate unencrypted profile JSON file.
A profile photo selected through Apple's photo picker, or a built-in avatar, is saved only on this device, separately for each account or device-only history. The app prepares a smaller image without the source photo metadata; it does not identify your face or generate an AI image. Profile pictures are excluded from workout exports, cloud workout backup and the app's device backup. Choose a built-in avatar to replace a saved photo. Your original photo in Apple's Photos library is not deleted by Sweat.
Journal
Journal entries contain the dates, titles and text you save, with optional meal/activity descriptions you explicitly review. Suggestions use on-device phrase matching, not Cloud AI; they do not infer calories, dietary adequacy or completed workout measurements. Journal records stay in separate account/device-only files on this device. They are excluded from workout exports, cloud workout backup and device backup, and are not automatically included in AI context. Apple dictation processing, if used, is described below.
You can edit or delete entries and export a separate unencrypted Journal JSON file. Export it before removing the app if you want to keep it. Clearing workout history is not a Journal export. Deleting the account on this device or using the relevant testing reset removes its local journal; exported copies remain wherever you saved them.
Floating assistant and Recent Chats
A microphone inside a text/search field dictates into that field without sending it. The floating assistant lets you review and edit a command before explicitly sending it. Recording or pressing Stop alone does not execute a command. Supported local settings commands can run on the device; requests requiring Cloud AI follow the separate AI-sharing choice below.
Profile → Recent Chats saves submitted floating-assistant text, responses, dates, outcomes and retry/Undo/Redo status locally, separately for each account and device-only history. It does not retain raw audio or field/search-bar dictation as assistant interactions. The local receipt archive is excluded from workout exports, cloud workout backup and device backup. Workout commands may also appear in ordinary workout chat, which follows workout export and optional backup choices. A command's prior AI transmission is not undone by deleting its local receipt.
Recent Chats stays until you delete entries or remove that account's local data. It has a 1,000-interaction limit; when full, export and remove older entries to continue. You can export it separately. Deleting a receipt does not undo its workout or settings change. Undo/Redo for supported changes is separate from deleting history and does not recall information already sent to providers.
Optional local exercise coaching
Progression & Coaching can use earlier matching exercise sets and optional goal, effort and readiness answers to show an editable planned target. These answers stay in the coaching screen and are not saved or sent to Cloud AI. An explicitly saved target is part of the workout and follows the same storage, export and optional backup choices as other planned workout data. The feature does not assess medical conditions or guarantee a progression outcome.
Optional Nutrition & Recovery check-ins record your reported sleep hours, energy, soreness and nutrition-routine consistency for the preceding seven days. All fields are optional. You explicitly choose to save a check-in with its workout, and separately choose to use it for local coaching. Check-ins stay with that account’s workout history until removed or the workout/history is deleted. They are included in Files exports and optional cloud backups (including automatic backups already enabled), but are not included in automatic Cloud AI context. Removing a local check-in does not erase previously exported files or existing cloud copies immediately; use the existing backup controls for those copies. Older check-ins remain historical records, not evidence of current readiness. The app does not infer food intake, dietary adequacy or medical readiness from these answers or missing entries.
Optional cloud AI
Cloud AI Sharing is off until you enable it for your account in Profile → Account → Cloud Settings → AI Data Sharing. Requests requiring cloud AI send your message and recent workout context through Supabase to OpenAI to interpret logging, answer questions or suggest workouts. Context can include exercise names, sets, weights, reps, muscle groups and a recent workout summary.
Optional AI Preferences are separate from your full profile. If you explicitly save preferences with their use enabled, capable app versions can include your selected reply style, trainer tone, equipment, session length, goal, experience and training days in future Cloud AI requests through Supabase to OpenAI. AI sharing must also be enabled on the device. Age, body weight, lifestyle and contact details are not automatically copied into these preferences. You may copy supported training details into the preference form, review and save them, change or remove saved preferences, or export them separately. Chat messages do not silently become saved preferences. Turning use off and saving, or removing the preferences, stops their inclusion in future requests; it does not withdraw previously transmitted data. Unfiltered trainer tone requires a separate strong-language opt-in; it changes reply style, not data access or workout safety rules.
Optional daily workout guidance lets you review a dated summary before explicitly choosing Ask AI Using This Summary. The summary includes a bounded sample of saved exercise names and logged-set counts, and manually reported activity types, dates, duration and distance. Your optional considerations are sent with that request through Supabase to OpenAI; enabled reviewed AI preferences may also be included. Reviewing the page alone sends nothing. This feature excludes planned-only drafts, imported Health records, steps, heart rate, precise routes, workout notes/chats, Journal entries and saved recovery check-ins from its summary. Guidance and unsent considerations are transient on the device; opening a plan preview explicitly creates an ordinary saved draft plan. Prior provider retention still applies to requests you chose to send.
Recorded GPS routes, imported Health metrics and microphone audio are excluded from automatic AI context. Text you choose to type or dictate can itself contain personal or health information. Review it before sending. Disabling sharing prevents new submissions; requests already sent may finish.
The backend uses OpenAI’s Responses API with response storage disabled (store=false). This is not a zero-retention guarantee. OpenAI’s default security/abuse-monitoring retention can include prompts and responses for up to 30 days, with legal and safety exceptions. Our OpenAI organization’s optional sharing of API inputs/outputs, model feedback and evaluation data is disabled. Under OpenAI’s API data policy, content is not used to train its models unless sharing is enabled. Security and abuse monitoring still apply. Provider processing is described in OpenAI’s data controls. We do not sell your workout content or use it for advertising.
Optional cloud backup and exports
Cloud Workout Backup is a separate opt-in, off by default. Enabling it lets you upload a snapshot of your current history to Supabase, including chats, plans, lifting records, imported Health information, steps, heart rate and precise routes when present. Optional automatic backup runs while the app is active. Backup content is not sent to OpenAI for backup processing.
Journal, the separate Recent Chats archive and profile pictures are not part of this workout snapshot. Full profile and AI-preference exports are separate from workout exports.
The cloud copy is the latest snapshot, not a version history or automatic merge across devices. Restore requires an empty local history. Cloud communication uses HTTPS; backup is not end-to-end encrypted, so the service operator and provider can access data as needed to operate the service.
Turning backup off stops new uploads but does not delete an existing copy or recall a request already in flight. Use the cloud-copy deletion control to remove the stored snapshot. JSON exports are unencrypted files saved to a location you choose; protect or delete those copies separately.
Health, Motion, location and voice
Apple Health: with permission, the app reads supported workouts, steps, distances, heart rate and workout routes. Optional automatic import checks recent supported workouts while the app is active. It does not continuously monitor an Apple Watch. Imported data stays local unless you export it or separately enable cloud backup. We do not use Health information for advertising, data brokerage or marketing.
Motion & Fitness: the iPhone pedometer can count steps during walks/runs you explicitly start. Permission setup can issue a short query to trigger the iOS permission prompt; that setup count is not saved. This feature is separate from importing all-day steps through Health.
Location: GPS recording requires a started session and iOS permission and may continue with the screen locked. Pause or finish to stop recording. Turning Allow GPS Recording off pauses recording; enabling it does not start tracking. Apple Maps receives map-service requests under Apple’s policies.
Voice: voice input starts when you tap the microphone and grant microphone/speech permissions. Apple Speech may process audio using Apple services. Sweat AI does not send microphone recordings to Supabase or OpenAI; the resulting text follows your message-sharing choices. Manage permissions in iOS Settings and Health access in Apple Health.
Web workout viewer
At sweat-ai.com/workouts you can sign in with the same verified email account as the iPhone app. Your email and verification code go directly to Supabase. The page keeps its sign-in session in memory, not persistent browser storage; leaving or reloading the page, or 15 minutes of inactivity, clears it. Sign Out clears the page immediately and requests server-side sign-out for that browser session. If offline, server-side revocation cannot be confirmed. Provider token-expiry rules still apply.
Loading a backup is a separate action with a notice first. It downloads the full latest cloud copy into the browser tab, which may include saved chats, imported Health information and precise routes. This initial viewer displays exercise/set details and basic activities only; chats, notes and routes are not shown. Use a private device and close the page when finished. The page does not send backups to AI, edit workouts, upload, restore or delete data. It labels the cloud copy's saved time; it is a snapshot rather than live synchronization. No new advertising or analytics integration is added. The hosting/network providers described below process ordinary web requests.
Operations and service providers
Supabase, OpenAI, Resend and Apple provide the features described above. The Supabase project hosting the app database is in East US (Ohio); the OpenAI project uses standard retention and global processing. Resend’s configured sending region is North Virginia; this does not guarantee all provider processing stays in that region. Service providers can process IP addresses, approximate location inferred from network addresses, timestamps, request identifiers, security events and errors. Supabase gateway logs can include network-derived country/city/region information for service operation and security; this is separate from GPS route recording. App/backend diagnostics are designed to log timing, action categories and error codes rather than workout messages, credentials or routes. There is no third-party advertising or cross-app tracking integration in this version. We use crash reports Apple makes available through TestFlight or App Store Connect to troubleshoot problems. Apple controls those reports under its settings and policies; no additional crash-reporting SDK is added by Sweat.
Information may be processed in the United States and other countries where providers operate. We use information to deliver requested features, authenticate users, enforce access and spending limits, resolve support requests and protect the service. Information may also be disclosed when required by law or to protect rights and safety.
The website has no analytics or advertising integration and no contact form. Its workout viewer has first-party sign-in/display scripts; page code does not persist account tokens or set account cookies. The website is hosted through OpenAI Sites and Cloudflare infrastructure, which process ordinary web-request information to deliver and secure the pages. Support email is forwarded by Cloudflare Email Routing to the operator’s Google Gmail mailbox. Emailing support shares your address and message with the operator, Cloudflare and Google. Email transport is not guaranteed to be encrypted end to end. Please do not send sign-in codes, passwords or unnecessary health or route information.
Optional issue reports
Profile → Report an Issue prepares a report locally with the app/iOS version and details you enter. You can separately choose a related workout’s exercise names/sets and individual chat messages. Routes, imported Health records, nutrition/recovery check-ins, profile details and credentials are not automatically attached. Your selected chat and written explanation may still include personal information. Common credential/contact patterns are redacted best-effort; review the exact report before sharing. Nothing is sent automatically or to Cloud AI by this feature.
You can save an unencrypted JSON file or compose an email to support@sweat-ai.com using your configured Mail account. You control the final send. Your sender address and attachment are then processed by the support email providers described above. Copies in Files, drafts and sent email are separate from workout/account deletion. The operator can inspect basic account/contact and service-status fields for support; the owner account overview excludes workout/backup contents and records accesses through that report. Submitting a report does not enable silent sign-in to your app or access to your whole device.
Retention, deletion and requests
Local history remains until you delete it or remove app data. Cloud account/profile records and the latest backup remain until you remove the relevant data or delete the account. No automatic inactivity deletion is currently implemented. Provider security logs, backups and legally required records may outlast deletion of live data; deletion does not instantly purge every provider copy.
Resend currently describes 30-day email/log retention on its standard plans and seven-day infrastructure backups. Supabase dashboard log-availability windows depend on the plan; they do not define how long live account data or your saved cloud copy exists. Our last provider configuration review did not identify enabled project-level scheduled backups, point-in-time recovery or log drains. Provider infrastructure/security retention can differ from the logs visible in our dashboard. OpenAI’s retention is described above. Support reports and attachments are accessed by the operator and deleted within 90 days after the issue is resolved. You can ask for deletion sooner. This cleanup is handled manually; no automated expiry service is currently implemented. Website hosting and email providers also apply their own security and operational retention practices.
- Delete local history: Profile → Workout Data → Delete This History removes only the open history on this device.
- Delete a cloud backup: use the cloud-copy deletion control under Cloud Backup and Restore. Local history remains.
- Delete your account: Profile → Account → Delete Account. Verify a fresh email code in the deletion page, then confirm deletion. Successful deletion removes the cloud login, associated profile, AI preferences, beta-access records and cloud backup, signs you out and returns to Welcome. It also cleans up that account’s local workouts, Recent Chats, Journal, profile picture and credentials on this device. Partial failures are reported.
Removing the app or choosing a local-only testing reset does not delete your Supabase account or cloud copy. Testing resets explain which local histories/settings they remove; deleting the account uses the same verified deletion process. Apple Health records and system permission grants are managed separately.
Account deletion does not erase exported files, device backups or local copies on other devices. Remove those separately. Empty local store files and non-content preference/ownership metadata may remain. Shared aggregate cost counters may remain without the deleted account’s personal usage records.
Email support@sweat-ai.com to request access, correction or deletion, or if you cannot reach the in-app controls. We may verify account ownership before acting. Do not send your password or sign-in code.
Policy updates
We will update this page when practices change. Material changes to cloud AI sharing require a renewed in-app opt-in. This policy describes the current beta and does not imply that every planned feature is available. Provider privacy information: Supabase, Resend, OpenAI, Cloudflare, Google and Apple.