Data residency
The form data your team collects — the application that serves it, the database that holds it, and every backup of both — stays in Germany.
| What | Where |
|---|---|
| Application and database | Germany (EU) |
| Backups | Germany (EU) |
| Transactional email | France (EU) |
| Website analytics | Our own servers |
The current list of providers is on the sub-processors page.
GDPR obligations the product serves
| Obligation | Article | How Formabi serves it |
|---|---|---|
| Right of access | Art. 15 | Search every form for a person and export everything held about them — each field, across every submission — as one bundle |
| Right to erasure | Art. 17 | Purge an individual field, a whole submission, a form, or an entire workspace. Every request is recorded |
| Storage limitation | Art. 5(1)(e) | Per-workspace retention: set how many days submissions are kept, and a background job purges anything older |
| Consent | Art. 7 | Consent is stored with a snapshot of the exact text shown. Withdrawal is recorded against the same record |
| Records of processing | Art. 30 | Sign-ins, administrative changes, permission changes and data-subject actions are written to an audit log, kept for 365 days |
| Security of processing | Art. 32 | Encryption in transit and at rest, 2FA, SSO and tenant isolation — set out below |
Security controls
- Encrypted in transit and at rest — HTTPS only (TLS 1.2/1.3 with HSTS); databases, tenant volumes and backups on encrypted disks, backups encrypted before they leave the server
- Two-factor authentication and SSO — TOTP with recovery codes, plus single sign-on through any OpenID Connect provider (Google Workspace, Microsoft Entra ID, Okta), with optional enforcement, email-domain allow-list and role sync
- Passwords, tokens and sessions — passwords hashed with bcrypt; session and share-link tokens stored only as hashes; logins rate-limited; sign-ins listable and revocable
- Tenant isolation — each customer runs in its own container against its own database, reachable by no other tenant
- Backups and tested restores — encrypted nightly backups kept seven daily, four weekly and six monthly; restores are rehearsed, last drilled 22 September 2026
- Audit log and declarative infrastructure — an append-only audit log kept 365 days; infrastructure declared in code (NixOS), version-controlled and reviewed, with dependency vulnerability scans on every release build