ELYSÉA Application UsersWhat the pipeline prevents the application from doing to you.
Written into every call — not into the terms.
Every application displaying “Powered by ELYSÉA” has accepted 8 prohibitions inscribed in the pipeline — active at every exchange, non-deactivatable by the builder. Applied by the pipeline at every exchange.
Differentiation
A privacy policy says.
An architecture does.
Most AI protections rest on written promises. ELYSÉA CERVEAU rests on prohibitions applied by the pipeline at every exchange — traced, with their limits published; their effectiveness will be measured during the campaign and published afterwards, favourable or not.
Privacy policy · Fragile
Unilaterally modifiable
The service can change its terms at any time, often without clear notification.
Not verifiable by a third party
Impossible to prove that the stated rules are actually being applied.
Bypassable by configuration
An operator or subcontractor can change the rules without your knowledge.
Depends on human will
If the company changes leadership or is acquired, your protections change with it.
ELYSÉA CERVEAU · Pipeline · Structural
Designed for every call
The 8 prohibitions are designed to be applied by the pipeline at every call that goes through it; no builder configuration parameter can disable them.
Traced, measurement to come
Every refusal is traced and timestamped pipeline-side. Their effectiveness will be measured on corpora during the campaign and published afterwards, favourable or not; known limits are published.
Non-configurable downwards
Builder configuration can tighten protections, not weaken them.
Independent of the AI model
The 8 prohibitions are applied by the pipeline, whichever allowlisted model is used behind it.
What the label is designed to signal
Source: ELYSEA.SDK.INTEGRITY_PROTECTION.v1 §4 — design objectives of the pipeline, not configurable downwards by the builder, with no measured result to date. No protection is infallible: known limits and the measurement status are published on the Limits page.
01Refusal to diagnose
The pipeline is designed to refuse any clinical conclusion about you, regardless of how you phrase your message.
02Against manipulation
The pipeline is designed to screen out oriented bias mechanisms, hidden persuasion and unconsented influence. Art. 5 AI Act.
03Against dependency
Designed with no affective prompting, no engagement optimisation, no algorithmic retention.
04AI identification
The pipeline is designed to have the AI identify itself as such at every relevant interaction, not as a human. Art. 50 AI Act.
05Redirection in critical zones
Emergency, distress, medical or legal need: the AI is designed to direct you to a qualified human, not to substitute for one.
06Your memory belongs to you
Viewing, export and immediate deletion available. Prohibition P2 is designed to block a builder's access to your memory without your explicit recorded consent.
Your memory belongs to you
If you use an ELYSÉA application, your memory — preferences, context, interaction history — is stored under your explicit consent. It does not belong to the application builder. It is not monetised. It is not shared without your agreement.
You can consult it, export it as JSON, or delete it immediately. These rights are not optional — they are in the pipeline. Prohibition P2: applied by the pipeline, not configurable by the builder.
Your data, your controls →
How to verify the label is active
The “Powered by ELYSÉA” label embedded by the SDK reads the application's state at every display. If access is revoked, the key is refused immediately, the label shows “Not verified” and the withdrawal is entered in the public register; the builder removes it from its interface within 48 hours. Anyone can verify it.
What the label means →
Frequently asked questions
- Is this a consumer app like any other?
- No. It is an ethical cognitive infrastructure. You do not interact with ELYSÉA directly — ELYSÉA is the active pipeline inside the applications you use.
- Can the app builder access my memory?
- Not without your consent. Prohibition P2 blocks a builder's access to your memory without explicit consent recorded in the registry.
- Can I delete my data?
- Yes, at any time. Viewing, JSON export and immediate deletion are available in your space. For data from this site, write to contact@elysea.app.
- What happens if the app changes its rules?
- Builder configuration cannot weaken the 8 ELYSÉA prohibitions. If an application stops using the SDK, the "Powered by ELYSÉA" label disappears from its interface.
A question about your rights or a specific application?
Your dossier
Dossier 10 — End users
Faithful sentence-by-sentence translation of the French master text, aligned line by line; the French text remains the reference.
- Message: you are talking to the application, not to ELYSÉA; it cannot analyse your emotions, manipulate you, or switch these rules off; if you are in danger, you receive the public numbers.
- What it does not do: provide care, contact someone, verify age. →
10_END_USERS.md
Measurements (campaign results file)
- Crisis recall — FrenchTo be measured — campaign in progress
- Response qualityTo be measured — campaign in progress