Privacy
Updated November 7, 2026
track2.fit is a workout tracker operated by Angelo Ocana Martins. This page describes the information used to save your workouts, sign you in, sync your devices, and provide optional public workout sharing.
Information you provide
Your workout history, exercises, routines, sets, notes, preferences, and device names are saved on each device you use. After sign-in, the app uploads this information as a log of changes so your other signed-in devices can recover and sync it. The log includes randomly generated account, event, and device identifiers and timestamps.
Optional public profiles and workout sharing
Your training stays private until you share a workout or enable automatic sharing. Creating a profile asks you to choose a Public or Private account. Once approved, your handle, display name, bio, selected profile photo and follow counts are public in either case. Public accounts accept follows immediately; private accounts approve requests. Pending requests do not grant access. Shared workout snapshots, captions, selected photos or videos, likes and comments inherit the account’s current visibility: everyone for public accounts, approved followers for private accounts. Removing a follower revokes subsequent private-workout and media requests. Making an account public asks for confirmation because previously shared workouts become public; unshared workouts stay private. Making it private preserves existing followers and protects hosted workout media. We show a pending state until older media URLs have been replaced. Previously downloaded public copies cannot be recalled.
Automatic sharing asks whether to include past workouts. It shares completed summaries using account visibility, without photos, videos, private notes or heart-rate data. Turning it off keeps existing shares. Choosing Only me for a workout excludes it from automatic sharing until you deliberately share it again. Exporting images or video to another app does not publish to the community. Older friends/group shares retain their original restrictions and do not silently become visible to followers. Old automatic policies for these audiences are paused until reviewed. Removing a friend or leaving a group still revokes that legacy access. Sign-in emails, private notes and heart-rate data are not in workout snapshots. Editing or deleting a private workout does not change its existing shared post; use Remove shared workout to withdraw it.
Social drafts and selected files are saved on your device. Publishing and social interactions require a connection. Uploaded files are stored by Convex; unused uploads are removed after 24 hours. Original photos and videos may include location or other embedded metadata. Removing a shared workout hides the post and deletes its hosted media. Other people may have downloaded or cached public content, and those copies cannot be recalled. Blocking hides content and denies interactions between signed-in users; it does not make public posts private. Reports are stored for operator review.
Watch heart rate and motion
With your permission, the Apple Watch app reads heart-rate samples from HealthKit during an active workout; Wear OS uses its native health service. Heart-rate readings and measurement timestamps are saved with your workout, linked to your account, and synced to your signed-in devices and our hosted service so you can see exercise and workout summaries. Heart-rate access is optional and you can continue logging without it. We use health and fitness information only to provide workout tracking and sync, never for advertising, data brokerage, or model training. The Apple Watch app does not save workouts to Apple Health.
Optional rep suggestions use wrist motion on the watch. Raw motion stays on that watch and is discarded. If you accept a suggestion, the saved rep count becomes part of your normal workout log. You can turn rep suggestions off in Settings and manage heart-rate permissions in your device's system settings.
Body measurements
If you record body measurements (weight, body fat, height, tape measurements such as waist or arms, and skinfold caliper readings), they are saved on your devices like your workouts and, after sign-in, synced to your signed-in devices and our hosted service so your devices show the same history. They are linked to your account, included in Export data and deleted with your account. Body measurements are never included in shared workouts, posts, public profiles or feeds. We use them only to show your measurements and charts, never for advertising, data brokerage, or model training.
To calculate body fat from skinfolds or tape measurements, the app can ask for your sex and birth date. They are optional, stored and synced like your other settings, used only by these calculations, never shown on shared or public pages, and you can change or remove them in Settings at any time.
Google and Apple sign-in
When you use Google sign-in, Google provides a verified account identifier, email address and, when available, a profile photo URL. Apple provides an account identifier and, when available, a verified email address, which may be a private relay address. We use these to authenticate you, show your connected sign-in methods, and associate your devices with your workout history. The app does not receive your Google or Apple password.
Google sign-in requests only the openid, profile and email permissions. It does not request access to Gmail, Drive, Calendar, contacts, or other Google services. Google account information is used for sign-in and account management. Your Google photo stays private unless you select it for your public profile. You can upload a custom public profile photo or remove it. Apple sign-in does not supply a photo. Custom profile photos are resized and re-encoded without embedded metadata. Replacing or removing a custom photo deletes its hosted file. Account information is not sold or used for advertising.
For Apple sign-in, the server keeps an encrypted refresh token so it can revoke Apple's authorization when you disconnect Apple or delete your account. This token is never sent to your devices or included in workout exports. If Apple is temporarily unavailable, an encrypted revocation request is retained separately and retried until Apple acknowledges it, then erased. Ordinary sign-out does not disconnect your Apple authorization.
Community review
The operator can inspect submitted profiles and photos, shared workout snapshots, captions, attachments, comments and group names to enforce community standards before publication. Unreviewed and rejected submissions are visible only to their authors and the operator. Editing a profile temporarily hides its community content until approved again. Approval does not change your chosen audience or account privacy. The operator uses locally running AI models to screen submitted community content. Clear text may be approved automatically. Attached photos are also checked by two local image models. When the operator switches on automatic photo approval, photos both models consider clearly safe may be published without human review; the operator spot-checks them and can remove them. Videos, photos from sign-in providers and uncertain or flagged content always require human review. Models can make mistakes. Community content is processed on the operator’s computer, not sent to an external AI inference service or used to train these models. Private workout logs are not sent to the moderation worker. Temporary review content is held in memory; a short-lived local cache retains input hashes without account identifiers and classification results. To evaluate the photo checks, a local log keeps for up to 12 months a hashed submission reference, the photo check scores and the operator’s decision, without account identifiers, text or images. Decision records contain the submission identifier, revision, decision, reason, time and, for automatic approvals, model and policy identifiers and an input hash, plus file hashes for photos. Account deletion erases its server decision records.
Storage and service providers
The web app stores its local copy in your browser's IndexedDB. Phone and watch apps use local SQLite databases. Convex stores the hosted account information and event log; Cloudflare hosts the website and routes API traffic. These providers process information to run the service, and their infrastructure may process it outside your country. The current production Convex deployment is in the United States.
Requests use HTTPS. Browser sign-in uses a secure, HttpOnly session cookie. Native sessions and watch sync credentials use the platform's secure credential storage. The backend stores hashes of session credentials. The service uses access controls; workout data is not end-to-end encrypted.
Cookies and operational information
The app uses its session cookie and local storage for sign-in, offline use, and syncing. It does not include advertising trackers or an analytics SDK. Hosting providers process network information such as IP addresses and request metadata to operate and protect the service. The backend uses a hashed visitor identifier for short-lived rate limits.
Each app keeps a short log of problems on your device, such as a failed save or sync, without workout contents. Requests include the app version. With each sync, an app sends how many problems it had in each category (for example cloud sync, or the app closing unexpectedly), without messages or workout data. The version, the time the device last synced and seven days of these counts are stored with that device's record in your account and shown to the operator only as totals. Share diagnostics in Settings creates a file with the app version, sync status and recent problems; it leaves your device only if you choose to send it.
Bug reports and ideas
When you send a bug report or an idea from Settings → Help, we store what you wrote, the app version, platform and language, and, if you leave Include diagnostics on, the same diagnostics as Share diagnostics (no workout contents). If you leave Email me about this on, we store your account's sign-in email so we can reply. Reports are read only by the operator to fix problems and improve the app, and are deleted with your account.
Retention and deletion
Signing out preserves your local and hosted workout history. Deleting a workout, routine, exercise, or set hides it from your history, while the change log retains the earlier data and deletion event so offline devices can converge. Hosted account and workout data remain until account deletion is requested.
You can permanently delete your cloud account, linked sign-ins synced workouts, profile, follows and pending follow requests, legacy friendships and friend requests, per-workout privacy choices, groups you own, group memberships, sharing settings, shared posts, media and social interactions, bug reports, ideas and exercise-data reports in Settings → Account → Delete account. Access is revoked immediately and the live cloud database is erased in bounded background batches. Sign out everywhere revokes sessions without deleting cloud workouts. Local copies, including unsynced sets, remain stored and locked on your devices; remove the installation or clear site/app storage to erase them. Offline devices lock when they next sync or receive the phone's sign-out. Non-identifying credential hashes remain until their original expiry (at most 30 days) to communicate revocation; pending sign-in proofs expire within ten minutes. Hosting-provider backups follow the providers' retention policies. Export from Settings before deleting. For data access or help, contact angeloocana@gmail.com from your connected sign-in address.
Changes and contact
This page will be updated when the service's data practices change. Questions can be sent to angeloocana@gmail.com.