Skip to main content
Audact
See the offer

Acceleration Programme · Enterprise tier

Article 50, configured for your deployment in a scoped pilot of roughly eight weeks.

Article 50 of the EU AI Act has applied since 2 August 2026. It is a transparency duty: a person must be told they are dealing with an AI system. Article 50 requires the disclosure; it does not require you to prove afterwards that it happened. This programme puts that disclosure into your existing voice deployment per country and per language, and leaves a compliance receipt behind for every governed call.

Apply for the Acceleration Programme

Sales-led intake, response within one working day. Production go-live also depends on your telephony, your data, your policy and your own sign-off.

Pilot

≈ 8 weeks

One engagement: audit, configuration, verification, written deployment summary.

Last reviewed: 8 October 2026

What the law says

A duty to disclose, not a ban on deploying.

Read the three lines below before anyone tells you the deadline is coming. It has passed, and what follows from it is narrower and more precise than most vendors suggest.

  • In force since 2 August 2026

    Article 50(1) requires that a natural person interacting with an AI system is informed of that fact, unless it is obvious from the context. Article 50(2) requires synthetic audio, image, video and text to be marked in a machine-readable format, detectable as artificially generated. Regulation (EU) 2024/1689.

  • A full provenance chain is not mandatory

    Commission guidelines C(2026)5054 of 20 July 2026, point (73). Anyone selling you a provenance chain as a legal requirement is describing their product, not the law. We record one because it answers the supervisor's next question, not because Article 50 demands it.

  • The ceiling, with its exception

    Article 99(4) sets the ceiling for a breach of Article 50 at €15 million or 3% of total worldwide annual turnover. For SMEs and start-ups it is the lower of the two. See Article 99(6), confirmed in guidelines C(2026)5054, point (152). The reverse formulation circulates widely and is wrong.

  • The older-systems transition does not cover a new build

    The Digital Omnibus, Regulation (EU) 2026/1744, inserted Article 111(4): systems already placed on the market before 2 August 2026 have until 2 December 2026 to satisfy Article 50(2). A deployment you switch on now is not one of them.

How the engagement runs

Four deliverables.

The work runs through the CEO and the CTO directly. No account manager in between, no partner delivery.

  1. Step 1

    Audit

    We map every voice agent in your stack, per country and per language, and write down where disclosure is delivered today, where it is not, and what is recorded about it.

  2. Step 2

    Configuration

    Policy rules and pre-response validation deployed in shadow mode (In controlled testing) across your agents, with the per-country rules switched on. Shadow mode means nothing is blocked yet. You see what would have been.

  3. Step 3

    Verification

    Shadow mode (In controlled testing) switches to active enforcement. Disclosure delivery is checked end to end on live test calls, and the evidence chain starts recording a compliance receipt per call.

  4. Step 4

    Deployment summary

    A written summary for your compliance file: what was configured, per country, on which date, against which policy version. Plus 90 days of support after the switch.

Scope

What the engagement includes.

Delivered on the Enterprise tier: a paid pilot of €15,000, scoped, roughly eight weeks.

  • Audit of every existing voice AI deployment in scope, per country and per language.
  • Verification that the Article 50 disclosure is actually delivered, in the language of the call.
  • Policy rules configured for your target markets, per country.
  • Pre-response validation rules written for your use case.
  • Shadow-mode pilot (In controlled testing), then the switch to active enforcement.
  • Evidence chain recording a compliance receipt per call, hash-chained with SHA-256.
  • Written deployment summary for your compliance records.
  • Per-country documentation pack of the rules that were applied.
  • Ninety days of support after the switch.
  • Direct line to the CEO and CTO for the duration.

Who this is for

Four situations.

  • Banks and insurers

    Your supervisor's question is not whether you disclosed. It is what the system said, on whose authority, and what you can show. A compliance receipt per call carries a hash of the output the gate released, the decision and the recorded policy version, in the form a compliance department can file.

  • Healthcare organisations

    Article 50 lands on top of the GDPR and, for some deployments, the MDR. The programme configures disclosure, retention and per-country rules once, and records a policy version with each call.

  • Regulated utilities and telecom

    Multiple countries, multiple languages, one policy set. Per-jurisdiction rules are configured together and the eligibility check runs before an outbound call is placed.

  • Anyone who started late

    Article 50 has applied since 2 August 2026 and the programme exists for organisations that need outside hands to close the gap quickly rather than build the capability first.

Questions

Asked before every engagement.

Does this guarantee that we comply with Article 50?
No, and no supplier can. We deliver a working configuration built for the disclosure obligations of Article 50, a written deployment summary and ninety days of support. The final regulatory interpretation rests with your own counsel and the competent national authority.
How long does it take?
The pilot is scoped with you and runs roughly eight weeks; production agreements follow by application.
What happens after the ninety days?
The service continues on the Enterprise tier; production agreements are scoped and quoted per engagement. You keep the configuration, the evidence chain and the written deployment summary regardless.
What is on a compliance receipt?
A hash of what went in, a hash of what went out, and a link to the previous receipt. Those three can be recomputed by anyone, without a key and without an account. 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 receipt also carries an authentication code under a key issued to your tenant.

Ask for the scoping call.

One email. We answer within a working day with a concrete, scoped plan for your deployment.

Apply for the Acceleration Programme

Sales-led intake, response within one working day. Production go-live also depends on your telephony, your data, your policy and your own sign-off.