Termitude
Policy management software

The system of record for every
policy your users agree to.

Draft, approve, version and publish Terms, Privacy, DPA, AUP, AI and security policies — and prove which version each user accepted, on which device, on which day.

Approval workflows Versioned publication Auditable consent ledger
policies
acme.termitude.com
  • Terms of Service
    v3.1.0Published
  • Privacy Policy
    v2.4.2Published
  • Data Processing Agreement
    v1.7.0In review
  • Acceptable Use Policy
    v1.2.0Published
  • AI Usage Policy
    v1.0.0Draft
The problem

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

Policies are scattered

Terms in Docs, Privacy in the CMS, DPA in a PDF on a shared drive. No one can answer 'what's live right now?' without a meeting.

Changes ship without governance

Edits go straight to the website. There's no review trail, no sign-off, and no record of why a clause changed.

Acceptance can't be defended

When a regulator or customer asks which version a user agreed to, the best you have is a screenshot and a guess.

How Termitude solves it

One platform for the whole document lifecycle.

One library

Every policy — Terms, Privacy, DPA, Cookie, AUP, AI, SLA, Security — with owners, approvers and effective dates.

Approval workflow

Draft → Legal → Security → Executive → Published, with comments, change requests and electronic sign-off.

Versioned changes

Every edit creates a new version with a redline, AI change summary, and a major/minor classification.

Auditable consent

An append-only ledger sealed against each version's content hash. Evidence packs on demand.

Governance built in

Nothing reaches your users until the right people have signed off.

Configurable approval chains per policy type. Reviewers comment inline, request changes, and approve with an electronic signature. The full approval trail is part of the audit record.

  • Per-policy approval chains by role
  • Inline comments and change requests
  • Electronic sign-off recorded with version
  • Block publish until required approvers sign
01Draftauthor@acme
02Legal reviewapproved
03Security reviewapproved
04Executive sign-offpending
Publish and re-consent

Push updates everywhere — and bring users back to re-accept when it matters.

When a policy publishes, every hosted page, embed and SDK serves the new version automatically. Major changes can trigger notifications, force re-acceptance, or block access until the user agrees.

  • Hosted pages on your own domain
  • Web, iOS, Android, React Native, Flutter SDKs
  • Email, in-app and SMS notifications
  • Mandatory deadline or block-on-login
terms@v3.1.0notify12,481
privacy@v2.4.2re-accept9,302
dpa@v1.7.0block412
ai-policy@v1.0.0fyi—
FAQ

Common questions

What is policy management software?
Policy management software is a system of record for the policies an organisation publishes and asks people to agree to — Terms of Service, Privacy, DPA, AUP, AI usage, cookie and security policies. It owns drafting, approval, versioning, publication and acceptance evidence in one place.
How is Termitude different from a CMS or a contract tool?
A CMS publishes pages. A CLM tracks negotiated contracts. Termitude is built for the policies your users agree to: it versions every change, classifies major vs minor, routes approvals, publishes to web and mobile, and writes a signed ledger entry for every acceptance.
Can policies be approved before they go live?
Yes. Configurable workflows route drafts through legal, security and executive approvers with comments, change requests and electronic sign-off. Nothing publishes until the required approvers have signed.
How do you handle re-consent when a policy changes?
Each change is classified major or minor (with AI assistance and human override). Major changes can trigger email, in-app and SMS notifications, force re-acceptance at next login, set an acceptance deadline, or block access until accepted.
Does it support multiple jurisdictions and customer segments?
Yes. Each policy can have variants scoped by region, language, plan or customer segment. Variants version independently and the correct one is resolved at the API edge based on the request.
What evidence do we get for audits?
An append-only consent ledger keyed to each version's content hash. You can produce an evidence pack for any user or any version with the exact text they accepted, IP, user-agent, locale and timestamp — suitable for GDPR, SOC 2 and ISO 27001 audits.

Know what changed, who accepted it, and when.

Free to try. No card required.

Related
Terms management →Policy version control →All features →Security & trust →Developer docs →