Privacy Policy
Last updated 21 October 2026
What's changed: if you tick an injury or limitation, Forge now uses it to swap or leave out exercises in your workouts that we've marked as ones that could make it worse (sections 2, 3, 4 and 6). Areas ticked before this version don't change your workouts unless you tick them again in Profile. What we collect, who we share it with and where it's stored haven't changed. The update of 5 October 2026 added sign-in codes for new browsers. The update of 28 September 2026 added card-expiry reminders, failed-payment notices and the beta gift. The first full version was published on 26 September 2026.
1. Who we are and how to contact us
Forge is run by Lyceum Digital Ltd, NZBN 9429053867315, 149 Nelson Street, Auckland City, Auckland 1010, New Zealand. We're responsible for your personal information under the Privacy Act 2020.
Privacy Officer: privacy.forge@lyceumdigital.com, 149 Nelson Street, Auckland City, Auckland 1010, New Zealand.
2. The short version
- We collect what you give us to run Forge: your account details, your training, your body measurements and wellbeing check-ins, and photos you choose to upload.
- Some of it is health-related (like injuries, heart-rate data and body photos). We treat it with extra care. We use it only to show you your own training and progress and, if you tick an injury or limitation, to swap or leave out exercises in your workouts.
- We don't sell your information, we don't use advertising trackers, and we don't share your data with advertisers.
- Your data is stored with our service providers in Australia and some overseas locations (details in section 7).
- You can download your data, correct it and delete your account at any time in Settings.
3. What we collect, and why
| What | Examples | Why we need it | Required? |
|---|---|---|---|
| Account details | Name, email address, password (stored only as a secure one-way hash), whether your email is verified, sign-up date | To create and secure your account and contact you about it | Email and password required (or Google sign-in). Name optional |
| Confirmations and consents | That you're 16+, the version of these policies you accepted and when, marketing email choice and when you changed it, purchase age confirmation | To show what you agreed to, and respect your choices | Required to create an account |
| Profile | Date of birth, sex (male / female / prefer not to say), height, units, lifting and running experience, goals, equipment, training days and session length, nickname | To set up programs and estimates (e.g. daily calorie estimate, training loads) and personalise Forge | Optional — Forge works without them, but estimates will be less accurate |
| Injuries and limitations | Areas you tick (e.g. knee, lower back) and any notes you write | So your workouts swap or leave out exercises we've marked as ones that could make those areas worse. Swap still lists them, after the others. Areas ticked before version 1.3 of this policy only do this once you tick them again in Profile. Your notes are kept in your profile; nothing in Forge reads them | Optional. Tick none and your workouts stay as written. You can change them in Profile. Please don't enter more medical detail than you want stored |
| Body measurements and check-ins | Weight, body-fat %, muscle mass, resting heart rate, heart-rate variability (HRV), weekly energy / sleep / recovery ratings, notes | To show your progress and trends | Optional |
| Training data | Sessions, sets, reps, weights, RPE, notes, personal records, goals, runs (distance, duration, pace, average heart rate), streaks and badges | To run the app: log, sync, analyse and show your progress | Needed for Forge to be useful |
| Location during runs | GPS position while you use the Run page | To measure distance and pace on your device. Your GPS route is not sent to or stored by us — only the totals (distance, time, pace) | Optional; you can enter runs manually |
| Photos | Profile photo; progress (body) photos (Pro) | To show them back to you. Stored privately; only you can view them, through short-lived secure links. We don't analyse photos (no face recognition) | Optional |
| Purchases and subscription | Plan (including any beta gift), subscription status, renewal/end date, programs unlocked, voucher codes used, Stripe customer ID | To give you what you paid for and manage renewals | Needed only if you buy something |
| Payment details | Card details and billing information | Collected and held by Stripe, not us. We receive only the payment result and customer ID | Needed only if you buy something |
| Sign-in sessions and security | When you signed in, your device/browser description (user agent) and IP address, secure session tokens | To keep your account secure, detect misuse and let you stay signed in | Required |
| Remembered browsers and sign-in codes | For each browser (or installed Forge app) confirmed as yours: a one-way hash of a random marker saved in that browser (a cookie — see section 6) and the date it was last confirmed. We don't record the browser's name, IP address or location with it. Sign-in codes we email you: stored only as one-way hashes, with the marker hash of the browser that asked, the number of tries, when the code was sent and when it runs out, and a count of the codes asked for on your account in the current hour | To ask for an emailed code when someone signs in with your password on a browser that hasn't been confirmed for your account in the last 30 days, so a stolen password isn't enough on its own — and to email you when your account is signed in with Google on a new browser | Required |
| Failed sign-in tries | For each email address someone tries to sign in with, whether or not it has a Forge account: a one-way hash of the address (not the address itself), the IP address the try came from (for an IPv6 address, only its network part), the number of tries in a row, the time of the last one and, if sign-in is locked, when the lock ends | To pause sign-in for that email from that IP address for 20 minutes after 3 wrong passwords in a row, which makes passwords harder to guess | Required |
| Notification settings | Which reminders you want and when | To send the reminders you asked for | Optional |
| Messages to us | Name, email and message from the website contact form, or emails you send us | To reply to you | Optional |
We don't collect: advertising IDs, contacts, analytics or tracking data, or biometric templates.
Information we get from others (indirect collection)
- Google — if you choose “Continue with Google”, Google tells us your email address, first and last name and that your email is verified. We use this only to create and sign in to your account.
- Stripe — tells us whether a payment or renewal succeeded, failed, was refunded or cancelled.
- Our hosting and security providers — record technical information such as IP addresses in server logs.
4. How we use your information
We use your information only to:
- provide Forge — your account, programs (including swapping or leaving out exercises for injuries or limitations you tick), logging, sync across your devices, analytics, badges and streaks;
- process purchases and manage subscriptions, receipts and refunds;
- send account emails (verification, sign-in codes, new sign-in alerts, password reset, receipts, renewal reminders, card-expiry reminders, failed-payment notices, important changes to Forge or these policies) — these aren't marketing and you can't opt out of them while you have an account;
- send reminders and notifications you've switched on in Settings;
- send marketing emails only if you've opted in — you can unsubscribe at any time from any marketing email or in Settings;
- keep Forge secure, fix problems and prevent misuse;
- reply to your questions and complaints;
- meet our legal obligations (for example tax records).
We don't use your health-related information for marketing, and we don't make automated decisions about you that have legal or similarly significant effects.
5. Who we share it with
We don't sell or rent your information. We share it only with:
- Service providers who store or process it for us to run Forge (listed in section 7). They act on our behalf and may use it only to provide their service to us.
- Stripe, to process payments (Stripe also has its own legal obligations, e.g. anti-fraud and financial record-keeping, under Stripe's privacy policy).
- Professional advisers (lawyers, accountants) where needed, under confidentiality.
- Authorities when the law requires it, or to prevent a serious threat to someone's life or health.
- A buyer of Forge, if the business is sold — they'd have to keep treating your information in line with this policy, and we'd tell you.
6. Cookies and storage on your device
- Cookies: we use only essential cookies — a secure sign-in cookie that keeps you logged in, a short-lived cookie that protects Google sign-in, and a security cookie that marks this browser so we can tell whether a sign-in needs an emailed code. The security cookie holds only a random marker. It lasts up to 30 days and is renewed each time the browser is confirmed for an account. It stays when you sign out, because it marks the browser, not an account. You can remove it by clearing your browser's cookies; you'll then be asked for a code the next time you sign in with your password. No advertising or analytics cookies.
- On your device: Forge stores some of your data in your browser/app storage so it works offline and loads quickly — for example your profile (including the injuries and limitations you ticked, and your notes on them), recent body measurements, your profile photo, workout history and changes waiting to sync. It's cleared when you delete your account and when a different person signs in on the same device. Signing out clears your sign-in details. If you share a device, sign out when you're done.
- Fonts: fonts are served from our own servers.
7. Where your information is stored (including overseas)
| Provider | What they do for Forge | What data | Location |
|---|---|---|---|
| Google Cloud (Cloud Run) | Runs the Forge server | All data passes through; server logs (incl. IP addresses) | Sydney, Australia |
| Neon | Database | All account, profile, training, body, purchase and consent data | Sydney, Australia |
| Cloudflare | Domain, security and traffic routing (DNS, proxy/Worker); R2 photo storage | Traffic metadata incl. IP addresses; your photos | Global network; R2 bucket location: Oceania |
| Stripe | Payments and subscriptions | Name/email, payment and billing details, purchase history | United States (and other Stripe locations) |
| Microsoft 365 | Sending and receiving our email | Your email address and email content (account emails, marketing emails if you've opted in, messages to us) | New Zealand |
| Sign-in with Google (if you use it) | Sign-in details | United States / global |
Australia and the United States don't have exactly the same privacy laws as New Zealand. We choose providers with strong security and contractual protections, and our main data stores are in Australia, which has comparable privacy law.
8. How we protect it
- Passwords are hashed; we can't see them.
- Data is encrypted in transit (HTTPS) and at rest by our providers.
- Photos are in a private store and shown only through links that expire within minutes.
- Our database provider keeps short-term backups for recovery (about 6 hours of point-in-time history).
No system is perfectly secure. If a privacy breach is likely to cause serious harm, we'll tell you and the Privacy Commissioner as soon as we practicably can.
9. How long we keep it
| Information | How long |
|---|---|
| Your account and everything in it | Until you delete your account. If you don't sign in for 24 months, we'll email you, then delete the account a month later if you don't respond. |
| Accounts that never verify their email | Deleted after 7 days |
| Sign-in session records (incl. IP address, device) | Until 7 days after the session expires (sessions last up to 30 days) |
| Password reset / email verification links | Deleted 7 days after they expire |
| Remembered browsers (a hash and a date) | A browser stays confirmed for 30 days. Its record is deleted by our daily clean-up 400 days after it was last confirmed, or when you delete your account |
| Sign-in codes | A code works for 10 minutes and is deleted when you use it. Unused codes, and the count of codes asked for, are deleted 1 to 2 days later — or straight away when you reset or change your password |
| Failed sign-in tries (email hash, IP address, count) | Deleted 1 to 2 days after the last try — or straight away when the right password is entered from the same IP address, or the password is reset or changed |
| Payment records held by Stripe | As Stripe and tax law require (we must keep tax records for 7 years) |
| Messages you send us | Up to 2 years after we've resolved your query |
| Backups | Roll off automatically within about 6 hours |
| Server logs | Deleted automatically after 30 days |
When you delete your account we permanently delete your profile, training, body data, check-ins, photos, purchases and consents from our database and photo store, and ask Stripe to delete your customer record (which also cancels any subscription). Stripe may keep payment records it's legally required to keep.
10. Your rights and choices
You have the right to ask for the personal information we hold about you and to ask us to correct it (Privacy Act principles 6 and 7).
- Download your data: Settings → Export my data (a copy of all the data Forge holds about you).
- Correct it: edit your profile, body data and logs in the app, or email us.
- Delete it: Settings → Delete account.
- Marketing: turn it off in Settings or use the unsubscribe link in any marketing email.
- Reminders: Settings → Notifications.
- Ask us anything: email our Privacy Officer at privacy.forge@lyceumdigital.com. We'll respond within 20 working days (the Privacy Act limit), and usually much sooner.
If you're not happy with how we've handled your information, please tell us first. You can also complain to the Office of the Privacy Commissioner — privacy.org.nz, 0800 803 909.
11. Age
Forge is for people aged 16 and over. We don't knowingly collect information from anyone younger. If you think someone under 16 has an account, contact us and we'll delete it.
12. Changes to this policy
We'll update this policy when Forge or the law changes. If a change affects how we use information you've already given us, we'll tell you in the app or by email before it applies and, where needed, ask for your agreement. Each version shows its date and a summary of changes.