Vos contenus prives restent proteges.
- Message bodies and secure notes
- Titles and filenames
- Uploaded documents and file contents
- Private instructions prepared for release
If a dashboard casually shows plaintext filenames or note bodies, users will naturally assume the service operator can see them too. That is why DMS defaults to placeholders like “Chiffre file” and “Chiffre message” until the browser locally unlocks the vault.
The server stores encrypted vault materials while the user's browser handles the session-based reveal of filenames, messages, and files after a local unlock.
Admin tools stop at status, counts, dates, reminder state, payment state, and release workflow visibility. Non plaintext vault contents appear there.
Utilisateurs still need to choose trustworthy verifiers, keep recovery instructions safe, and test the full workflow before relying on it.
“We process the operational data needed to run reminders, verification, and release. We do not read the encrypted contents of your private vault in ordinary use.”
DMS uses strong authenticated encryption for vault contents together with a clear separation between encrypted payloads and service metadata.
DMS explains what is encrypted, what is not, what the service depends on, and what risks remain, without pretending any system can guarantee every outcome.