One receipt per governed interaction.

The distinction

A promise and a receipt are not the same object.

There are two ways to answer the compliance question. One is process: a pledge to scrub a do-not-call list, a quality review after the call, an indemnity clause in the terms. All of it describes what should have happened. None of it shows, on one specific call, that it did.

Audact answers it with the record. The AI disclosure is spoken at the position the country policy requires, the approved wording is checked before the model speaks rather than sampled afterwards, and both leave a trace in the same artefact. When something is disputed, a promise is an argument and a receipt is a document. Status: In controlled testing. Germany active · Netherlands in progress · Belgium, Austria queued.

Where we sit

Agency-native, with the artefact on top.

We match the agency-native shape on the things that make a reseller's life work: white-label the caller actually hears, isolated sub-accounts, transparent per-minute pricing, and billing that routes to your Stripe rather than ours. Stripe re-billing: Planned.

What is added on top is the part that is hard to bolt on afterwards, because it has to sit in the path of the call rather than beside it. Both leave the same receipt, which is what turns a claim into something an end-client's data protection officer can open and check; the monthly evidence package that goes with it is not in the offer; it is Under validation: we do not ship an evidence artefact we have not tested ourselves. What sits in the path of the call today: the disclosure is enforced at the moment it is due, and the approved wording, the prices and the commitments the agent may make are checked before the model speaks.

Backed by a patent-pending governance stack filed at the UK IPO.

The fields

What a third party can recompute, and why that is the whole point.

1. The input hash: what went into the model on this turn.
2. The output hash: the output the gate released (on a block, the fallback reply).
3. The link to the receipt before it: so a later alteration or reordering is detectable.
4. Merkle inclusion, so a single receipt can be tied to a published commitment. The fourth, inclusion in the Merkle root, is checked against the published root with the inclusion proof from the call's Article 50 report; the roots are published at api.audact.ai/v1/metachain. The three above it you can run right now.