Privacy

Privacy Policy

Effective date: October 2, 2026

This policy explains what the Fully Tuff app ("Fully Tuff", "we", "us") does with information when you use the app on iPhone and Apple Watch, or visit fullytuff.com. It is written to describe what the app actually does. If something here is unclear, email support@fullytuff.com.

What stays on the device

These are stored on the iPhone and are not sent to our servers unless a feature below says otherwise:

• Workouts, sets, exercises, workout notes, programs and planned workouts. These also sync through iCloud if iCloud is on (see iCloud sync).
• Profile details you enter, such as age, sex, height, body weight, activity level, training focus and nutrition targets.
• Coach conversations, including photos attached to them.
• Coach memory: the facts and summary the Coach keeps, such as goals, preferences and injuries you mention. Coach memory is kept in its own store on the device. It is not synced to iCloud and is excluded from device backups, so it does not move to a new phone.
• Progress photos, including physique photos you choose to keep. These are kept in a separate on-device store and are not synced to iCloud.
• The profile picture you set in the app.
• Workout titles the app writes for you. These are made on the device by Apple Intelligence where it is available, not by a cloud service.
• Apple Health readings, which are read live from Apple Health when the app needs them.

When data leaves the device

Signing in

You need to sign in to use Fully Tuff. You can sign in with Apple or with Google. We use a service provider for accounts. There are no Fully Tuff passwords.

• With Sign in with Apple, you can hide your email. If you do, we receive an Apple private relay address instead of your real email address. We do not request a name. We store an Apple token so we can revoke Sign in with Apple when you delete the account.
• With Google, we receive the email address, and Google also shares the name and profile picture link on the Google account, which our account provider stores with the account.

AI features

AI features include the Coach, plan and program building, program adjustments, suggested Coach prompts, weekly summaries, cloud reading of workout lines, workout insights, help reading imported workout files, and reading photos. They run only after you turn on AI features in the app, and you can turn them off at any time in Settings, under Coach.

When you use one, the app sends the information that feature needs to our server, which forwards it to an AI provider and returns the answer. Depending on the feature, this can include:

• Messages you type or dictate to the Coach, and workout lines to be read.
• Workout notes, read in the background to keep Coach memory up to date, for example when you mention an injury or a goal.
• Recent training history and programs.
• Profile details: age, sex, height, body weight, daily activity, training focus, and any nutrition target.
• Coach memory and the conversation summary. These are sent with each request so the Coach has context. Our server does not store them.
• If you import a workout file, the column names the app could not match and up to 12 sample rows from the file.
• Photos you attach (see Photos).
• A summary of recent sleep, recovery, body weight and nutrition from Apple Health, only if Share Health context is on.

We do not send your name, email address or location to AI providers. Anything you type, say, or include in a photo is shared with the provider, so please do not include medical records, government identifiers, passwords or other information you do not need for training.

For some requests from the Coach and other text features, our server includes a one-way hashed version of an internal account ID. The AI provider uses this to detect abuse. It does not contain a name or email address.

Our server does not store the content of AI requests or replies. It keeps usage records tied to the account, such as the date, the type of request, the model used, token counts and estimated cost, so it can enforce daily and monthly limits.

Photos

Photos leave the device in three cases, and only when you choose to send one:

• Logging from a photo. A photo of gym equipment or of a written workout is sent to be read. This requires AI features to be on. If the cloud cannot be reached, the app tries to recognize equipment on the device instead.
• Coach questions. You can attach up to five photos to a Coach question, such as a menu, a meal or a machine. This requires AI features to be on.
• Physique feedback. Up to five photos of you are sent to write feedback. Physique feedback is for people 18 and older, and it requires a separate agreement shown before the first photo is sent. The photos, your note, and the goal and focus areas you choose are always sent. When AI features are also on, profile details, program and Coach memory are included so the feedback fits your goals. The app does not yet have a switch to withdraw this agreement; you can stop using physique feedback at any time, and you can email us to withdraw it.

Our server passes photos to the AI provider and does not store them. For physique feedback, it keeps a record of each request (the date, whether it succeeded, how many photos were sent, the model used, token counts and estimated cost) so it can enforce a weekly limit and a daily limit on failed attempts. Photos are kept on the device only in a Coach conversation, or in progress photos when you choose to save them there.

Voice dictation and read aloud

• Dictation. When you dictate, to the Coach or on the logging Canvas with the Fully Tuff keyboard, the recording is sent through our server to our AI provider to be turned into text. This requires AI features to be on. The recording is deleted from the phone as soon as it has been used, and our server does not keep the audio or the text. In the Coach, the text appears in the message box and nothing is sent until you tap send. On the Canvas, the text becomes part of your workout, where the AI features above may read it. If the cloud cannot be reached, the app can transcribe on the iPhone using Apple speech recognition set to stay on the device.
• Read aloud. When you have a Coach reply read aloud with the Coach voice, the text of that reply is sent through our server to our AI provider to create the audio. This requires AI features to be on. You can pick a device voice in Settings instead, which works without a connection and sends nothing.
• Voice test on TestFlight builds. Beta builds include an optional on-device voice test. Starting it downloads a voice model from a model host, which receives your IP address and the request, but no content from the app.

Links in Coach questions

If you paste a link into a Coach question, the AI provider may visit that page to answer, and our server may request that site's public site map to help find the right page.

Cloud Backup

Cloud Backup is optional and happens only when you sign in and tap Back Up Now. A backup contains workouts, sets, workout notes, the Coach's notes on each workout, programs and planned workouts. It does not contain Apple Health data, profile details, Coach conversations, Coach memory or photos. Each new backup replaces the previous one. Backups are stored with our backup provider and sent over an encrypted connection.

iCloud sync

Workouts and programs sync between your devices through your own private iCloud account, using Apple's CloudKit. We cannot read this data. Apple Health data, Coach memory and photos are not synced to iCloud.

Anonymous usage analytics

We use an analytics provider to count which features are used. Events contain the event name, the app version, whether the build is a test build, a random ID created on this install, and short fixed values such as a count or a setting name. They never contain text you enter, such as workout notes, Coach messages or names, and they are not connected to an account. The provider does not build a profile for these events, and IP addresses are discarded. Analytics is on by default. You can turn it off in Settings, under Privacy.

Crash and error reports

In App Store and TestFlight builds, we use an error-reporting provider to collect crash reports, error reports and performance timings so we can fix problems. Reports include device and app details, such as the device model, iOS version and app version, and details of failed requests to our own server, with sign-in tokens and query strings removed. We do not attach an account, name or email to these reports.

Security checks and rate limiting

To keep our AI features from being abused, the app uses Apple's App Attest to prove that requests come from a genuine copy of the app. Our server stores the resulting key with the account. Our server also uses the IP address of each request to limit requests per minute. These IP records are removed within minutes.

AI providers

We use AI providers through their paid APIs for the Coach, plan and program building, workout insights, physique feedback, voice dictation, read aloud, and reading photos. We ask the provider that handles the Coach not to store responses for later retrieval.

Under their API terms, these providers do not use API data to train their models by default. Each provider may keep request data for a limited time for safety, abuse monitoring and legal reasons, under its own terms. We may change providers in the future, and if we do, we will update this policy and ask for your agreement again in the app where required.

Apple Health

If you connect Apple Health, the iPhone app reads workouts, sleep, resting heart rate, heart rate variability, body weight, nutrition (energy, protein, carbohydrates, fat and sugar), steps, and active and resting energy. The iPhone app does not write anything to Apple Health. It asks for permission to save workouts only because iOS requires it to start a workout on Apple Watch.

Health data is shown live in the app. It is never written to iCloud, never included in Cloud Backup, and never stored on our servers. It is sent to the Coach only if you turn on Share Health context in Settings, under Coach, which is off by default. You can change Apple Health permissions at any time in the Health app.

We do not use Health data for advertising or marketing, and we do not sell it or share it with data brokers.

Apple Watch

When you record a workout with the Fully Tuff app on Apple Watch, the watch reads heart rate, active and resting energy, and your Activity rings summary, and saves the finished workout, with its heart rate and active energy, to Apple Health. A summary is shown on the iPhone and is not stored or sent to our servers.

The website

fullytuff.com is hosted by our website host. It has no analytics, no advertising and no tracking scripts, and its fonts and images are served from the site itself. Like any web host, the host processes your IP address to deliver the page and keeps standard request logs under its own terms.

If you join the beta through the website, we store your email address, your first name if you give it, your main training goal, and the time you agreed to be contacted. We use them to manage beta access and to contact you about the beta, and we send a welcome email through our email provider. To limit repeated signups, we keep a keyed one-way hash of your IP address for up to 24 hours; it is not stored with your signup. We keep signup details for as long as the beta runs, or until you ask us to remove them by emailing support@fullytuff.com.

What we do not do

• We do not sell personal information.
• We do not show ads or share data with advertisers.
• We do not track you across apps and websites owned by other companies.
• We do not use Health data or photos for anything other than the feature you used.

Service providers

We share information with service providers only so they can operate the app for us. They provide accounts and cloud backup, AI features, anonymous usage analytics, crash and error reports, a voice model download on TestFlight builds, website hosting, beta signup storage, and beta email. Sign in with Apple, iCloud, Apple Health, TestFlight, and the App Store are part of the platform you use. Sign in with Google is available if you choose it.

Each provider handles data under its own terms. Fully Tuff is operated from the United States, and providers may process data in the United States and other countries.

Retention

• On the device: until you delete it in the app or delete the app.
• iCloud: until you delete the data in the app or in iCloud settings.
• Cloud Backup: until you replace it with a newer backup or delete the account.
• Account, Apple token, usage records, physique request records and App Attest key: until you delete the account.
• Content of AI requests on our server: not stored.
• Content held by AI providers: kept for a limited time under each provider's API terms, as described above.
• IP addresses used for rate limiting: removed within minutes in the app, and within 24 hours on the website.
• Website beta signups: for as long as the beta runs, or until you ask us to remove them.
• Analytics and crash reports: kept by our analytics and error-reporting providers for as long as needed to understand usage and fix problems, and not linked to an account.

Deleting data and other choices

• Delete the account: Settings, then Account, then Delete Account. For a guest account, use Delete Guest Backup. This deletes Cloud Backup, usage records, physique request records, the App Attest key, the Apple token (after revoking Sign in with Apple), and the account itself. Workouts on the device and in iCloud stay until you delete them. If a guest session has ended, the app cannot delete its backup; email us and we will.
• Delete workouts: Settings, then Your data, then Delete All Workouts, or Clear Workout History for a date range.
• Clear Coach history and memory: Settings, then Your data, then Clear Coach History. What Coach Knows shows the memory first.
• Delete progress photos: in the progress photos album.
• Export workouts: Settings, then Your data, then Export Data, as Markdown or CSV.
• Turn off AI features: Settings, then Coach, then Use AI features.
• Stop sharing Health context: Settings, then Coach, then Share Health context with Coach.
• Turn off analytics: Settings, then Privacy, then Share anonymous usage.
• Leave the beta mailing list: email support@fullytuff.com.
• Other requests: to ask for access to, correction of, or deletion of information we hold, email support@fullytuff.com. We may need to confirm the request comes from the account holder.

Children

Fully Tuff is not directed to children under 13, and we do not knowingly collect personal information from children under 13. Physique feedback is for people 18 and older. If you believe a child has given us information, email support@fullytuff.com and we will delete it.

Security

Data sent between the app and our servers is encrypted in transit. Sign-in tokens are stored in the iPhone Keychain, and provider API keys are kept on our server, never in the app. No system is perfectly secure, so we cannot guarantee absolute security.

Changes to this policy

We will update this page when the app's handling of data changes, and change the effective date above. For material changes, such as a new AI provider or a new kind of data leaving the device, we will tell you in the app before the change takes effect and, where required, ask for your agreement again.

Contact

Questions or requests about privacy: support@fullytuff.com

Fully Tuff is an independent app project based in Baltimore, Maryland.