Trust

What the server enforces, page by page

Three pages describe what the platform enforces, server-side, for data, security and access – what is in place, not what is planned.

Data

Consent, sensitive data and traceability

Compliance is not dealt with after the fact: it decides where a value is written, who may read it back, what is logged about it and the day it disappears. And what leaves a space through a workflow is declared, classified, logged: no undeclared target, health data sent only encrypted, to an attested connection, field names in the log – never values.

Read the page

Security

Security and compliance

Missivia is designed for regulated environments. This page lists verifiable facts about how the platform handles data, and describes what is in place, not what is planned.

Read the page

Authorisation

Authorisation and access

An organisation, its spaces, its roles, its named permissions and its API keys combine into a single authorisation, computed on every call, server-side.

Read the page

Two deployment modes

The same product is deployed in two ways. The standard mode is the default; it is not health data hosting.

Standard, by default

Hosted in France, in the Paris region, with a French hosting provider named in the contract.
Encryption, isolation per space, audit log, automatic database backups.
For any use without health data.

Health, as an option, under contract

The same product, as a dedicated instance, deployed with a hosting provider certified as an Hébergeur de Données de Santé (HDS, the French certification for health data hosting).
Scope, deployment environment and each party’s responsibilities defined in the contract.
The certification applies to the hosting provider: the platform itself is not HDS-certified, and cannot be.

The product’s guarantees apply in both modes: consent per purpose, sensitive data encrypted outside the record, statistical masking below the display threshold, tamper-evident audit log. Details on the Security page →