Privacy Policy

Effective 2026-11-03 · Applies to the Forge mobile app and forging.day · Last revised: 2026-11-05

Forge is a training app. To coach you, it has to know things about your body and your training. This page says exactly what it collects, who else touches it, and how to make it go away.

We do not sell your data. We do not run advertising. We use Firebase Analytics to understand app usage (in the EU, EEA, UK and Switzerland only if you allow it) and Firebase Crashlytics to diagnose failures, as described below.

Who we are

The Forge app is listed as “Forging” on the App Store and Google Play.

Forge is operated by Sargis Vanik Harutyunyan, IE, Apartment 16, 28 Tigran Petrosyan Street, Yerevan 0054, Armenia ("we", "us"), the data controller for the information described here.

Questions, requests, or complaints: privacy@forging.day.

What we collect

We collect information to provide coaching, manage accounts and subscriptions, understand app usage, and maintain the service. The categories below include information you enter and information generated when you use the app.

Account

We never see or store your password. Firebase Authentication holds a hash; sign-in with Google or Apple hands us a token, not a credential.

Training profile

Your goal, training experience, days per week, time budget, available equipment, injuries or limitations you tell us about, sex, birth year, height, and general activity level. Plus any durable notes you or the coach record about how you train ("knee flares on high-bar squats", "prefers mornings").

Some of this — injuries, sex, height, bodyweight — is health-related data. In the EU/UK it is a special category of personal data, and we process it only on the basis of your explicit consent, which you give when you create your account — before you enter any of it. We record the date and time you consented and the version of each document you agreed to. You can withdraw that consent by deleting your account, which also erases that record.

This consent also covers reviewing a coach reply you choose to report, because a reply can mention health information.

Training records

Programs, planned sessions, and what you actually did: exercises, sets, reps, weights, holds, rest, reps-in-reserve ratings, session notes, timestamps, and bodyweight or body-measurement entries you log.

Coach conversation

The messages you exchange with the AI coach. If you add a photo to the chat, it stays on your device: it is not sent to us or to the coach. The app reads a photo only after you pick it and never browses your library on its own.

Reports of AI content

If you report a coach reply, we store that reply, the reason you chose and your note. If you report AI content from Profile, we store the reason and your note. Each report also records the app version, platform and language. It is linked to your account and is never sent to the AI coach.

Subscription status

Whether you have an active subscription, which plan, and when it renews or lapses. We never receive your card number, bank details, or billing address. Payment is handled entirely by Apple or Google. RevenueCat links your account identifier to subscription information and sends our server subscription events, including entitlement status and purchase or expiry timestamps, to manage access.

App analytics

We use Google Firebase Analytics to understand how people use Forge and improve the app. We record screen views and events such as sign-in, workout completion, coaching errors, and subscription interactions. Event details are limited to categories, such as the subscription plan or why a request failed; they never include what you logged in a workout. We also send broad profile categories: age band, training experience, and training days per week.

For signed-in users, we send a hashed version of the account identifier to associate analytics with the same account. This is a pseudonym, not a guarantee of anonymity. Our custom analytics events and profile categories do not include your name, email address, raw birth year, sex, coach messages, or free-text notes. We do not collect your device's advertising identifier, and analytics data is not used for advertising.

Your choice. In the EU, EEA, UK and Switzerland, analytics stays off until you choose. We ask once: after sign-up, or on your next launch if you already have an account ("Help improve Forge"), and nothing is measured unless you tap Allow. Elsewhere, analytics is on by default. Everywhere, you can turn it on or off at any time in Profile → Account → Help improve Forge. We work out which applies from your device's region and time zone: if either looks European, or we can't tell, we ask. Your choice is stored with your consent records. Your device remembers your last choice when you sign out. Turning analytics off stops collection on this device and clears the analytics identifier Firebase keeps on it. On a device where you previously allowed analytics, Firebase may record the start of an app session in the moment before the app applies your current choice.

Diagnostics

If the app crashes, Firebase Crashlytics sends us a crash report containing the stack trace, device model, OS version, and a pseudonymous identifier (a one-way hash of your account identifier, the same one used for analytics) so we can tell whether a bug hit one person or everyone. Crash reports contain no training data and no coach conversation.

Device settings

Theme, haptics, language, and units. Stored so the app looks the same on your next launch.

What we do not collect

We do not request access to your GPS location or contacts. App usage analytics are described above; the website has separate practices described below.

The forging.day website sets no cookies. It counts visits with Cloudflare Web Analytics, which stores nothing on your device and does not fingerprint you: it records the page you opened, the site that linked to it, your browser and device type, and your approximate country. We do this on the basis of our legitimate interest in understanding how the website is used. Fonts are served from our own domain, not a font CDN.

How the AI coach uses your data

To create your coaching, Forge sends your coach messages, training data and health information (such as injuries, sex, height and bodyweight) to a third-party AI service provider that processes them on Forge's behalf. You agree to this explicitly, with the checkbox you tick when you create your account.

The coach runs on our server and calls an AI model operated by our AI service provider. Two things are worth knowing about how that call is built:

1. We omit structured account identity fields from the coaching context. The context includes training profile information, workout history, and coaching notes, with a derived age rather than your birth year. We do not add your name, email address, or account identifier as identity fields. We also send coach conversation text and your answers. Messages and free-text notes may contain identifying or sensitive information you choose to include; removing structured identity fields does not anonymise that text.
2. The AI service provider processes it on our behalf, as our processor, under commercial terms that do not permit training models on our inputs or outputs.

Everything the coach writes back — a program, a session, a note — is re-validated against our own schemas before it is stored.

Who else processes your data

The following services process information for Forge or provide services directly to you. Apple and Google act as independent controllers for payment data, as noted below.

If you are in the EEA, UK, or Switzerland, this means your data is transferred to the United States. Those transfers rely on the European Commission's Standard Contractual Clauses (and the UK Addendum where relevant), incorporated into our agreements with each processor.

Legal bases for processing

Under the UK/EU GDPR:

• Performance of a contract — running your account, storing your training data, generating and adapting your program, managing your subscription.
• Explicit consent — health-related data (injuries, sex, height, bodyweight). Given at account creation, before any of it is entered. Withdrawable at any time by deleting your account, which erases the consent record along with everything else. It also covers reviewing a coach reply you choose to report.
• Consent — app analytics in the EU, EEA, UK and Switzerland. Withdraw it at any time in Profile → Account.
• Legitimate interests — keeping the service secure and abuse-free (rate limits, crash diagnostics) and understanding how the app is used so we can improve it (app analytics outside the EU, EEA, UK and Switzerland, which you can switch off in Profile → Account). We have weighed this against your rights; you can object using the contact address above. We also rely on it to review the reports you send about AI content, to keep coaching safe.
• Legal obligation — where we must keep records or respond to lawful requests.

How long we keep it

Your data stays while your account exists. Delete your account and we delete it — your profile, programs, sessions, coach conversation, notes, and measurements are removed from Firestore in full. We keep no copy of your workouts.

Account deletion also removes the associated Firestore billing and consent records and triggers a request to delete the RevenueCat subscriber record. It does not delete purchase records held independently by Apple or Google or cancel a store subscription; manage that subscription through the relevant store.

Usage records: to run the coach, our server keeps daily records of how much you used it and short-lived rate-limit counters. They hold counts and costs, not your training data or messages. Daily usage records are deleted automatically 90 days after the day they count, rate-limit counters after 7 days, and the spending total for each billing period 120 days after that period starts. Any that remain are deleted when you delete your account.

Reports: a report you send about AI content is deleted automatically 90 days after you send it, or sooner when you delete your account.

Server logs: our server's logs can contain your account identifier, for example when a request fails or when an account is deleted. They are kept for 30 days and then deleted; deleting your account does not remove them sooner.

Crash reports are retained by Crashlytics for up to 90 days.

Analytics data is kept for 14 months. While you are signed in it is linked to the hashed account identifier; otherwise it is linked only to the analytics identifier Firebase keeps on your device. It is not deleted when you delete your account.

Your rights

Wherever you live, you can ask us to:

• give you a copy of your data (access / portability),
• correct it,
• delete it,
• restrict or object to processing,
• withdraw consent you previously gave (for analytics: Profile → Account → Help improve Forge).

You can correct your profile and delete your account in the app, under Profile. Delete account (Profile → Account) erases everything as described above. For a copy of your data, or anything else, email privacy@forging.day and we will respond within 30 days. We will not charge you or degrade your service for exercising a right.

If you are in the EEA or UK you may also complain to your local data protection authority. If you are in California, we confirm we have not sold or shared personal information in the preceding 12 months, and we do not process it for cross-context behavioural advertising.

Security

Access is enforced per account at the database layer: our security rules deny everything by default and let you read and write only your own subtree. Some paths — your subscription entitlement and the coach's own messages — are readable by you but writable only by our server, so they cannot be forged from a device. Internal records such as usage counters cannot be read or written from a device at all; only our server uses them. All traffic is TLS-encrypted, and data is encrypted at rest by Google Cloud.

No system is perfect. If we discover a breach affecting your personal data, we will notify you and the relevant regulator as required by law.

Children

Forge is for adults only. You must be at least 18 to use it. We do not knowingly collect data from anyone under 18; if we learn we have, we delete it. If you believe someone under 18 has an account, tell us at privacy@forging.day.

Changes

If we change this policy we will update the effective date above and, for changes that materially affect you, tell you in the app before they take effect. The current version always lives at https://forging.day/privacy.

Contact

privacy@forging.day — Sargis Vanik Harutyunyan, IE, Apartment 16, 28 Tigran Petrosyan Street, Yerevan 0054, Armenia.