Skip to content

AI Act compliance (EU Regulation 2024/1689)

Nurion provides AI-powered meeting transcription, summarisation, and CRM tooling to teams across the EU. This page describes how we meet the transparency obligations set out in the EU AI Act (Regulation (EU) 2024/1689), in particular Article 50, and the AI-literacy obligation in Article 4.

Disclosures we provide

Article 50(1) requires that natural persons interacting with an AI system are informed that they are doing so. Wherever a user meets an AI surface in our products, we display a clear, contextual notice before the interaction begins:

  • Every Nurion Meet surface (lobby, name entry, participant picker) carries a persistent Operational Sovereignty badge (top-right) whose popover discloses EU AI Act compliance, EU data residency, and links to the EU Cloud Sovereignty Framework.
  • Live captions and transcription in Nurion Meet are opt-in: a participant must explicitly turn them on via the "Turn on Live Captions" control. The act of opting in is itself the Article 50(1) disclosure moment — no AI processing of speech occurs until the user activates it.
  • Capture sessions in Nurion Meet display a quiet "All participants must have given their consent" notice the moment a second participant joins, and a buffered-audio indicator reminds users throughout the session that audio is held in their own browser memory until they explicitly trigger diarization.

Machine-readable markers

Article 50(2) requires AI-generated content to be marked in a machine-readable format. Nurion outputs carry the following markers using a fixed taxonomy of three values — generated, assisted, and human:

  • Diarized transcript JSON returned by our speech-to-text pipeline carries top-level fields ai_generated, ai_model, and generator.
  • Summary emails sent by Nurion Meet carry an X-Nurion-AI-Generated email header and an HTML <meta name="ai-generated"> tag in the rendered body.
  • Article 50(3) (emotion recognition) and Article 50(4) (deepfakes) are not applicable to the current product surface.

Technical documentation

Per-product technical documentation is maintained internally and made available to procurement teams on request. Each document follows a fixed structure: purpose, providers and model identifiers, inputs, outputs, data retention, human-oversight controls, and known limitations. Article 4 (AI literacy) is satisfied through a written attestation of deployer-staff briefings with an annual refresh cadence.

For copies of the technical documentation, the AI-literacy attestation, or any other compliance artefact, contact us at compliance@nurion.com.

Contact

Compliance enquiries: compliance@nurion.com

See also our Data Privacy policy and Terms.

Last updated: 2026-04-26