Skip to main content
Audact
See the offer

The obligation follows your brand into text.

Voice: In controlled testing · chat: Planned

For voice AI: Article 50(1) interaction disclosure, on the same evidence chain as your voice agents. Article 50(2) synthetic-content marking and coverage of text channels are planned.

For voice, a compliance receipt per governed interaction; chat and email are planned.

  • Voice hand-off: In controlled testing. Chat and email are planned and not part of the current offer; there is no separate price for them.
  • Primary application hosting: Frankfurt

The two duties

Article 50(1) and Article 50(2) are not the same obligation.

They are often treated as one. They are not: one is about telling a person, the other is about marking a file, and a channel can satisfy the first while failing the second.

  • Article 50(1): interaction disclosure

    Voice: In controlled testing

    A person interacting with an AI system must be told, unless it is obvious from the circumstances. Audact enforces it per session, per channel and per locale, and records that it happened.

  • Article 50(2): synthetic-content marking

    Planned

    Generated audio, image, video and text must be marked in a machine-readable format, detectable as artificially generated. Attaching cryptographic provenance (C2PA) to generated output would be part of a later release; no date has been established and it is not in the product today.

The article numbers are Regulation (EU) 2024/1689, Art. 50(1) and Art. 50(2). Article 50 has applied since 2 August 2026. It is a transparency duty, not a ban.

Coverage

Wherever AI speaks for your brand.

Planned: the same disclosure on the text channels your clients run.

  • Customer-service chatbots on the website and in-product.
  • AI sales agents and support copilots.
  • CRM-native AI assistants.
  • WhatsApp Business AI.
  • Email AI agents and AI-assisted replies.

Integration

Two webhooks, no SDK to adopt.

  • chat-message-sent

    Planned

    Fires on each outbound AI message. Audact attaches an Article 50(1) disclosure ID and a reference to the Article 50(2) C2PA manifest.

  • chat-message-received

    Planned

    Fires on each inbound message from the person. Audact records the disclosure state, the locale and the policy version for the session.

Planned: REST and webhooks.

Commercial

How it is priced.

Voice hand-off: In controlled testing. Chat and email are planned and not part of the current offer; there is no separate price for them. Production access sits inside an applicable paid agreement. Endpoints are not priced separately. Talk to us.

The platform itself is €1,497 implementation, then €499 per month with 5,000 minutes included, €0.11 per minute above that, and 15% off on annual prepayment. That is the founding rate, for Audact’s first three external agency customers; from Audact’s fourth it is €2,995 and €749.

Primary application hosting: Frankfurt; a backup region in Ireland is being set up.

Next step

Put every channel on one evidence chain.

Chat compliance is planned: the same governance and disclosure layer, extended to web chat, WhatsApp and email. Talk to us to be first in line.

  • The export returns the receipts. That is not the same as an outsider being able to check the export: the export envelope refers to a key of ours, and that key is not published.
  • REST and webhooks, no SDK lock-in.
  • Disclosure wording per language and per jurisdiction, out of the box.

Related

  • Article 50

    What the law requires, since when, with the article numbers.

  • The platform

    One governance layer under voice and outbound; chat is planned.

  • Proof

    The receipt every channel writes to, field by field.