Skip to content
FREN
Login
Incident procedure

What to do in case of an incident?

This page distinguishes technical incidents from incidents involving a person in danger, specifies what ELYSÉA can produce, under what procedure and within what timeframe, and what it cannot produce.

INCIDENT INVOLVING A PERSON IN DANGER — ABSOLUTE PRIORITY

If a user of your application is in an imminent crisis (vital emergency, suicidal intent, medication ingestion, ongoing violence):

  1. Call emergency services (your national emergency number). This is the first action — before any report to ELYSÉA.
  2. Preserve all available information about the interaction (timestamp, session identifier if available) — do not modify or delete anything.
  3. Report to ELYSÉA: contact@elysea.app — subject: [URGENT SECURITY] app-name. Response within 2 business hours during office hours (France).

ELYSÉA cannot contact emergency services on your behalf or access your infrastructure in real time. Direct human action remains irreplaceable.

1. Technical incident — abnormal pipeline behaviour

Who to contact

contact@elysea.app — subject: [INCIDENT] app-name · short description

Response time

Acknowledgement within 4 business hours. Initial diagnosis within 24 business hours.

What to preserve

  • Session or request identifier(s) involved
  • Precise incident timestamp (UTC preferred)
  • Observed vs expected behaviour — verbatim, without reformulation
  • Raw logs from your infrastructure (application side, network side)
  • The ELYSÉA SDK version in use

What not to delete

No logs, no headers, no network traces. Deletion may make verification impossible and constitutes a risk in case of regulatory proceedings.

2. What ELYSÉA can produce — and within what timeframe

Signed Guardian log (HMAC-SHA256) for the relevant period

Within 48 business hours

Available in the builder portal (/portail/constructeur/logs) once the Core endpoint is active. Until then, manual request.

Exportable AI Act compliance report (timestamped PDF)

Immediate (portal)

Accessible at /portail/constructeur/logs → "PDF Report".

Confirmation that the call transited through the ELYSÉA pipeline

Within 48 business hours

Requires session or request identifiers from the integrator side.

Behaviour fingerprint of the active version at the time of the incident

UNAVAILABLE

Core work in progress — opened 2026-08-28. Depends on GET /v1/behavior/fingerprint.

Continuous behaviour probe report

UNAVAILABLE

Core work in progress. Depends on GET /v1/behavior/probe.

3. What ELYSÉA cannot produce

Full conversation transcripts

ELYSÉA never stores conversation content. The text of exchanges is neither logged nor transmitted to ELYSÉA — only pipeline metadata (floors, posture, attestation) is retained.

Identity or personal data of end users

ELYSÉA holds no user identifier on the Core side. Identifying individuals falls exclusively under the integrator's infrastructure.

IP addresses of end users

Not retained by ELYSÉA for GDPR compliance reasons. Available only in the integrator's network logs.

Proof that the pipeline was active for a request with no session identifier

Verification requires a request or session identifier. Without this link, verification is impossible even with journal access.

RELATED RESOURCES

Insurer and legal documentation →Behaviour version history →AI Act compliance report →

Contact: contact@elysea.app · Critical incidents: subject [URGENT SECURITY]