Audacity Forks Created After 2021 Policy Changes

In 2021, the acquisition of Audacity by Muse Group and the subsequent introduction of controversial privacy policy updates sparked significant backlash within the open-source community. Users and developers objected to the inclusion of telemetry, network connectivity, and vague data-collection terms in what had historically been a completely offline audio tool. In response, several community-driven, open-source forks emerged to provide clean, telemetry-free alternatives to the original digital audio workstation.

The Catalyst: The 2021 Privacy Policy Controversy

In May 2021, Muse Group acquired the Audacity project. Shortly afterward, proposals to implement basic telemetry and error reporting surfaced. The situation escalated in July 2021 when an updated privacy policy was published, stating that Audacity could collect IP addresses, system specifications, and data deemed necessary for "law enforcement." The policy also attempted to restrict users under the age of 13, violating the GNU General Public License (GPL) terms regarding use restrictions. Although Muse Group later revised the policy and clarified their intentions, the initial trust was broken, prompting developers to branch the codebase.

Primary Audacity Forks

1. Tenacity

Tenacity became the most prominent and organized long-term community fork. Created to preserve a completely telemetry-free experience, the project aimed to:

• Strip out all tracking code, network calls, and crash-reporting services.
• Maintain strict adherence to the GPL license without corporate-style user agreements.
• Modernize the legacy codebase while retaining full functional parity with Audacity.
• Implement community-requested features, such as improved UI themes and expanded plugin support.

Tenacity established an open governance model to ensure no single corporate entity could alter the software's privacy terms in the future.

2. Audacium

Audacium was launched almost simultaneously with Tenacity by developers who wanted not only to remove network-dependent code, but also to heavily refactor Audacity’s interface and architecture. Key focuses of Audacium included:

• Total removal of telemetry, analytics, and update checkers.
• Experiments with user interface modernizations, including streamlined menus and customizable workspaces.
• Codebase cleanup to make contributing easier for independent open-source developers.

3. Sneedacity

Sneedacity was the very first fork to gain viral traction immediately following the policy update. Named after an internet meme, it served as an immediate protest fork created purely to excise telemetry, automatic network connections, and crash-reporter modules from the source code. While its origin was somewhat informal, Sneedacity demonstrated how quickly the community could replicate the software without corporate oversight, and it laid the technical groundwork that fed into more formalized projects like Tenacity.

Current Status of the Ecosystem

Following the intense backlash and the rise of these forks, Muse Group walked back the most aggressive provisions of their privacy policy, removing third-party telemetry and clarifying that any future data exchange (such as checking for software updates) would remain strictly opt-in. Because the official version of Audacity returned to a privacy-friendly baseline, development momentum on forks like Tenacity and Audacium eventually slowed, though their repositories remain accessible as community-governed fallbacks.