How Piilot protects your data

You entrust us with your company’s and your customers’ data. Here is how we handle it, without jargon. If a question is not covered below, write to us at [email protected].

Where your data lives

The entire Piilot infrastructure is hosted by OVH in France (Roubaix and Gravelines datacenters). No customer data is stored outside the European Union under standard platform operations.

• The database (your content, agents, conversations, indexed files)
• Binary files you upload (object storage, S3-compatible protocol)
• Agent sessions and in-memory cache
• Encrypted backups

Our technical stack relies entirely on mature, widely battle-tested open-source components, selected for their security track record, auditability and independence from any single vendor. No proprietary component handles your data behind the scenes that isn’t documented here.

Your data is not used to train our models

Neither we nor our LLM provider partners use your data to train AI models. Specifically:

• Piilot trains no model. We orchestrate existing models.
• Managed-mode providers (OpenAI, Anthropic, Mistral): our contracts include a no-training clause on the API we use. Your prompts are not used to train their models.
• BYOK mode (you bring your own keys): your contracts with your providers apply.

You choose your AI models

Piilot is multi-LLM. You decide which models can process your data:

• Managed mode: we provide access to OpenAI, Anthropic and Mistral. Inference runs on those providers’ servers. OpenAI and Anthropic may process requests outside the EU during inference (no storage, no-training contract in place). Mistral stays within the EU.
• BYOK mode: you configure your own provider accounts and apply your own localization rules.
• Full self-hosted mode: on-premise deployment with an open-source language model running locally. No data leaves your infrastructure.

You can switch an agent from one model to another at any time, without re-ingesting data or losing configuration.

Isolation between customer companies

Each company using Piilot is isolated at the database layer itself via the engine’s native forced Row Level Security mechanism. The database physically refuses to return data from another company, even in case of an application bug. This is defense in depth: the application code checks authorization, AND the database checks it independently.

Isolation between your customer files (for firms)

If you manage multiple end customers within your Piilot workspace, isolation between files relies on four stacked mechanisms:

1. Forced Row Level Security at the database layer
2. Cross-cutting access grants on every agent, knowledge base and module
3. Per-file agent scope: an agent attached to a file can only query resources tied to that file
4. Auditable trail: every agent access is logged and visible

Limitation to be aware of: a firm administrator can, by design, view all files if granted the corresponding rights — this is a deliberate choice that depends on properly assigning roles at onboarding.

Encryption

• In transit: TLS 1.2 minimum, TLS 1.3 preferred, on every flow (UI, API, inter-service communication)
• At rest — secrets: API tokens, SMTP passwords, external connector keys are encrypted using an industry-standard authenticated symmetric encryption scheme before being stored in the database
• At rest — user passwords: hashed with a password-grade algorithm (brute-force resistant, automatic salting)
• Backups: encrypted and stored on OVH France infrastructure

If you leave Piilot or delete an agent

• Export at any time: you can export your knowledge bases and conversations as CSV / JSON from the interface
• Deleting an agent / document / file: immediate logical deletion, physical deletion within 30 days (including backup purge)
• Closing your Piilot account: full deletion within 30 days after confirmation. No data retained beyond that, except where legally required (billing records: 10 years).

Authentication and access

• Password authentication or email magic link
• Short sessions: 15-minute access token, 7-day sliding refresh, 30-day maximum lifetime
• Auto sign-out after 10 minutes of inactivity
• OAuth Google and Microsoft Entra (rolling out)
• Rate limiting and anti-brute-force protection on all sensitive endpoints

Audit and logging

Every significant action (resource creation / modification / deletion, agent execution, external connector access) is logged. Workspace administrators have access to those logs from the interface.

Self-hosting

For organizations that require complete isolation, Piilot can be installed on your own infrastructure. The codebase is strictly identical to the SaaS version — no diverging fork. Documentation: SELFHOST.md in our repo.

Our providers’ certifications

Piilot relies on providers that hold their own recognized certifications:

• OVH (hosting): ISO 27001, ISO 27017, ISO 27018, HDS (French Health Data Hosting), SecNumCloud on dedicated offerings
• Mistral AI (Managed EU LLM): SecNumCloud process underway, EU infrastructure
• OpenAI & Anthropic (Managed LLM): SOC 2 Type II, enterprise no-training contract enabled on the API we use

These certifications belong to our providers and do not constitute a Piilot certification. Our own certification roadmap is described below.

What we do NOT yet claim to have

We’d rather be honest than oversell:

• SOC 2 — in progress. Not yet certified. Initiative scheduled for H2 2026 based on market traction.
• SAML / Enterprise SSO — in progress. OAuth Google and Microsoft Entra come first, SAML follows.
• EU AI Act formal compliance pack — in progress. Registries, transparency on automated decisions, etc.
• ISO 27001 — not on the short-term roadmap.

If any of these is a blocker for your organization, get in touch: we’ll tell you exactly where we stand and what mitigations are available.

Contact