Privacy policy

When you register with email, FitCrew uses your email address, password, display name, handle, and time zone to create and manage your account. The backend stores a password hash, not your password in plain text. Profile information can also include a profile photo, distance-unit preference, and visibility settings.

A profile photo is optional. The app uses your camera or photo picker only when you tap to take or choose one. It shrinks the photo and re-encodes it before uploading, and the backend removes embedded metadata, such as where the photo was taken, before storing it with your account. Removing your photo or deleting your account deletes it from FitCrew’s servers.

If you choose Sign in with Apple, or Google sign-in where available, FitCrew verifies the identity token and stores the provider’s account identifier and email address when supplied. Apple may provide a private relay email address. For Sign in with Apple, FitCrew also stores an encrypted token from Apple, used only to revoke FitCrew’s access to your Apple ID when you delete your account. Sign-in options depend on the platform and release configuration.

FitCrew also stores the challenges you create or join, invitations, Crew relationships, the members you block, reactions, pokes, challenge progress, achievements, the names you give your workouts, the people in your Crew whose workout alerts you turned on, the people you take off your suggestions, and notification preferences. If you email support, your email address and the information you choose to send are part of that conversation.

FitCrew emails members “What’s new in FitCrew” updates from updates@fitcrew.org. It records which updates it sent you and whether each was sent, and when you unsubscribed. Every update email has an unsubscribe link; unsubscribing doesn’t stop account emails such as password resets. Replies to updates@fitcrew.org reach FitCrew’s team.

When you use a challenge’s chat, FitCrew stores your messages, the people you mention, and your reactions for 7 days, and remembers how far you’ve read it.

When you send someone a Fitz emote on a challenge’s leaderboard, FitCrew stores who sent it, who it’s for, which emote, and when they saw it, for 7 days.

If you report a member, a challenge, or a chat message, FitCrew stores the report, with the reason you chose, and emails it with your name and username, and a reported message’s words, to FitCrew’s support address for review. FitCrew doesn’t tell anyone who reported them.

FitCrew is for people 18 and older.

When you create an account, FitCrew records that you confirmed you’re 18 or older and agreed to the Terms of use and this policy: their versions, the time, how you signed up, and which app you used. It doesn’t record your IP address or browser for this. The record is kept after you delete your account, with only the internal account identifier, as proof of what was agreed.

Connecting health data is optional. When Apple Health or Health Connect asks for access, you can decline it or allow only some categories. Without access, FitCrew cannot read new health activity from your device; previously uploaded activity may still appear in your account.

The installed iOS app uses Apple Health through HealthKit. The Android app uses Health Connect. FitCrew requests read access to workouts, distance, steps, activity minutes, and active calories, and you choose which of these to allow. For sleep goals, FitCrew can also read your sleep (sleep analysis in Apple Health, sleep sessions in Health Connect): it uploads only your minutes asleep each night and, for sleep goals that count consistency, a score from 0 to 100 your phone works out for how close that night’s bedtime was to your usual one, never bed or wake times or sleep stages. On Android, FitCrew also reads total calories burned and basal metabolic rate (resting energy) from Health Connect, because many devices record only total calories: your phone subtracts resting energy from total calories to work out your active calories. FitCrew uploads only the resulting active calories, never your total calories burned or basal metabolic rate. Activity minutes means recorded workout duration; Exercise ring minutes outside recorded workouts are not included. Availability depends on your device, health provider, and permissions. The current integrations do not request heart-rate measurements or GPS routes, and do not write records to your health store.

Imported data can include activity type, including what your health app recorded a workout as, such as Badminton, but never a workout’s own title or notes, start and end times, duration, selected metrics, a workout’s laps (when each started and ended and how far it went) when your health app split it into them and you allow distance, time zone, provider, and source activity or device identifiers. Sync checkpoints and record revisions help process updates and avoid counting the same activity twice. Initial sync can include recent historical activity allowed by the provider.

So that activity counts from one phone at a time, each sync includes a random identifier the app creates for that installation and the phone’s model or device name. FitCrew stores them for the phone your activity counts from, and shows that name on your other phones.

This information is not kept only on your phone. Selected activity is normalized and uploaded to the FitCrew backend, linked to your account, and used for your activity summaries, challenge scoring, and leaderboards. Health access supports these fitness features, not advertising.

A browser cannot read Apple Health or Health Connect directly. It can show activity already uploaded by the installed iOS app using Apple Health or the Android app using Health Connect. Demo mode uses synthetic activity instead of reading your real health data.

Your profile is visible to other signed-in FitCrew members: your display name, handle, profile photo if you added one, the number of people in your Crew, and your challenge wins. Anyone who can see your name in FitCrew, including in searches, Crew lists, and leaderboards, can see your photo. Your profile can appear in member searches by display name or handle. Your Crew is the people who accepted a Crew request from you or whose request you accepted. People in your Crew can see everyone in it, and so can every member if you share your activity with Everyone; other members see only how many people are in it and anyone who is also in their own Crew.

Profile → Settings → Privacy → Activity visibility controls who can see your daily activity summaries and your workouts from the last seven days: your Crew, challenge participants (people who share an invite-only challenge you have joined; public challenges are open to anyone, so they don't count), both, or neither. Each workout shows only its kind or what your health app recorded it as, such as Badminton, or the name you gave it, how long it lasted, how far it went and the calories it burned when those were recorded, its splits (how far each lap went and how long it took, never when) when your health app split it into laps, and what recorded it, such as Apple Watch, iPhone, or the app that saved it, like Samsung Health or Strava, never your device’s own name or identifier. Everyone, which is off unless you turn it on, lets any signed-in FitCrew member see them, including people who find you in a search. New accounts share activity with their Crew. Turning all of these off keeps your activity to yourself.

Someone in your Crew who may see your activity can turn on workout alerts for you. Each time a workout of yours finishes, from when they turned it on, they get a notification with your name, its kind or what it was recorded as, or the name you gave it, how long it lasted, and how far it went and the calories it burned when those were recorded. The alerts stop once they can no longer see your activity, or either of you leaves the other’s Crew or blocks the other. When someone in your Crew pokes you, you get a notification with their name and the emote they sent.

Activity visibility does not control health uploads. Your own daily activity screen shows summaries of your uploaded activity and your workouts. Changing visibility does not delete that activity.

Challenge access is separate from activity visibility. People who can access a challenge can see its leaderboard names, progress, ranks, and completion information: its participants and the people invited to it, or any signed-in member for a public challenge, which anyone can find by name and join. Turning off activity visibility does not hide your challenge scores.

Your profile lists the challenges you're in. Public challenges, and the ones you share with the person looking, show there with your place and score. Your other invite-only challenges don't show there, even to your Crew.

A challenge’s chat shows your messages and reactions, with your name and photo, to everyone still in that challenge, including people who join while your messages are there. The chat also tells them when you join, leave, or take the lead. Once you leave the challenge you can no longer read its chat, and someone you’ve blocked, or who blocked you, doesn’t see your messages.

A Fitz emote you send on a challenge’s leaderboard pops over that member’s row, with your photo, for everyone watching the board, and the member it’s for gets a notification saying it’s from you.

You can share an image of a challenge while it runs or once it has finished, of your week or month from Insights, of one workout, or of a day’s workouts. A challenge image comes as Board, Stats, or Photo and shows your name, your place, the challenge, and, depending on the template, your own totals and the challenge’s goal; it shows only how many people take part, never who they are. A workout or day image shows its own figures, such as duration, distance, pace or speed, and activity calories, over Fitz or a photo you choose.

The app draws every share image on your device and passes it to the app you choose or your browser’s download. FitCrew does not upload the image, and a photo you choose stays on your device. The text sent with it can include a link to the challenge’s page or to FitCrew’s homepage.

FitCrew stores preferences, cached account and challenge information, synchronized activity, sync checkpoints, and queued changes on your device so the app can preserve state and retry changes after connectivity returns. Native sign-in sessions use secure device storage; the website stores its session in browser local storage.

Signing out, or a session that has ended, removes the session and the account information saved on that device. Your personal goals stay on the device for when you sign in again, and are deleted from it with your account.

The website and API receive technical request information, such as IP addresses and browser or device information. Authentication records include session identifiers, token hashes, timestamps, and security-related metadata. Server request and error logs help operate and troubleshoot the service. For each email FitCrew sends, Azure Communication Services records the address it went to and whether it was delivered, so FitCrew can find addresses that bounce.

FitCrew records when you last opened the iOS app, the Android app, or the website, so it can count how many people use FitCrew apart from apps that only sync in the background. Only those totals are reported, never who opened it.

If you enable device notifications, FitCrew registers an Expo push token with your account and stores the device platform and your notification preferences. Device push requires a supported native app and permission; notification availability depends on the release configuration.

FitCrew runs on Microsoft Azure in India. The API runs in Azure’s South India region. The database, which holds your account, profile photo, activity, challenges, and chat messages, is in Central India. The website is served by Azure Static Web Apps.

Azure Communication Services, which sends FitCrew’s emails, keeps its data in India. Other companies receive some information to run FitCrew, as the next section explains.

Avoid sending passwords, sign-in or reset links, or full health records in an email.

Change health permissions in Apple Health or your device’s Health Connect settings. Revoking access stops future reads of those categories; it does not delete information already uploaded to FitCrew or necessarily cancel activity uploads already queued on a device.

Use Profile → Settings → Privacy to change visibility. Use Profile → Settings → Notifications to change notification preferences or Disable on this device where available. Device settings also control notification permission. To stop update emails, use the unsubscribe link in any of them.

To get a copy of your information, use Profile → Settings → Privacy → Download your data. You can also email the address below to ask for a copy of your information, or to have it corrected or deleted.

Signing out or uninstalling the app does not delete your backend account or activity. To delete your FitCrew account, use Profile → Settings → Delete account in the signed-in app or website, and confirm. If you cannot access your account, contact the address below for help with your request.

Account deletion removes uploaded activities, health connections and the phone your activity counts from, challenge participation and progress, Crew relationships, blocks, reports you sent or that were made about you, reactions, leaderboard reactions you sent or got, chat messages, the record of update emails sent to you, notifications, achievements, workout names, workout alerts you turned on or that others turned on for you, the people you took off your suggestions or who took you off theirs, when you last opened the app or website, and device push tokens from the application database. Challenges you created are also deleted, which affects the other participants in those challenges. If you signed in with Apple, FitCrew also asks Apple to revoke its access to your Apple ID.

Deletion replaces your profile’s identifying fields and disables your sessions rather than erasing every database record. The service keeps an internal account identifier, when the account was deleted, and the record of what you agreed to when you created the account. Revoked session records and associated security metadata are deleted within 90 days of the deletion. Server logs, support emails, and emailed reports are deleted on the schedule above. Signing in again later with the same Apple or Google account starts a new, empty FitCrew account.

The device you delete your account on also forgets your session, saved account information, and personal goals. Deleted information stays in database backups for up to 7 days.

Deleting your FitCrew account does not delete the original records in Apple Health, Health Connect, or another source app. Those records remain under that provider’s controls.

Contact FitCrew for privacy questions or requests about access, correction, or deletion of your information. Include your account email and a brief description of what you need, but do not send your password or health records.

The date at the top identifies this version of the policy. FitCrew emails members at least 7 days before a material change to this policy takes effect. You can return to this page from account setup or Privacy settings.