Last updated: 20 July 2026
Kit is a workout tracking app made by Joint Effort Software. This policy describes what data the app handles and where it goes. The short version: your training data lives on your device; everything else is optional and under your control.
Your workouts, exercises, sets, personal records, strength goals, manually entered body measurements, program customisations, and feedback are stored in a local database on your device. This data never leaves your device unless you enable one of the optional features below. Deleting the app deletes this data.
You may create an account (email/password, or Google sign-in) to enable cloud backup. If you do:
Account deletion is available in the app (Account screen → Delete account). It permanently removes your account and cloud backup. Data on your device is kept.
When you generate a workout while online, the app sends training context — recent exercises, muscle-group recovery status, optional derived recovery/availability instructions, difficulty feedback, and any rejection notes you typed — to Anthropic's Claude model through our server, which holds the API credentials. No name, email, or account identifier is included. To diagnose generation problems, our server keeps short-lived operational logs of these requests (truncated request/response excerpts, model name, token counts); they contain the same training context described above and nothing more. Anthropic processes this data per their commercial terms. If you are offline, workout generation runs entirely on-device.
Kit maintains a shared, growing exercise catalog so every user benefits when someone discovers a new exercise:
Exercise names are visible to other users as catalog entries, so don't put personal information in an exercise name.
The app sends crash reports to Sentry (stack traces, device model, OS version, app version) so we can fix bugs. To make crashes reproducible, reports include a short trail of recent in-app actions (e.g. "saved workout", "opened exercise info" with the exercise name). This trail leaves your device only when an error occurs, attached to that report. Crash reports never include your logged weights, reps, or workout history.
If you use Settings → Send feedback, the message you write — and your email address, if you choose to provide one for follow-up — is stored in Kit's support database after the app receives a successful server acknowledgement. A secondary copy may also be sent through the crash-reporting service (Sentry) for diagnostics. Both fields are entirely under your control: send nothing, or send it without an email, and it still reaches us.
If you configure a webhook URL in Settings, the app sends your workout summaries to that URL after each save. This is entirely user-configured — you choose the recipient, and it is off by default.
If you enable Health workout sync in Settings, Kit asks for permission to write each newly completed workout to Health Connect on Android or Apple Health on iOS. The entry contains the workout start and end time, exercise names, and completed-set count.
Separately, if you enable Health insights, Kit reads last-night sleep and exercise sessions from the previous 36 hours. These can make a generated workout lighter, shorter, or avoid recently loaded muscles. Raw health records are processed on-device and are not saved to Kit's database, cloud backup, logs, or analytics. AI generation may receive only a derived recovery or muscle-load instruction, never the raw records.
Both options are off by default and can be controlled independently. Turning workout sync off does not remove entries already written to your device's health store.
If you enable Calendar availability in Settings, Kit reads event start/end times for the current day to find the longest free gap and size a workout around it. It ignores event titles, notes, locations, attendees, all-day events, cancelled events, and events marked free. Raw events and times are not saved to Kit's database, cloud backup, logs, or analytics. When AI workout generation is available, Kit may send only the derived instruction that about a certain number of minutes are available; it does not send the underlying events. This option is off by default and can be turned off at any time.
Beta builds are distributed through Firebase App Distribution, which processes tester email addresses for the purpose of delivering builds.
Questions or data requests: use Send feedback in the app (You tab → Send feedback), or email contact@jointeffort.software.
We will update this page when data practices change, and note material changes in the app's release notes.