FitnessFeed

Privacy Policy

The short version

FitnessFeed lets you share health numbers with friends, and you decide what gets shared. Here is what that means in practice:

The rest of this page explains each of these in detail.

Who we are and how to reach us

FitnessFeed is made by Derrick Michael Guthier, an individual developer. In this policy, "we" means Derrick Michael Guthier.

For any question, request, or concern about your privacy, email privacy@fitnessfeed.net.

What we collect

This table lists every kind of information FitnessFeed keeps, why, and where it lives. "Our servers" means the hosting service we use, described under "Who can see what."

Information Why we need it Where it lives
Email address and password To create and secure your account, and to send account emails such as password resets Our servers. Your password is stored in scrambled form and we can't read it
Display name and username So friends can find and recognize you Our servers
Age confirmation To confirm you are 18 or older Our servers keep a note of when you confirmed it. Your date of birth is checked on your phone and never kept
Health numbers you choose to share: weight, calories and nutrients, active calories, exercise minutes, last workout, sleep, and your logging streak To show them to your friends, at the level you choose for each Read from Apple Health on your phone. Only the version you chose to share is sent to our servers
Goal details: target weight, starting weight, dates, and whether you are cutting, bulking, or maintaining To track your progress and show it to friends at the level you choose Our servers
Sharing settings To remember what you decided to share Our servers
Posts, comments, and reactions So you can interact with friends Our servers
Challenges: names, members, and your daily scores To run challenges between friends Our servers
Progress photos and captions For your private timeline, and to share a photo if you choose Our servers, in private file storage
Friend connections and blocked people To show your friends and to enforce blocks Our servers
Notifications To show alerts inside the app Our servers
Reports you send, or that are sent about you To keep the community safe Our servers. Only we can see them
Calorie coach details: height, age, sex, activity level, and your plan To work out your daily calorie target Only on your phone. Never sent to our servers
Saved meals, and the names you give meals So you can log a meal again with one tap Your phone and, if you use iCloud, your own iCloud account. Never sent to our servers
Food searches and barcodes you scan To look up nutrition information Sent to our server and on to USDA FoodData Central, a U.S. government database. We don't store them
Basic technical information, such as your IP address and device type To keep the service running and secure Our hosting provider's logs

Your health data

Your health data stays on your phone unless you choose to share it, and you control each kind separately.

What we read from Apple Health. With your permission, FitnessFeed reads your weight, height, date of birth, biological sex, food and nutrition, active energy, exercise minutes, workouts, sleep, and steps. Weight and nutrition you log inside FitnessFeed are saved back to Apple Health. You can change or withdraw this permission any time in your iPhone's Settings.

What leaves your phone. For each kind of data, you pick a sharing level, such as "off," "trend only," or "exact." The app works out the version you chose to share and sends only that. Your sleep score is calculated on your phone. If you set something to "off," nothing about it is sent.

Changing your mind. When you lower a sharing level or turn something off, the app replaces what we hold with the new, smaller version the next time it sends an update, so friends stop seeing the old value.

Challenges. If you join a challenge, the app sends your daily score for that challenge's measure (for example, steps) for the days the challenge runs.

What we never do with it. We don't use Apple Health data for advertising or marketing. We don't sell it, and we don't share it with advertisers, data brokers, or insurers.

The calorie coach. The coach works out your target on your phone. The details it uses, and your plan, are not sent to our servers.

Meal names and saved meals. Names you give your meals are saved with the entry in Apple Health on your phone. Meals you save so you can log them again are kept on your phone and, if you use iCloud, in your own iCloud account. We never receive them, and friends never see them.

Food search and barcode scanning. The camera is used only on your phone, to read a barcode. Pictures are not saved or sent anywhere. The words you search for, or the number in a barcode you scan, go to our server, which asks USDA FoodData Central for nutrition information. We do not store what you search for or scan.

Progress photos

Progress photos are private by default. Only you can see a photo until you decide to share that specific photo.

Photos are for people 18 and older.

Who can see what

Who What they can see
Your friends Only the health numbers, goal details, and photos you choose to share, at the levels you set, plus the posts you make
Anyone signed in to FitnessFeed Your display name and username, so they can find you and send a friend request. Nothing else
People in a challenge with you Your name and your daily score for that challenge
People you block Nothing. They can't see your updates, send you requests, or comment on your posts, and they are not told
Our hosting provider The information stored on our servers, only to run the service for us
Apple What Apple already handles: Apple Health on your phone, and the App Store and TestFlight

Service providers. We use Supabase to host our database, sign-in, and private file storage, in the United States (East US, North Virginia). We use an email service to send account emails such as password resets. When you search for a food or scan a barcode, our server asks the U.S. Department of Agriculture's FoodData Central database for nutrition information. USDA receives the search words or barcode number, but not who you are. These providers handle information only to provide their service to us, under their own terms and privacy policies.

Us. The person who runs FitnessFeed can technically access information stored on our servers. We only look at it to fix a problem, to review a safety report, or to meet a legal duty.

Legal and safety. We may share information if the law requires it, or if we believe it is needed to prevent serious harm to someone.

What we do and don't do with your information

We use your information to:

We don't:

FitnessFeed has no ads and no third-party analytics or advertising tools today.

If this changes. If we ever add ads, analytics, or paid features, we will update this page and tell you in the app before the change takes effect. Health data from Apple Health will never be used for advertising. If we offer paid features, Apple would handle the payment, and we would only learn whether your subscription is active.

How long we keep information, and your choices

We keep your information while your account exists. You can control it at any time:

Depending on where you live, such as California or the European Union and United Kingdom, you may have legal rights to access, correct, delete, or receive a copy of your information. Email us and we will honor them.

Safety: reports and blocking

Because people share photos and comments, we give you tools to report and block, and we review reports.

Security, age, and changes

Security. Information is sent over encrypted connections. Our database enforces the sharing rules itself, so a friend's app can't read what you haven't shared, and photos sit in private storage. No system is perfectly secure. If a breach affects you, we will tell you as the law requires.

Age. FitnessFeed is for people 18 and older. When you create an account, we ask for your date of birth to check your age. The check happens on your phone and we don't keep your date of birth; we only record that you confirmed you are 18 or older. We don't knowingly collect information from anyone under 18, and if we learn we have, we will delete it.

Changes. If we make a significant change to this policy, we will tell you in the app before it takes effect. The date below shows when it was last updated.

Effective date: October 14, 2026