For CIOs, CISOs and DPOs
Our technical commitments,
in writing.
What we do with your data, where it goes, who can access it and what you keep if you leave. Copy them into your vendor questionnaire as they are; we answer in writing.
1Hosting
- European Union by default: n8n self-hosted on your server (OVHcloud, Scaleway, Hetzner…) or on an EU cloud.
- Databases in a European region (Supabase Frankfurt or Paris, Xano EU).
- No client data on a server outside the EU without your written agreement.
2AI providers
- API access (Anthropic, OpenAI, Mistral), under terms that exclude training models on your data.
- Provider, region and model are chosen with you and written in the delivered documentation.
- Mistral or an EU-hosted model when sensitivity requires it. Never a consumer tool with your data.
3What is sent to the model
- The minimum the task needs: the fields, not the whole file.
- Pseudonymisation when possible (names, emails, identifiers replaced before sending).
- The exact list of data sent, per flow, is part of the delivery.
4Access and secrets
- Accounts and subscriptions are opened in your company's name, not ours.
- We work with a named, least-privilege access, revocable at any time.
- API keys and passwords in a vault (encrypted environment variables), never in code or in an email.
5Human approval and log
- Every agent action is traced: what, when, on which data, with what result.
- Human approval before any external sending or accounting entry, at least for the first month; after that, you decide.
- An alert threshold per flow: beyond it, the automation stops and notifies.
6Reversibility
- Code, n8n workflows, prompts and documentation belong to you, from payment.
- No imposed subscription; n8n is open source and runs without us.
- Full export and hand-over to the team or vendor of your choice, included.
7GDPR
- We act as a processor under Article 28; a data processing agreement (DPA) is provided on request.
- Record of processing and list of sub-processors (host, AI provider) delivered with the project.
- Test data deleted at the end of the engagement, with written confirmation.
8What we are not
- Not ISO 27001 or HDS certified: if your requirements demand it, we say so on the first call.
- No health data without an HDS-certified host on the client side.
- No automatic sending to an authority, a customer or a bank without human approval configured with you.
- No permanent access to your systems after delivery, unless a signed maintenance contract says so.
Can you fill in our vendor security questionnaire?
Yes. Send it with your contact request; we answer in writing, point by point, before any quote. The answers reuse the commitments on this page and state what depends on your configuration.
Where exactly does n8n run?
Your choice: on a server you administer (we install and document), on an EU server we administer for you, or on n8n Cloud in a European region. For a flow that touches personal data, we recommend the first two.
What happens if we stop working together?
You keep everything: code, workflows, prompts, documentation, accounts. We remove our access, delete test data and confirm it in writing. Another vendor can take over from the documentation.
Who at App Studio accesses our data?
Théo, the founder, who scopes and builds. No outsourced development. If extra help is brought in, you are told beforehand and they follow the same named-access rules.
A question this page doesn't cover?
Write it in the contact form or send your questionnaire. Théo answers in writing within one business day, and these commitments are restated in every quote.
Page updated October 2026. If a commitment changes, this page changes first.