ISO/IEC 27001:2022
Certified. Renewal in progress (2026 surveillance/recertification audit). Full certificate details available under NDA.
GDPR-compliant. ISO 27001:2022 certified. EU-hosted. 9 named sub-processors under signed DPAs and SCCs. Customer data processed exclusively in the EU under S3NS sovereign cloud.
Direct answer: Flowie is GDPR-compliant, EU-hosted, and ISO 27001:2022 certified. We have 9 named sub-processors, all covered by Data Processing Agreements and Standard Contractual Clauses. Our DPA template is available in English and French (May 2025 revision). Customer data is processed exclusively within the EU under S3NS sovereign cloud — primary in Paris, disaster-recovery in Belgium. AI providers process descriptive text only; they never see financial amounts or account numbers, and they are contractually bound to zero retraining. This page routes you to the specific commitments you need: security controls, sub-processor details, and breach notification procedures.
Trusted by enterprise finance teams










Independent third-party validation
Certified. Renewal in progress (2026 surveillance/recertification audit). Full certificate details available under NDA.
Score 878 / 1000 · Industry benchmark 654 (assessed 2024-10-04)
Certified December 2025 · French e-invoicing mandate (XP Z12-014)
Compliant · Pan-European e-invoicing interoperability
Not currently held — see FAQ
Additional security evidence — penetration test reports, Detectify continuous scanning results, and the full ISMS Statement of Applicability — is available to qualified prospects under NDA.
GDPR
Flowie handles B2B financial and procurement data. That means invoices, payment terms, supplier identities, and approval workflows — data that carries legal and fiduciary weight. We treat it accordingly.
Under GDPR, your organization holds rights over every personal data element Flowie processes on your behalf. Those rights are not theoretical.
Articles 28 (DPA), 33 (72h breach), 34 (customer notification), 15-22 (data subject rights)
Article 28 GDPR · May 2025 revision · countersigned before go-live
[email protected] · responds within 30 days · residency + subject-rights questions
All under signed DPAs · non-EU under SCCs · full table at /trust/subprocessors
GDPR Art. 33 supervisory authority notification · Art. 34 customer notification without undue delay
To exercise any of these rights, contact [email protected]. We respond within 30 days.
Article 28 GDPR
Every customer relationship at Flowie is governed by a signed Data Processing Agreement. The DPA defines the scope of processing, the legal basis, sub-processor obligations, data subject rights procedures, and your ability to audit.
The current DPA template was revised in May 2025 and is available in English and French. It aligns with GDPR Article 28 requirements and includes a complete sub-processor annex by reference to the list published at /trust/subprocessors.
If you need a countersigned DPA before procurement approval, we can turn that around quickly — typical turnaround depends on the specific redlines submitted. Request it via the form at the bottom of this page or email [email protected] directly.
⚠️ TO VALIDATE: confirm specific DPA countersignature SLA with Legal before publish (e.g. "within X business days") if a public commitment is desired.
No customer goes live without a signed DPA in place.
9 named vendors
S3NS · sovereign cloud
| Attribute | Detail |
|---|---|
| Primary region | Paris, France |
| Disaster-recovery region | Belgium · cross-border DR within the EU |
| Cloud provider | S3NS (Google Cloud + Thales joint venture) |
| Sovereign posture | ANSSI SecNumCloud-aligned · French law jurisdiction |
| Data residency | 100% EU at infrastructure layer · zero US/UK replication |
All Flowie customer data is processed and stored within the European Union. There are no exceptions.
Our infrastructure partner is S3NS — the sovereign cloud platform built jointly by Google Cloud and Thales. S3NS operates under French law, meets ANSSI SecNumCloud requirements, and provides physical and logical separation from US-jurisdiction cloud infrastructure.
Primary region: Paris, France. Disaster-recovery region: Belgium. Data does not cross EU borders at the infrastructure layer.
Three AI providers
This section is more specific than most vendors provide, because the questions we receive are specific.
Flowie integrates three AI providers: OpenAI, Mistral AI, and Anthropic. Each is used for natural language processing tasks — extracting field values from document text, matching line items, categorizing descriptions.
| Provider | Hosting region | Residency posture |
|---|---|---|
| Mistral AI | France · EU | Full inference cycle remains in France |
| OpenAI | United States | Under signed SCCs · descriptive text only · zero retraining |
| Anthropic | United States | Under signed SCCs · descriptive text only · zero retraining |
What AI providers receive
Descriptive text only. Supplier names, line item descriptions, product references, document titles. That is the complete scope.
What AI providers never receive
Financial amounts, IBAN or account numbers, payment terms values, or any data field that could identify a transaction's financial exposure.
This is enforced at the data pipeline layer before any call leaves our infrastructure. It is not a policy preference — it is a technical boundary.
Zero retraining — contractual commitment
All three AI providers are bound by contract to not use Flowie customer data to train or fine-tune their models. This applies to API-submitted data and is not dependent on product settings or opt-outs. The commitment is in writing, in the DPA annexes.
If your security team needs the specific DPA language covering AI processing constraints, request it through the DPA form below.
GDPR Article 33 / 34
72-hour notification commitment
GDPR Art. 33 · 72h compliantIn the event of a personal data breach meeting the threshold under GDPR Article 33, Flowie notifies the relevant supervisory authority within 72 hours of becoming aware of the breach. This is not a target — it is our contractual and regulatory obligation.
Customer notification
Where a breach is likely to result in a high risk to the rights and freedoms of your users, we notify you without undue delay so you can fulfill your own GDPR Article 34 obligations. The notification includes the nature of the breach, the categories and approximate number of data subjects affected, the likely consequences, and the measures taken or proposed.
How notification reaches you
Through the technical contact and DPO contact designated in your signed DPA. If those contacts change, update them with your account manager so notification routing stays current.
The full GDPR Incident Response Plan is available for review under NDA as part of advanced due diligence.
Buyers ask us this
Request a countersigned DPA in English or French.