Security at Fipeo
Last reviewed: 15 November 2026.
Schools and agents trust Fipeo with their prices, bookings and the details of their students. This page says what we do to protect them, in plain words.
Where your data lives
Fipeo runs on a dedicated server of OVHcloud in Roubaix, France. The database and its daily copies stay in the European Union.
Fipeo is run from Barcelona, Spain, and follows the EU General Data Protection Regulation (GDPR).
Each school and agency only sees its own data
Every request is checked against the account that makes it, down to the database query: a school cannot open the bookings, students or documents of another school, and the same goes for agencies.
Automated tests check this separation, and the whole test suite runs before every change goes live.
Encryption
All traffic uses HTTPS, with HSTS, from your browser to Cloudflare and from Cloudflare to our server (with a verified certificate).
The most sensitive fields are encrypted inside the database with XChaCha20-Poly1305 (libsodium): bank details, the secrets of two-step verification and, when a school stores them, student documents such as passports and health notes. The keys are kept apart from the database and are not part of the backups.
Passwords are stored only as Argon2id hashes. We never see them.
Signing in
Passwords need at least 12 characters, and we reject passwords that appear in known data breaches (checked with Have I Been Pwned without sending the password or its full hash).
Repeated failed attempts are limited per account and per address.
Two-step verification with an authenticator app is available to every account. It is mandatory for Fipeo staff, and a school or agency can make it mandatory for its whole team.
In My account you can see your open sessions (device, approximate address and last use) and close them. Resetting your password closes all of them.
What we record
Sensitive actions are recorded: changes to bank details and who viewed them, changes to two-step verification, data exports and account closures.
When our support staff need to see an account as its user does, they can only do it with their own staff session, for at most one hour, every time is recorded, and in that mode bank details and sensitive student data are not decrypted.
Backups
The database is copied every day. Each copy is checked (size and checksum), encrypted before it leaves our server and kept in two places: 7 days on separate OVHcloud backup storage in France and 30 days in a Hetzner storage box in Germany.
Your data is yours
The owner of a school or agency can export all of its data at any time as a ZIP file (JSON and CSV), and any user can download their own personal data from My account.
If you close your account, its data is deleted 30 days later, except what the law requires us to keep, such as invoices. Until then you can change your mind.
Payments
Card payments are handled by Stripe and PayPal. Card numbers never reach Fipeo's servers.
Certifications
Fipeo does not hold ISO 27001 or SOC 2 certification. We use the controls of ISO/IEC 27001 Annex A as our own checklist and review them regularly; the last review, with a basic penetration test of our test environment, was in November 2026.
If something goes wrong
If a security incident affects your data, we will tell you without undue delay, explain what happened and what we are doing, and notify the data protection authority when the law requires it.
To report a vulnerability or ask a security question, write to [email protected]. Please give us time to fix the problem before making it public.
API documentation for developers →
Providers that process data for us
We only share with each provider what it needs for its job.
| Provider | What for | Company based in |
|---|---|---|
| OVHcloud | Hosting and backups (servers in France) | France |
| Cloudflare | DNS, delivery of the web pages and protection against attacks | United States |
| Brevo | Sending system emails (sign-in links, notifications) | France |
| Migadu | Our support mailbox | Switzerland |
| Anthropic | AI features, only when a school or agency uses them | United States |
| Stripe | Card payments and subscriptions | Ireland |
| PayPal | PayPal payments | Luxembourg |
| Hetzner | Encrypted second copy of the backups (servers in Germany) | Germany |