Skip to main content
Audact
See the offer

Part of the Audact layer

The four numbers that matter when a regulator calls.

SLOs: In controlled testing · not a separate product

Disclosure success, receipt coverage, block and rewrite rate, stale consent. Scoped to what an auditor actually verifies, surfaced as dashboards, alerts and webhook events you can route into the incident stack you already run.

  • Included in Agency Voice & Enterprise
  • Patent-pending governance stack (UK IPO)
Talk to salesSee a receipt

The SLOs

Four service levels, and the targets they are measured against.

These are the values this capability will be measured against. They are targets, not a measurement of your deployment, and they are stated here so you can hold us to them.

  • Disclosure success

    ≥ 99.5%

    In controlled testing

    The Article 50(1) disclosure step was recorded at the start of the session. Measured per calendar month.

  • Receipt coverage

    ≥ 99.9%

    In controlled testing

    A receipt is written for every governed interaction within sixty seconds of completion. It does not establish that every relevant path was governed. Measured per calendar month.

  • Block and rewrite rate

    monitored

    In controlled testing

    What share of candidate utterances the Governance Gate stopped or rewrote. A drift indicator rather than a target. Measured per calendar month.

  • Stale consent rate

    ≤ 0.1%

    In controlled testing

    Outbound dispatches against consent that has lapsed, narrowed in scope, or been revoked. Measured per calendar month.

Where it plugs in

Into the incident stack you already run.

  • Webhooks

    Planned

    Authenticated events for every SLO threshold crossing. HMAC-SHA256 under your tenant key, replay-safe.

  • Dashboards per jurisdiction

    Planned

    Germany first, then the Netherlands, then Belgium and Austria, sliced per policy bundle so a country-level answer is one filter away.

  • Incident routing

    Planned

    Outbound payloads designed to map onto the schemas that common ITSM and SIEM platforms already use.

What is marked Working today is delivered through the platform today; the rows marked Planned are not yet. Its own service terms and SLA are the next step. It stays part of the platform — there is no separate product to buy.

Why these four

Because these are the four an auditor can check.

A compliance dashboard that reports twenty metrics reports none of them. These four correspond one-to-one to a question someone will actually ask: was the disclosure made, is there a receipt for it, is the gate doing anything, and did an outbound call go out against consent that no longer held.

Next step

Compliance metrics that ship.

The Observability Layer runs inside every Audact deployment and gets its own service terms later; no date is set. Status: In controlled testing. It stays part of the platform, not a product you buy on its own. Start with white-glove onboarding, or ask engineering for the event schema.

Apply for a founding seatTalk to engineering

Related