Skip to content
POWERED BY ELYSÉA · Label verification

This application declares it embeds ELYSÉA CERVEAU

No application identifier provided. This page is intended to be opened via a link embedded in an application using the “Powered by ELYSÉA” label. The expected URL format is /en/verify?app=<identifier>.

What the label is designed to signal

Four barriers the pipeline is designed to apply.

These are not instructions given to the AI — they are barriers designed to be applied server-side, regardless of how you phrase your messages, without the application builder being able to deactivate them. Measurement campaign not yet run: to be measured.

Non-domination

The AI does not seek to influence your opinions, direct you towards a position, or occupy a disproportionate place in your decisions.

Non-dependency

No affective prompting, no engagement optimisation, no mechanism designed to retain you or compel you to return.

Non-substitution

The AI does not substitute for a qualified human in zones that require one — emergency, distress, care, critical decision. It directs; it does not replace.

Non-manipulation

No subliminal technique, no exploitation of vulnerability, no unconsented oriented bias. Aligned with AI Act Art. 5, applied in the pipeline.

The block is applied server-side, by the pipeline — not a configuration, not a prompt. It applies regardless of the version of the underlying AI model.

Transparency · Current state

The label is self-declared by the application builder.

At present, the label is self-declared by the application builder. ELYSÉA does not yet have an online verification portal enabling independent confirmation that a given application actually integrates the pipeline. For any question about a specific application's integration: contact@elysea.app.


Your door

Questions about this label? Learn more about the label → · Contact us →

Verify an interaction attestation

Each pipeline response can carry a signed attestation. Paste it here: the service tells whether it is authentic. No account, no personal data.

Verify an attestation offline (Ed25519)

Without going through ELYSÉA: the signature is verified in your browser against the published reference public key.

Reading the reference key…

Verified format:

  • signed payload (UTF-8) : interactionId:timestamp:deployedSHA:1|0:buildArtifactHash (without “:buildArtifactHash” for a v2 attestation)
  • signature : Ed25519 (RFC 8032), base64 ; publicKeyFingerprint : SHA-256 of the SPKI DER public key, hex
  • reference key : /.well-known/elysea-attestation-keys.json — JWK set (RFC 7517 §5), OKP Ed25519 keys (RFC 8037), “kid” = SPKI fingerprint; stable address (RFC 8615)
  • a public key attached to the attestation is never trusted: it must be a published key