Version control

Version control for
legal & policy documents.

Track every change, redline any two versions, classify major vs minor, and automatically bring users current on the latest text — without leaving a single audit gap.

Permanent, sealed versions Word-level redlines Re-consent automation
terms-of-service · history
4 versions
  • v3.1.0minorJun 12Typo + clarification
  • v3.0.0majorMay 04Liability cap raised; venue moved
  • v2.4.1minorApr 18Updated contact details
  • v2.4.0minorMar 22Added AI usage clause
The problem

Most teams manage their legal documents in places that can't tell them what changed.

No real version history

Word and Docs overwrite history. When counsel asks what changed in March, no one can produce the exact text — or the exact diff.

Major changes aren't flagged

There's no consistent way to decide which changes warrant re-consent, so either every user is nagged or none of them are.

Stale users keep accumulating

Each new version creates a long tail of users still bound to old text, with no automated way to bring them current.

How Termitude solves it

One platform for the whole document lifecycle.

Permanent versions

Every publish is sealed and retained forever. Reference any past version by ID for evidence, redlines and audit trails.

Word-level redlines

Side-by-side diffs between any two versions, so counsel or reviewers can see exactly what changed.

AI change analysis

Plain-English changelog per version and a suggested major or minor classification you can accept or override.

Re-consent engine

Leave it informational, notify users, or force re-acceptance — Termitude works through the outstanding cohort and reports back as users re-accept.

Diff anything

Side-by-side redlines for any two versions.

Compare v3.1 to v2.0 the same way you compare v3.1 to v3.0. Word-level adds and removals, clause-aware grouping, and an evidence-ready view for counsel.

  • Word-level additions and deletions
  • Compare any two versions, not just adjacent
v3.0.0

Liability is capped at $100 USD.

v3.1.0

Liability is capped at 12 months of fees.

Bring users current

Re-consent automation that runs itself.

Publish a major change and Termitude identifies every user still on a stale version. Pick a strategy per document — and watch the outstanding cohort drain.

  • Outstanding-user dashboard per document
  • Policies: none, notify, forced
  • Webhooks fire as users re-accept
  • Evidence pack rebuilt automatically
OUTSTANDING1,284
2,612 accepted67%
FAQ

Common questions

How do I track changes between policy versions?
Every publish in Termitude creates a permanent version with its own content fingerprint. You can open a side-by-side word-level redline between any two versions — not just adjacent ones — and share a permalink with counsel.
What's the difference between a major and a minor policy change?
A major change materially alters user rights or obligations (pricing, liability, privacy, termination) and usually triggers re-consent. A minor change is a typo, formatting fix, or clarification. Termitude classifies each change automatically and lets you override it.
How is this different from Git or a CMS?
Git versions code; a CMS versions web pages. Neither classifies legal changes, generates plain-English summaries, links versions to user acceptance, or runs re-consent workflows. Termitude does, because every version is tied to a consent ledger.
What triggers re-consent for users?
You configure the rule per document. A major version can be left informational (none), surface a re-consent prompt (notify), or require re-acceptance before the user can proceed (forced). Minor versions carry the existing acceptance forward.
Do you publish a changelog automatically?
Yes. Termitude generates a public version history page for each document, with AI-written summaries of what changed and optional redline view — a trust page out of the box.

Know what changed, who accepted it, and when.

Free to try. No card required.