Mercurial Privacy By Default

Mercurial Privacy By Default changes that story. It strips away accidental exposure before it happens. No extra flags. No hidden settings. Every commit assumes the minimum disclosure needed to maintain the code and nothing more. Metadata, logs, and annotations stay under your control, not scattered across servers where you lose track of them.

With Mercurial Privacy By Default, the default workflow respects personal and organizational boundaries. Author information is protected unless explicitly revealed. Commit messages carry only the data you choose. This approach makes privacy not a side feature but the baseline mode of operation.

Security teams benefit from fewer leaks of identifiable info. Compliance stays tighter because sensitive attributes never enter the repository in the first place. Developers move faster because they spend less time scrubbing histories or rewriting commits. The default branch is cleaner, safer, and easier to audit.

Configuring this is not an afterthought. It is embedded in the core behavior of modern Mercurial. Every clone and push follows the same privacy-first rules. No separate extensions to maintain. No conflicts between local and remote privacy policies. The same predictable behavior applies across the workflow.

Mercurial Privacy By Default is more than a technical upgrade—it’s a shift in how teams think about code history. It assumes your data is valuable and keeps it locked down until you decide otherwise. That reduces risk at scale while keeping development friction low.

See how privacy-first version control runs in real time. Try it with hoop.dev and have it live in minutes.