AI Act compliance (EU Regulation 2024/1689)

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:

• Public booking pages (meet.nurion.com/book/...) carry a one-line notice that meetings may be recorded and AI-transcribed.
• The Nurion Meet pre-join modal acknowledges that the meeting is AI-transcribed before the "Join" action.
• During an active call, the Nurion Meet control bar shows a persistent "AI transcription active" indicator that cannot be dismissed.

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.