Privacy Policy.

FORGE is run by an independent developer (“FORGE”, “we”, “us”). This policy explains what FORGE keeps, where, and who can see it. It goes with our Terms of Use. Questions: support@forgeendure.com.

FORGE keeps your training in the browser on your device. Without an account, none of this is uploaded to FORGE:

• your goal, profile, body weight and thresholds;
• your training plan and plan history;
• workouts and lift sessions, and anything you import from Garmin or your watch;
• recordings made with your phone, with their GPS routes and per-second data (pace, heart rate, power, elevation);
• watch files you import (.FIT, .GPX, .TCX), kept in full, original file included;
• health data: your morning check-ins, and the resting heart rate, HRV, sleep, weight and steps synced from your watch;
• your intervals.icu access (a sign-in token or the key you pasted), if you connect your watch (see Your watch);
• your meal log, fuel targets and meal photos.

With an account, some of it goes to our servers: a summary of each workout you share, and your goal's name and progress (see the next two sections). Your plan, thresholds, workouts you don't share, GPS routes, per-second data, original watch files, health data, meal log, saved meals, fuel targets and meal photos stay on your device either way.

Because it lives in your browser, clearing this site's data deletes it, and a new phone starts empty. Export a backup from More → Export everything now and then. The backup includes your recordings and health data; original watch files stay with your watch's app, and your intervals.icu access is left out.

You can use FORGE without an account. If you create one, we store:

• Account: your email (to sign you in and reset your password, and shared with Stripe when you pay or set up coach payouts — never shown to other people), your password as a one-way scrambled hash we can't read, and when you agreed to our terms. If someone proves with Google that they own the email on an account and says the account isn't theirs, the email is removed from that account and we keep a record of the change, so we can help if it was a mistake.
• Sign in with Google, if you use it: the name, email and Google account id Google sends us, used to sign you in and set up your profile. Never your Google password, contacts or anything else in your Google account.
• Face ID and passkeys, if you add one: only its public key (never the private key or anything about your face), with its id, the name you give it, which FORGE address it's for, and when it was added and last used. Your face or fingerprint is checked by your phone and never leaves it.
• 2-step sign-in, if you turn it on: whether it's on, and your recovery codes, stored only as one-way hashes.
• Profile: your name, handle and avatar color, plus a bio, location, sports, gender and body weight if you add them. Gender only places you on the women's or men's crown boards; body weight is never shown to anyone else.
• Community: your workout posts (sport, title, date, time, distance, elevation gain, heart rate and its graph, time in each heart rate zone, power, training load, effort, lifts and how it felt), plus kudos, comments, follows and reports.
• Training summary: level, XP, streak, badges, your goal's name and progress, and weekly XP for the league. These update automatically while you're signed in.
• Coaching: coaching requests and status, workouts your coach writes and how you did them, and messages between you and your coach.
• Fuel+: your subscription status and renewal date, how many photos and descriptions you used each day, and a basic record of each estimate (when, which provider, photo or description, whether it worked, its cost) — never the photo or what you typed.
• Notifications, sign-in sessions (a scrambled token and your browser's name), and short-lived security records that stop password guessing, kept as hashes. While a Google or Face ID sign-in is finishing, the server keeps a short record of it for at most 10 minutes, with a scrambled (hashed) form of the network it started from, so a sign-in that finishes somewhere else has to be confirmed with a code from your phone.

Workouts are shared automatically. While you're signed in, each workout you finish or log is posted to the community, unless you untick Share to community on it. To stop this for every workout, turn off More → Auto-share completed workouts. A workout synced from your watch through intervals.icu ticks off the plan session it was by itself, and that session is then shared the same way, if it's from today or yesterday and auto-share is on. Any other synced activity is only shared when you share it.

A post never includes a GPS route or map, per-second data, an original watch file, or your check-ins, resting heart rate, HRV, sleep or weight.

Your audience setting in Account → Privacy decides who sees your posts and stats (level, XP, streak, badges and goal). New accounts start out Public. Change it anytime; posts you already shared keep their audience. You can also pick the audience on a post when you write one yourself.

• Public: anyone, even without an account. Public posts count toward the weekly crowns, and your weekly XP shows in the league.
• Followers: people who follow you (no approval needed), plus your coach.
• Only me: just you.

Heart rate is health information. It's only shown in your workout posts, to your audience. To keep it to yourself, set your audience to Only me or turn sharing off.

Your resting heart rate, HRV, sleep, steps, morning check-ins and the weight you log with them (or sync from your watch) are health information too. They stay on your device: they aren't sent to FORGE's servers and never appear in posts.

Your name, handle, avatar, bio, location and sports show on your profile so people can find you. A coach you work with also sees the coaching workouts and messages you share with them. If someone reports a post, we can see it to review the report. Your email and body weight are never shown to anyone.

When you snap your food with Fuel+, or describe a meal in words instead (say, a burrito from a restaurant you name), the photo or what you typed is sent from our servers to the same third-party processing providers, which estimate what you ate and its calories and macros. Some of these providers are located outside your country, including in China, and handle the photo or description under their own terms, which may let them keep it for a limited time.

FORGE doesn't store your food photos or descriptions on its servers — the estimate comes back to you, and the meal stays in your meal log on your device. Keep faces, documents and anything private out of the shot, and out of what you type.

Meals you save to reuse stay on your device, and logging one sends nothing anywhere.

Routes are drawn on your device. An activity shows its route as a plain outline until you tap Show map; then the map tiles load from OpenFreeMap (built from OpenStreetMap data). Like any website, OpenFreeMap sees your IP address and which part of the map is shown, but not the route itself. The map's code comes from FORGE, or from the jsDelivr network if FORGE's copy isn't available. Your choice is remembered on this device; turn the map off again from any activity.

When you finish a GPS recording on your phone, FORGE downloads elevation tiles for that area from the free Terrain Tiles dataset hosted by Amazon Web Services, to work out the climb more accurately. Amazon sees your IP address and which tiles were fetched (roughly where you were), not the route itself.

Connecting a watch is optional. FORGE does it through intervals.icu, a separate free service you sign up for yourself, which links to Garmin, COROS, Polar, Suunto, Wahoo and others (and to Apple Watch through an iPhone app). You connect it one of two ways:

• Connect with intervals.icu: you sign in to intervals.icu and allow FORGE. intervals.icu gives FORGE a one-time sign-in code, and FORGE's server swaps it for an access token and hands that to your phone. While it waits for your phone to pick it up, the server holds the token encrypted, with your intervals.icu name and athlete number and the permissions you allowed, for at most 10 minutes. It's deleted as soon as your phone picks it up; one that isn't picked up in time can't be used any more and is cleared out shortly after. To stop abuse, the server counts these requests by a scrambled (hashed) form of your IP address, kept for about a day. It also keeps a scrambled form of the network you started from for up to 15 minutes, so a sign-in that comes back from another network needs the code FORGE shows you.
• An API key: you paste your own intervals.icu key into FORGE. Nothing passes through FORGE's servers.

Either way, the token or key is stored only on your device. It doesn't stay on FORGE's servers and isn't included in backups.

After that, FORGE talks to intervals.icu directly from your device. Requests go straight from your phone to intervals.icu, not through FORGE's servers, so your activities and health data never pass through or stay on them. FORGE downloads your activity files and daily health data (resting heart rate, HRV, sleep, weight, steps and similar) and keeps them on your device. If you turn on Send my plan to my watch, FORGE puts your next two weeks of planned sessions on your intervals.icu calendar, and intervals.icu sends them on to your watch if you've allowed that there.

intervals.icu handles your data under its own privacy policy, and any app you use to link your watch to it (such as one for Apple Watch) under its own. Disconnect anytime in More → Devices & connections: the token or key is removed from this device, FORGE asks intervals.icu to remove its access (if you used the Connect button), and FORGE takes its upcoming sessions off your intervals.icu calendar when it can reach it. Activities already brought in stay in your log until you delete them.

Stripe processes payments for Fuel+ and for coaching. We never see or store your card number. When you pay, or set up payouts as a coach, we give Stripe your email for receipts and billing. We keep the Stripe customer and subscription references and their status, so we know what you've paid for. Coaches who get paid set up their payouts with Stripe directly. Stripe handles payment details under its own privacy policy.

We use a few service providers, only to run FORGE:

• Vercel — hosts the app and its servers.
• Neon — our database.
• Stripe — payments.
• Resend — sends password-reset emails.
• Google — Sign in with Google, only if you choose it. Google handles that sign-in under its own privacy policy.
• Sentry (Functional Software, Inc., USA) — error reports, to find and fix crashes (see Error reports).
• GitHub — keeps the encrypted nightly backups of our database (see Keeping and deleting your data).
• Food processing providers — estimate nutrition from Fuel+ photos and descriptions (see Food photos and descriptions).
• OpenFreeMap — map tiles, only once you tap Show map on an activity (see Maps and elevation).
• Amazon Web Services — the open Terrain Tiles elevation data for GPS recordings (see Maps and elevation).
• jsDelivr — the map's code, only if FORGE's own copy isn't available.

intervals.icu isn't one of our providers: it's a service you connect yourself, and your device talks to it directly, apart from the one-time sign-in swap (see Your watch).

These providers may process data in the United States and other countries. We don't sell your personal information, and we don't share it for advertising. We'll disclose information if the law requires it, or to protect someone's safety.

When something in FORGE breaks, a report goes to Sentry, which we use to find and fix crashes. It holds the error, the page it happened on (without anything after a ? in the address), the app version, your device's operating system and browser (main version only), whether FORGE was opened from your Home Screen, and a short list of the screens, buttons and app messages just before it (button labels and emails taken out).

It never includes cookies, your email, your IP address, what you typed or sent (request contents), or your training data. Reports are kept for up to 30 days.

FORGE uses one cookie: a sign-in cookie that keeps you signed in (for up to 60 days, renewed while you use the app). Inside the app there are no ad cookies, no analytics and no third-party trackers. The app also keeps your training in your browser's storage, as described above — that's how it works offline, not tracking.

The public website pages are different. Our marketing pages — the welcome page at /welcome and the free calculators under /tools — use Google Analytics 4 to count visits and see which pages people read. It records the page you viewed, when, roughly where from (country and region; IP addresses are truncated and not stored), your browser and device type, and how you arrived. It sets a first-party cookie (_ga) to tell repeat visits apart. We have turned off Google Signals and ad personalisation, so nothing is used for advertising, and none of it is linked to a FORGE account. Google's own policy describes how it handles that data: policies.google.com/technologies/partner-sites. These pages are the only place analytics run; opening the app, signed in or not, sends nothing to Google.

We keep your account data while you have an account. Delete it anytime from Account → Delete account: your profile, posts, kudos, comments, follows, crowns, coaching history and messages come off our servers, and any subscription is cancelled. A few things can remain: copies in backups for a short time, payment records Stripe must keep by law, and usage counts that are no longer linked to you.

Backups: every night an encrypted copy of FORGE's database (accounts, posts, coaching and the rest of what's listed under What goes to our servers, not the training on your device) is made and kept for 30 days. When you delete your account it comes off the database right away; the copies in those backups expire within 30 days.

To delete what's on your device, use More → Erase all data, or clear this site's data in your browser. Deleting an activity also deletes its route, per-second data and original file.

You can see and edit your profile and audience in Account, turn auto-share off and export your training in More, and delete your account anytime. Depending on where you live, you may have more rights — to get a copy of your data, to correct it, to object to how it's used, or to complain to a data protection authority. Email support@forgeendure.com and we'll help.

Connections are encrypted, passwords, sign-in tokens and recovery codes are stored only as hashes, passkeys only as public keys, and most of your training never leaves your device. You can add Face ID and turn on 2-step sign-in in Account → Security. No system is perfectly secure, so use a password you don't use anywhere else.

FORGE isn't for anyone under 16. If you believe someone under 16 has an account, email support@forgeendure.com and we'll delete it.

We'll update the date at the top when this policy changes, and tell you in the app before a meaningful change takes effect.

FORGE is run by an independent developer. Privacy questions or requests: support@forgeendure.com.