Material changes, recorded clearly.

September 2026 — Proofline AI governance workflows

• Added AI Change Control records for AI releases, before-and-after snapshots, impact explanations, affected governance records, and owner/admin decisions.
• Added signed AI release passports using Ed25519 when a server-only signing key is configured.
• Added AI Passport JSON exports containing a registry snapshot, linked evidence metadata, recent audit history, and an integrity digest; exports are unsigned and are not attestations.
• Added governance fire drills that simulate configured scenarios against an in-memory copy and preserve drill results without model calls or production changes.

September 2026 — Trust and procurement foundation

• Expanded the public Trust Center and assurance-status disclosures.
• Published core subprocessors and a manually maintained Service Status page.
• Added a Legal Center, data-processing readiness statement, data-lifecycle disclosure, Cookie Notice, Support Policy, resilience overview, and vulnerability-reporting guidance.
• Added focused platform, framework, company, contact, glossary, and resource pages.

September 2026 — Controlled communications

• Added organization-scoped inbound email threads and owner/administrator Inbox access.
• Added Civerent live-chat conversation routing into the controlled Inbox workflow.
• Separated owner-facing Inbox naming from administrator-facing Inbox naming.
• Published support@civerent.com as the primary customer-support address.

September 2026 — Stripe test billing

• Added Stripe-hosted Team checkout in test mode.
• Added webhook-based subscription and invoice reconciliation.
• Added customer billing-portal access when a Stripe customer record is available.
• Published current pricing, renewal, cancellation, invoice, tax, and refund information.

September 2026 — Enterprise readiness

• Added enterprise-readiness workflows and public trust boundaries.
• Added SAML and SCIM foundations for explicitly configured deployments.
• Added technical-test engine and vendor-risk/questionnaire foundations.
• Continued organization-scoped authorization and evidence-integrity hardening.

How to interpret release notes

A release note records a material product or documentation change. It does not mean every feature is enabled for every plan, every provider connection is configured, or every customer requirement is satisfied.

Current plan limits, configuration, production verification, and signed agreements control customer availability. Security or privacy-sensitive implementation details may be omitted from public notes.