Post-quantum cold encryption
Documents you keep for the long term will be protected at rest with encryption designed to resist the computers of tomorrow, not only today's.
See the roadmapTrust center
The answers a security questionnaire asks, on one page: where data lives, who can reach it, what recipients see, what we keep and for how long.
Your team's accounts are the first door.
Minimum length, required characters and lockout after repeated failures, set by your administrator.
Authenticator app or text message, with recovery codes. Administrators can require it for everyone.
See every active session and sign out the others; changing your password does it for you.
Owner, administrator and member roles per workspace; invitations by email that expire.
Every account confirms its address before it can act.
Every link and every room is a gate you configure.
Required email and name, one-time code to verify the address, passcode, allow and block lists by email or domain.
Text or PDF, read inline and signed with a typed legal name; signature, time and hashed address kept with the visit.
The recipient's details on every page on screen and burnt into any download you allow.
A date, or one click. A closed link shows nothing.
Allow downloads or not; choose the original file or a PDF.
The people who open your links are protected too.
The gate states that the sender receives reading activity and links to the privacy policy, in the recipient's language.
Visitor IP addresses are hashed before storage.
NDA acceptance and cookie choices are recorded with a time and a hashed address.
Recipients create nothing and are followed nowhere else.
What we do, without describing how our infrastructure is built.
Documents and data are backed up regularly, in France.
Visit records are purged after the period your administrator sets.
Administrative, security and AI actions are recorded with identifiers, never content, and can be exported.
Users, workspaces and waitlist entries can be deleted or anonymised on request, with an audit entry.
Planned maintenance is announced in the application before it starts.
The regulation applies in full, and we act on it.
Certifications
Published here when obtained, never before.
You are the controller of your documents and your recipients' data; Dicte Send is the processor acting on your instructions.
Access, rectification, erasure and portability requests are honoured for your team and your recipients.
Available on request, describing the processing, its location and the absence of subprocessors.
Cookie choices and gate acceptances are recorded as proof, with a version so that a policy change asks again.
Four AI features, what they can get wrong, and where they run.
An assistant your team asks about their workspace, an assistant your recipients ask about the content you shared with them, analyses that summarise a document or extract from it, and search that ranks existing passages.
Assistant answers and analyses are written by an AI system. They can be wrong or incomplete: the document is what counts, and every answer cites the pages it was built from.
Anyone who opens an assistant reads that they are talking to an AI system and not to a person, that it answers only from what was shared with them, and that you can see the conversation.
On Dicte Send's own servers. No document, question or answer reaches a third-party AI service, and there is no subprocessor in the chain.
The questions and answers of a conversation, the result of an analysis, and technical counters. Transcripts follow the retention your administrator sets — 30 days by default — and a recipient's conversation is deleted with their visit. Document content never enters the audit log.
No AI feature decides anything about you or your recipients, and support is answered by a person.
Documents you keep for the long term will be protected at rest with encryption designed to resist the computers of tomorrow, not only today's.
See the roadmapSign inside the flow you already use for NDAs, with a signature that carries legal value across the EU.
See the roadmapWhat we collect, why, and for how long.
Read the privacy policyThe one cookie we set and the choices you have.
Read the cookie policyThe four facts, on one page.
Read the sovereignty statementReport a vulnerability or ask a privacy question.
Contact usWrite to us with the details; we acknowledge every report and keep you informed until it is resolved. Please give us a reasonable time to fix an issue before disclosing it.
Send it. We answer in writing, in French or English.