Your most sensitive data deserves more than a promise.

The people who operate Kerdour cannot casually read your work. The platform's own operations surface sees metadata only — counts, timings, costs — never the content of a document, message, or memo.

• The internal operations console is restricted to metadata: it shows that a process ran and what it cost, never what it was about.
• Reading your actual content requires a break-glass grant that is scoped to one purpose, time-boxed, reason-logged, and visible to you — there is no silent backdoor.
• Every record is bound to the organisation that owns it; cross-organisation reads are blocked at the data layer, not just the interface.

AI is a tool inside your organisation, not a window out of it. The AI reads your data to serve you — but your content is never used to train models, and every interaction runs behind a hard trust boundary.

• Your content is never used to train third-party models, and never used to improve Kerdour across customers without your explicit opt-in.
• Using your data to answer your questions is not training — your content stays yours and is never absorbed into a model.
• Every document the AI reads is wrapped in a prompt-injection trust boundary, so instructions hidden inside a third party's file cannot hijack the system.
• A per-organisation AI kill-switch can halt all model activity instantly.
• Human notes are treated as facts to weigh, never as commands to obey — the AI cannot be talked into a conclusion.

Each organisation's data lives behind its own boundary. Roles are least-privilege, and elevated access is the exception, recorded every time.

• Per-organisation isolation enforced on every read and write.
• Role-based access with least privilege, separating everyday users from administrators.
• Every privileged action is written to an append-only audit log.

Data is encrypted in transit and at rest, and the handful of secrets that matter are never stored in a form that can leak.

• TLS 1.2+ on every connection.
• Encrypted, regularly-tested backups.
• Access tokens (share links, signing) stored only as one-way hashes — the plaintext is shown once and never persisted.
• Every uploaded file is content-inspected server-side before storage; declared file types are never trusted.

Kerdour runs on dedicated European infrastructure, isolated per deployment, behind a single hardened gateway.

• Hosted in the EU (OVHcloud, France).
• Dedicated database per deployment — no shared multi-customer database engine.
• Containerised services with a tight, auditable surface.

Outbound mail is authenticated and constrained so it cannot be spoofed or mis-sent.

• SPF, DKIM and DMARC published and enforced on the kerdour.com domain.
• Outbound recipients are allow-listed — the system will not email outside controlled domains by default.