Policy Versioning

Every change to a published policy creates a new version. This ensures a complete audit trail: every consent receipt records the exact policy version active at the time of the user's decision.

Version numbering

Versions are integers starting at 1. Each publish increments the version: v1 → v2 → v3.

When to publish a new version

Publish a new policy version when you:

• Add a new vendor to your site
• Remove a vendor
• Change a vendor's category (e.g. move a tool from functional to marketing)
• Add or change a consent purpose
• Make a material change to your data processing

Minor changes (fixing a typo in a description, adding a translation) do not need a new version — use Save Draft and publish when ready for a significant update.

Impact on existing consent

When you publish a new policy version:

Scenario	What happens
User consented to v1, new v2 published	User sees banner again on next visit
User consented to v2	No banner re-shown until v3 is published
User has no stored consent	Banner shown regardless

Rollback

If you need to revert to a previous version:

1. Go to Policy → Version History
2. Find the previous version
3. Click Restore — this creates a new version with the content of the old one

You cannot delete or modify a published version. The audit trail is immutable.

Version history

All published versions are stored permanently. View the history at Policy → Version History.

Each version shows:

• Published date
• Who published it
• A diff from the previous version
• How many consent receipts reference this version