Privacy Policy

Last updated · May 18, 2026

At a Glance

We built Forge because we were frustrated with how other fitness apps treat their users. This policy is meant to be the same way: plain language, no surprises, no fine print designed to hide things.

The short version:

  1. We collect the minimum we need to run the app.
  2. We do not sell your data. We do not share it for advertising. We do not show advertising inside the app.
  3. We do not send you marketing emails. We do not send you any emails.
  4. Your workout data is yours. You can view it, export it, and delete it whenever you want.
  5. The AI Coach and voice-to-text features send data to the services that power them (Anthropic and OpenAI) only when you use those features. Those services do not retain or train on your data.
  6. The only way your data is ever shared with another person is the Partner feature, which is fully opt in and entirely under your control.

The rest of this policy explains all of this in more detail. If anything here is unclear, email us at legal@forgeworkouts.com and we will fix it.

1. Who We Are

Forge is operated by Forge Health and Fitness LLC (“Forge,” “we,” “us,” or “our”). This policy explains what information we collect about you when you use Forge, how we use it, and the controls you have over it.

2. What This Policy Covers

This policy covers your use of the Forge mobile app on iOS and Android, and the web-based version of Forge. It applies to information collected through any of these surfaces.

The web-based version of Forge is a convenience for using the app on a larger screen. All purchases and subscription management happen through Apple’s App Store or Google Play. Forge does not accept payment directly through the web or anywhere else.

Where Forge is offered. Forge is intended for and offered to residents of the United States. The Forge mobile app is listed only on the United States storefronts of the Apple App Store and Google Play. Subscriptions and paid plans are available only through those storefronts. We do not direct or market Forge to residents of the European Economic Area, the United Kingdom, or any other region.

Because Forge uses Google and Apple as sign-in providers, we cannot inject our own region check into the sign-up flow. A user with a Google or Apple account from outside the United States could technically create a free Forge account through the web. We do not encourage this. If you are located outside the United States, you should not use Forge. Our policies, infrastructure, and operational practices are designed for US users and US legal frameworks.

If you do sign up from outside the United States despite this notice, we will make a best effort to honor your privacy rights, including reasonable requests under your local laws. We cannot guarantee compliance with regulations of regions where we do not operate.

3. Information You Provide to Us

3.1 Account Information

When you sign up for Forge, you sign in through Google or Apple. We receive the following from those providers:

  1. Your first name
  2. Your last name
  3. Your email address (used as the unique identifier for your account)
  4. Your profile photo, if your account with the provider has one

We do not store your password. Authentication is handled by Google or Apple.

You can sign in with either provider on either platform. That means you can use a Google account on an iPhone or an Apple account on Android. This is intentional so you can move between devices without losing access or being forced to re-subscribe.

3.2 Optional Demographic Information

If you choose to, you can tell us:

  1. Your age range (18 to 24, 25 to 34, 35 to 44, 45 to 54, 55 to 64, or 65+)
  2. Your gender (male, female, non-binary, or prefer not to disclose)
  3. Your country
  4. Your training experience level

All of these fields are blank by default. You are never required to fill them in to use Forge. You can update or clear them at any time in your settings.

Demographic information is entirely optional, and by design, there is no way to indicate to us that you are under 18. The age range options start at 18 and up. We would rather not know identifying personal characteristics of any user under 18.

3.3 Training Data

When you use Forge, you create training data. This includes:

  1. Workouts you log, including the exercises performed, sets, reps, weights, equipment used, exercise variants, and any notes you add.
  2. Templates you create or save, including which exercises they contain.
  3. Splits and plans you set up, including the structure of your training week.
  4. Settings and preferences such as training focus (hypertrophy, strength, fat loss, etc.), progressive overload preferences, default set counts, default warmup sets, units (kg or lbs), language, and timezone.
  5. Custom exercises you create, including any descriptions you write.
  6. Favorites, pinned items, and organizational choices you make to customize how Forge presents your library.
  7. Usage patterns within your account, such as how often you use specific templates or exercises. This is used only to help us surface your most-used items when you search or sort your library. It is not used for any external purpose or shared with anyone.

This is the core of what Forge does. We need this data to give you the workout tracking experience you signed up for.

3.4 Health and Body Measurements

If you choose to, you can also record:

  1. Body weight, when set as a goal or otherwise logged.
  2. Body measurements such as waist size, bicep size, or any other measurement you want to track.
  3. Habits and wellness markers you choose to log, such as sleep quality, daily steps, or any custom habit you create.
  4. Personal records and strength progress, which we derive automatically from your logged workouts.
  5. Goals of any type, including body weight goals, lift PR goals, body measurement goals, or custom metrics of your choosing.

All of this is optional and entirely under your control. You can leave every field blank and Forge will still work.

3.5 AI Coach Conversations and Memory

If you use the AI Coach feature (available on Elite, and on a limited bonus basis on Pro), we store:

  1. The conversation history between you and the Coach.
  2. Coach memory: observations and context the Coach saves to better understand your training. This might include any information you choose to share with the Coach that it should remember, such as injuries, preferences, training context, or other personal details relevant to your goals.

Coach memory is stored by Forge in our database. You can view, edit, or delete the memory at any time in your settings. You can also reset your conversation history at any point.

Encryption. Both your messages and the Coach’s responses are encrypted in transit and at rest. Under normal use, Forge staff cannot read the contents of your Coach conversations.

Reporting a Coach response. If you use the in-app feedback button to report a problem with something the Coach said, we need to be able to understand the context of the problem in order to improve the Coach. To do this, the reported response is decrypted along with the three messages immediately preceding it, and made available to Forge administrators for review.

This means that if those preceding messages contained personal information that you shared with the Coach, that information may become visible to Forge administrators reviewing your report. Outside of this report flow, Coach conversation contents remain encrypted at rest and inaccessible to Forge staff.

When the Coach generates a response, the relevant context (including conversation history and memory) is sent to our AI provider (Anthropic) to produce the response. Anthropic does not retain or train on this data. See Section 6 for more detail.

3.6 Feedback You Send Us

You can send us feedback through Forge in several ways:

  1. Bug reports, suggestions, and ideas submitted through the in-app feedback form.
  2. Up or down votes on AI Coach responses.
  3. Up or down votes on help center articles.

All of this feedback is anonymous by design. When you submit feedback, we do not capture your user identifier or any information that would tie the submission back to you. We do this on purpose so you can give honest feedback without thinking about it. The tradeoff is that we cannot reply to feedback directly. If you want a response from us, please email help@forgeworkouts.com instead of using the in-app forms.

3.7 A Note About What You Enter

Information you choose to enter into Forge is stored as you provide it. Forge contains many places where you can name things, write descriptions, and add notes. Some examples of what this covers:

  1. Names and titles for the things you create or use, such as workout names, split names, custom exercise names, template names, goal labels, and habit names.
  2. Descriptions you write, such as custom exercise descriptions and template descriptions.
  3. Notes you add, such as overall workout notes and per-exercise notes within a workout.
  4. Conversation content you share with the AI Coach.

This list is not exhaustive. Anywhere in Forge that you can type free text, that text is stored. Most of this data is stored in plain text in our database.

We recommend you avoid entering personal information into descriptions, names, titles, or other free-text fields that you would not be comfortable being stored on our system. This includes things like real names, addresses, phone numbers, medical record numbers, or other identifying details. The app does not require any of this to function, and the more you put in plain-text fields, the more there is to potentially expose in a worst-case scenario.

4. Information Collected Automatically

4.1 Technical Data

When you use Forge, we collect the following technical information involved in operating the service:

  1. IP address
  2. Device type, operating system, and OS version
  3. App version and build number
  4. Browser or user agent (when using the web interface)
  5. Session identifiers and authentication tokens

This information is used to operate the service securely and to support functions like rate limiting, abuse prevention, and enforcing account suspensions. We will never use this information for advertising, sell it, or share it with third parties for their own purposes.

Authentication tokens (JWTs) are managed for session purposes. Refresh tokens used to keep you signed in are stored securely on your device (in the system keychain on iOS or the equivalent secure storage on Android).

4.2 Crash and Error Reports

When Forge encounters a crash or unexpected error, we collect a crash report so we can fix the problem. A crash report can include:

  1. Device type, operating system, app version, and build number
  2. User agent
  3. Date and time of the crash
  4. The screen or feature where the error occurred
  5. The error message, stack trace, and other technical details associated with the crash

Crash reports do not identify the user who experienced the crash. The contents of a crash report can vary depending on what was happening when it occurred, but they are sent without account-level identifying information attached.

4.3 Cookies

Forge does not use cookies. This applies to our mobile apps, our web app, our marketing site, and our help center. If we add cookies in the future, we will update this policy and provide an appropriate consent mechanism before they are enabled.

5. How We Use Your Information

We use the information we collect to:

  1. Run the app and give you the workout tracking experience you signed up for.
  2. Provide the AI Coach when you use it, including remembering context across conversations.
  3. Transcribe voice input when you use voice-to-text logging.
  4. Understand the health of the app through aggregate, non-identifying data such as total workouts logged, active users, signup trends, and the distribution of users across age ranges and tiers.
  5. Prevent abuse and protect the service, including rate limiting, blocking abusive behavior, and enforcing account suspensions when necessary.
  6. Improve the app by reviewing anonymous feedback and crash reports.

We do not use your information for advertising, profiling for advertising, or any kind of marketing.

6. AI Features and the Services That Power Them

6.1 Anthropic (AI Coach)

If you use the AI Coach, the following data is sent to Anthropic to generate a response:

  1. The relevant portion of your conversation with the Coach.
  2. The Coach memory associated with your account.
  3. Context about your training that the Coach needs to give a useful response, such as recent workouts, your plan, and your goals.

Anthropic processes this data only to generate the Coach response. Anthropic does not retain your data after the response, and does not use your data to train its models. This is governed by our commercial agreement with Anthropic.

Coach memory is stored by Forge. It is transmitted to Anthropic only as part of the request when you interact with the Coach. You can view, edit, or wipe the memory at any time.

6.2 OpenAI (Voice-to-Text and Help Article Embeddings)

We use OpenAI in two specific ways:

  1. Whisper (voice-to-text): If you use voice input to log a workout or talk to the Coach, your audio is sent to OpenAI’s Whisper API for transcription. The audio is not retained by OpenAI and is not used to train OpenAI’s models.

  2. Embeddings for help articles: Our help center articles are processed through OpenAI’s embeddings API so the AI Coach can refer to them when answering your questions. This processing involves our own help article content, not your personal data. Your training data, conversations, or any personal information are never sent to OpenAI through this path.

6.3 No Other AI Services

We do not send your data to any other AI service. If we add new AI features in the future, we will update this policy and disclose which services are involved before the feature goes live.

7. The Partner System

The Partner system is the only way your data is ever shared with another person, and it is entirely opt in.

How it works

  1. A Partner (such as a training buddy, accountability partner, or personal trainer who uses Forge) generates a code from their account and gives it to you.
  2. You enter the code in your Forge app. This establishes a one-way link: you are sharing data with them.
  3. By default, only your first name and last initial are shared. Everything else is off.
  4. After the link is established, you can choose, item by item, what to share. The available categories are:
    • Recent workout history
    • Plan, goals, and strength progress
  5. We do not share your demographic data, email, or any other personal information through the Partner system regardless of what you opt in to.
  6. The partner can also choose to share their data back with you, item by item, on their own side. The two directions are independent.

Security by design

Codes are unique at the time they are generated, and each code represents a single active linking attempt. Codes expire after 24 hours, and generating a new code invalidates the previous one.

Because Partner codes are short (similar in format to the pairing codes you might use when linking a phone to a TV), an expired code value may be reused in the future for a completely different linking attempt by a different user. This poses no risk to you. Once a code expires, it is no longer associated with any active link or any prior user’s data, and any future use of the same code value is a separate linking attempt that requires its own consent and sharing setup from scratch.

The architecture is designed so that even if a code were intercepted, the worst possible outcome is that the holder of the code receives data from the person who entered it. A code cannot be used to extract data from someone else. Only entering a code creates a sharing relationship, and only in the direction of the person who entered it toward the person who generated it.

Generating a Partner code requires a Pro or Elite subscription.

Unlinking

You can unlink any Partner at any time. Once unlinked, the Partner immediately and permanently loses access to your data in their Forge account. No previously shared data remains visible to them.

What we cannot control

Once you choose to share information with a Partner, that information is visible to them within their own Forge account. We cannot control what a Partner does with information they have seen, including whether they remember it, take notes, or take screenshots. You should only enter codes from people you trust.

8. HealthKit (iOS) and Health Connect (Android)

Apple HealthKit and Google Health Connect are the platform-level systems for fitness and health data on iOS and Android, respectively. Forge integrates with these systems in a deliberately limited way:

  1. Forge does not read any data from HealthKit or Health Connect. We do not pull in body weight, heart rate, steps, calories, sleep, or any other information from your platform’s health system.
  2. Forge writes a workout receipt to HealthKit or Health Connect when you grant permission. A workout receipt is a short record consisting of the workout name and its duration or timestamp. This lets your workouts appear in your platform’s native health app alongside other activity.
  3. The detailed contents of your workouts (exercises, sets, reps, weights, notes) are not written outward. Those remain only in Forge.

You control whether Forge writes anything to your platform’s health system. You can grant or revoke this permission at any time in your device’s system settings.

Rules for HealthKit and Health Connect data:

  1. Forge does not use data exchanged with HealthKit or Health Connect for advertising.
  2. Forge does not sell this data.
  3. Forge does not share this data with any third party for that third party’s use.
  4. Data written to HealthKit or Health Connect is used only to provide the receipt-writing feature you have asked us to provide.

9. Future Integrations

Over time, we expect to add integrations with services like Fitbit, sleep trackers, smart scales, and similar tools. The intent is to let you bring in data you would otherwise have to enter manually, such as body weight progress or sleep tracking for habits.

When we add any new integration, the following rules will always apply:

  1. Explicit consent. Nothing will flow in or out without your explicit opt in.
  2. Per data type and direction. You will choose, by specific data type, whether data is read from the service, written to the service, or both.
  3. Disclosure. We will update this policy and notify users before any new integration goes live.

10. Who We Share Information With

We share information only with the following:

  1. Anthropic, when you use the AI Coach, to generate Coach responses.
  2. OpenAI, when you use voice-to-text (audio), and as part of how the AI Coach references our help articles (our content, not yours).
  3. Supabase, our infrastructure provider, which hosts our database and authentication systems.
  4. Google Cloud, which hosts our backend API and middleware services.
  5. Cloudflare, which provides our content delivery network (CDN) and edge services.
  6. Apple HealthKit and Google Health Connect, to the extent you have opted in to writing workout receipts to these platform systems. See Section 8.
  7. Apple and Google, for app distribution and billing through their respective app stores.
  8. Partners you have linked, only for the data categories you have explicitly opted in to share.

We do not sell your information. We do not share it with advertisers. We do not allow any third party to use your information for their own purposes. Our agreements with the services above limit them to processing your data on our behalf for the purposes described in this policy.

Legal requests and government authorities. We may be required to disclose your information in response to a valid legal request, such as a subpoena, court order, or other lawful demand from a government authority. When we receive such a request:

  1. We will only comply with requests we determine are legally valid and properly scoped.
  2. We will narrow our response to what is specifically required, rather than over-producing data.
  3. We will notify you of the request whenever we are not legally prohibited from doing so, so that you have an opportunity to respond or seek legal advice.
  4. We will challenge requests that we believe are overbroad, improperly directed, or not legally valid.

We may also disclose information if we have a good-faith belief that doing so is necessary to protect the safety of any person, prevent fraud or abuse of the service, or enforce our Terms of Service.

Where our service providers process data. Forge is operated from and offered to the United States. Our infrastructure and AI providers are configured to process data within the United States to the extent we control these settings:

  1. Supabase is configured to process data in the United States.
  2. Google Cloud is configured to process data in the United States.
  3. Anthropic inference is configured to the United States.

OpenAI is the exception. We use OpenAI for voice-to-text transcription (Whisper) when you use voice input, and for processing embeddings of our own help articles. At present, OpenAI’s geographic routing setting for our usage is global, which means audio sent for Whisper transcription may be processed by OpenAI infrastructure in any region they operate. OpenAI’s commercial terms prohibit retention of this data or its use to train their models. We will move to United States-only routing for OpenAI if and when that becomes available to us as a control.

For some providers, particularly content delivery networks like Cloudflare, traffic may be routed through edge locations closer to your device for performance reasons. This is the nature of those services and not always within our direct control. We require all service providers to maintain protections consistent with this policy regardless of the region in which data is processed.

We may operate from additional regions within the United States over time to reduce latency and improve reliability. We do not host or process Forge user data outside the United States, with the OpenAI exception noted above.

11. Where Your Data Lives and How It Is Protected

Your data is stored on Supabase in the United States. We may operate from additional regions within the United States in the future for performance and reliability, but we do not host data outside the United States.

Security practices include:

  1. Encryption in transit using TLS for all connections between your device and our servers.
  2. Encryption at rest for AI Coach conversation data.
  3. Row-level security in the database so that your data is isolated from other users.
  4. Authentication through Google or Apple, with refresh tokens stored in your device’s secure storage.
  5. Rate limiting and other protections against abuse.

Local storage on your device. Forge stores some data locally on your device because the app needs it to function. Specifically:

  1. Authentication tokens are stored in your device’s secure storage: the system keychain on iOS, the equivalent secure key store on Android, and localStorage in your web browser.
  2. Cached data for app responsiveness is stored in IndexedDB (for the React Query persistent cache) and the service worker cache (for the app shell).
  3. OAuth sign-in transfer uses a URL hash fragment briefly during sign-in. This is transient and not persisted.

This storage is local to your device, is necessary for the app to work, and cannot be disabled while using Forge.

No system is perfectly secure, but we take reasonable steps to protect your data and to limit what we collect in the first place.

12. Security Incidents and Breach Notification

If we become aware of a data breach that affects your personal information, we will notify you as soon as reasonably possible after we determine the scope of the incident, and in any case within 30 days of discovery. Because Forge does not have an email channel to its users, this notification will be made through an in-app advisory: a banner displayed prominently when you next open the app, which you can tap to view the full details. We will also post the notice in the in-app “What’s New” section.

The notification will describe what happened, what information was affected, what steps we are taking in response, and any steps you can take to protect yourself.

Due to the nature of our infrastructure, any meaningful security incident would most likely affect all users, not a subset. As a result, any breach notification we send is likely to reach you regardless of whether your specific data was directly compromised. We would rather over-notify than risk leaving anyone uninformed.

Realistic risk profile. The information at risk in a hypothetical breach is limited to what we actually collect: your first name, last name, email address, and profile photo from your sign-in provider; any optional demographic information you chose to disclose; your training data, settings, goals, habits, and any AI Coach data if you used the Coach. Forge does not collect or store payment information of any kind. All subscription billing is handled by Apple and Google through their app store systems, and Forge never receives your payment method details. Forge also does not collect or maintain other personally identifying information beyond what is described in this policy.

No breach should be minimized, but your realistic exposure in such an event is bounded by the limited scope of information we collect in the first place.

13. How Long We Keep Your Data

Forge retains your data for as long as your account exists. This includes your account information, training data, settings, goals, habits, Coach conversations, and Coach memory.

What we mean by “anonymization.” Throughout this policy, “anonymization” refers to a specific process. We set your personal identifying information (your name, email address, and profile photo) to null in our database, and we sever the link between your account and your historical data (workouts, goals, habits, custom exercises, and Coach data). The historical data is not immediately deleted. It remains in our database in disassociated form so it can support aggregate analytics, but it is no longer attached to you. Disassociated data may be deleted later as part of routine database maintenance, but we do not commit to a specific timeline for that.

You can change what we retain at any time using the controls described in Section 14. When you delete an item within the app, the underlying record is retained with a “deleted” flag for referential integrity and aggregate analytics. When you reset your account, your training data is anonymized while your profile and settings remain in place. When you delete your account, anonymization applies to both your training data and your profile.

We reserve the right to delete or anonymize accounts that have been inactive for two or more years. We do not currently have an automated mechanism for doing this. If we begin to enforce this in the future, we will announce it through the in-app “What’s New” section before any inactive account is removed.

14. Your Controls

You have meaningful control over your data in Forge.

  1. View your data. Everything you have logged or entered is visible to you in the app.
  2. Edit your data. You can change or correct anything you have entered.
  3. Export your data. You can export your workout history at any time.
  4. Manage your AI Coach memory. You can view, edit, or wipe the memory in your settings. You can reset your conversation history at any time.
  5. Unlink Partners. You can unlink any Partner at any time with immediate effect.
  6. Delete items within the app. When you delete something within Forge (such as a template, custom exercise, workout, split, or goal), it is removed from your view. The underlying record is kept in our database with a “deleted” flag set, so that other parts of your history that reference it continue to work correctly. For example, a past workout that used a now-deleted template will still display properly rather than break with missing-data errors. These records are not visible to you, are not used to restore items, and serve only to keep your existing history coherent and support aggregate analytics that do not identify you.
  7. Reset your account. Resetting your account triggers the anonymization process for your training history (see Section 13 for the definition of anonymization). Your profile and settings remain in place, so you can keep using Forge without signing up again. We cannot reverse this action once it is taken.
  8. Delete your account. Deleting your account triggers the anonymization process for your training history, and also anonymizes your profile by setting your name, email address, and profile photo to null. After deletion, there is no remaining path from any record in our database back to you. We cannot reverse this action once it is taken.

You can also update or clear any of your demographic information at any time.

A note about Partner sharing and account deletion. If you have shared data with a Partner and then reset or delete your account, the link between your shared data and your identity is severed by the anonymization process. The Partner will no longer see data attributed to you.

15. Anonymous and Aggregate Data

We use aggregate, non-identifying data to understand how Forge is performing as a product. Examples include:

  1. Total workouts logged across all users.
  2. Number of active users over a given time period.
  3. Signup trends over time.
  4. Distribution of users across tiers and (where disclosed) age ranges.
  5. Which help articles are most useful.
  6. Volume of feedback and crash reports over time.

This data does not identify individual users.

The in-app feedback you submit, the votes you give on AI Coach responses, and the up or down ratings on help articles are anonymous from the moment of submission. We do not capture your identity with these submissions and have no way of linking them back to your account.

16. Children and Minors

Forge is intended for users 13 years of age and older. We do not knowingly collect personal information from anyone under 13. If you believe a child under 13 has provided us with personal information, please email legal@forgeworkouts.com and we will delete it.

In addition, regardless of legal requirement, we do not request or collect demographic information from any user under 18. Demographic fields are only available to users who have affirmatively indicated they are 18 or older. We do not want to know identifying personal characteristics of younger users.

17. Your Privacy Rights

Forge is intended for residents of the United States. Even where not strictly required, we apply standards similar to those that govern privacy under the European Union’s GDPR, because we believe these are good standards regardless of where you live.

You have the following rights with respect to your data:

  1. Right to access. You can view all the data we hold about you, primarily through the app itself. If anything is missing, you can contact us.
  2. Right to correction. You can edit any inaccurate information.
  3. Right to portability. You can export your workout data.
  4. Right to erasure. You can delete your account at any time.
  5. Right to restrict processing. You can pause or disable optional features (such as the AI Coach or platform health integrations).
  6. Right to object. You can contact us about how we process your data.

To exercise any of these rights, please email legal@forgeworkouts.com. We will respond to your request within 30 days. Where reasonably necessary, we may extend that by an additional 30 days and will tell you if we do.

No retaliation. We will not discriminate against you for exercising any of the rights described in this policy. We will not deny you service, charge you different prices, or provide a different quality of service in response to a privacy request.

We do not buy, sell, or share your personal information. This is true regardless of your state of residence, and it specifically includes California, where “sale” and “sharing” have specific meanings under the California Consumer Privacy Act (CCPA). Forge does not generate any revenue from selling, sharing, or licensing user data. We have no plans to do so in the future.

Our use of service providers like Anthropic, OpenAI, Supabase, Google Cloud, and Cloudflare is not a “sale” or “sharing” under CCPA or any comparable framework. Those providers process data only on our behalf, under contractual restrictions, for the specific purposes described in this policy.

If California, Virginia, Colorado, Connecticut, Utah, Texas, or another US state with its own privacy law grants you additional rights, we will honor those rights to the extent they apply. Contact us if you have questions about a specific state’s rules.

18. Changes to This Policy

Forge is an active product, and this policy will change over time as we add features, work with new services, or refine how things work. We want to be honest about how those changes are communicated.

For most changes, including the addition of new features and most operational refinements, we will update this policy and announce the change in the in-app “What’s New” section at the time the change takes effect. The “Last Updated” date at the top of this policy will tell you when it last changed.

For significant changes (such as changes to data retention, the addition or change of major service providers, or changes to the fundamental commitments in this policy), we will make a best effort to announce the change in the in-app “What’s New” section in advance, so that you have an opportunity to review it before it takes effect.

For changes in ownership, see Section 19. Ownership changes are always announced in advance where reasonably possible.

Minor changes (clarifications, formatting, typo fixes, and other non-substantive edits) may be made without separate notification.

A note on how we communicate. Forge does not send marketing or notification emails of any kind, and that includes emails about policy changes. This is a deliberate choice, but it does limit our ability to reach you directly when this policy changes. Because of this, we encourage you to review this policy from time to time. The “Last Updated” date at the top will tell you when it last changed.

If you ever want to talk through a change or have questions about something in this policy, email us at legal@forgeworkouts.com.

19. If Forge Changes Ownership

Forge is currently owned and operated by Forge Health and Fitness LLC. The commitments in this policy reflect the values and philosophy of its current ownership. We want to be honest about what that means.

While Forge is owned by us, we will operate it according to the commitments in this policy. We will not pivot to advertising, sell your data, or quietly change our data practices. These commitments are central to why we built Forge in the first place.

If Forge is ever acquired, merges with another company, or sells substantially all of its assets, your data will be among the assets transferred to the new owner. This is a normal part of how acquisitions work, but the new owner may have different values, business models, or priorities than we do.

In that situation:

  1. The new owner inherits this policy at the time of transfer and is bound by it as a starting point.
  2. The new owner may update the policy going forward under the same procedure described in Section 18.
  3. We will announce the change of ownership through the in-app “What’s New” section before the transfer takes effect, where reasonably possible.
  4. You will have the opportunity to export your data and delete your account before the transfer, if you do not wish for it to be carried over to the new owner.

We cannot promise what a future owner will do once they own Forge. What we can promise is that we will not transfer your data quietly. If the philosophy of Forge ever changes hands, you will hear about it through the channels available to us, and you will have a chance to act on it before the change takes effect.

20. Contact Us

If you have any questions about this policy or your data, contact us at legal@forgeworkouts.com.

Change Log

Notable changes to this policy are logged here, most recent first. We add an entry whenever we make a substantive update.