PARIS
eu-west-3
Submissions are written to a Postgres cluster in Paris. There is no US region to fail over to, because we did not build one.
The form thatwon't get you sued.
Flora is the address. Point your <form> at us and every submission lands in a dashboard hosted in Europe. You keep the front end. We keep the paperwork.
<form method="POST" action="https://post.useflora.eu/YOUR_FORM_KEY"> Create your first form → No risk, high reward (˶˃ ᵕ ˂˶) .ᐟ.ᐟ
Three steps, and two of them aren't yours.
You do the first one once. After that the form is somebody else's problem, which is the entire point of paying for a form backend.
contact.html
-<form method="POST" action="/contact.php">
+<form method="POST" action="https://post.useflora.eu/pk_9f3c2a7d41b6e0c5">
That is the whole integration. The fields, the markup and the styling stay exactly as you wrote them.
No script tagNo packageNo build step
Stop blasting raw form data straight to email.
That copy leaves the EU, sits in an inbox nobody audits, and gets backed up somewhere you cannot name. Someone typed their phone number in because they wanted to hear back from you. They did not mean to put it in four places.
Flora sends a knock on the door instead. You come and read it where it lives.
- No field names and no values in any email
- Nothing to forward by accident
- One clean place to view it, one click to delete it
- No copy left in a third-party inbox
Pick one to bring it forward
The technical decisions we’re actually proud of!
None of these are badges we bought. They are decisions about where the servers are and what the software is allowed to send, and you can hold us to every one.
AES-256
at rest
Payloads are encrypted on disk. Backups carry the same encryption and live in the same region as the data they copy.
TLS 1.3
in transit
The endpoint refuses plaintext. A submission is encrypted from the visitor’s browser until the moment it is stored.
ART. 28
processor
A data processing agreement that names every subprocessor and the country it sits in. It binds us on every plan, free ones included. Business gets it signed.
- Notification emails carry no submission data
- Deleting a submission deletes it
- No third-party analytics on the endpoint
Free for side projects, fair when you scale ^^
A paid plan buys room, more forms and more submissions a month. Everything that makes Flora worth using, EU storage and submissions kept until you delete them, is on the free one too.
Business
Recommended
€49/month
For studios, agencies, and serious client work.
- Everything in Solo
- Unlimited forms
- 5,000 submissions a month
- A signed processing agreement, and a written record of where data sits
- Priority replies from a human
We build liketrust is fragile.Because it is.
Flora is made by Serendipiware, an independent software company that builds useful tools. The kind you can understand, rely on, and feel comfortable putting in front of your customers.
More about Serendipiware
Flora Be boring :p
The details, without the fine print.
Everything you might wonder about how we handle your data, where it lives, and how Flora actually works. No vague non-answers.
In a Postgres database in Paris, on infrastructure rented in the eu-west-3 region. It is written encrypted, backed up inside that same region, and there is no second region for it to travel to.
You are the controller. Flora is the processor, acting on your instructions and nobody else’s. That is the arrangement Article 28 describes, and it is the one our agreement reflects.
Supabase holds the database, in Paris. Railway runs the endpoint your forms post to, in Amsterdam. Cloudflare serves this site and the dashboard, and runs our DNS. Brevo sends the notification that says a submission arrived, from France. Stripe will handle payments once billing is switched on. All five are listed with their locations on the privacy page, and you get notice before that list changes.
You already have one. It is published at /dpa, it names each subprocessor above with its country, and it binds us from the moment you create an account, on the free plan too. On Business we sign it, countersign your copy and send it back. On Custom your legal team can rewrite the terms in it, and writing to [email protected] is how that starts.
The sentence “You have 1 new submission”, the name of the form, and a link. No field names, no values, no preview. There is no setting that adds them, because the absence is the product.
It leaves the database immediately and drops out of the backups as they roll forward. We keep no separate copy to restore from, and none was ever emailed, so there is nothing sitting in an inbox to surface two years later.
You get notice and a full export before anything is switched off, and your forms keep accepting submissions until the date in that notice. A form backend that could vanish overnight would be a worse liability than the one you have now.
Let your form be boring.
Let yourform beboring.
You shouldn't need a compliance team or a messy stack just to receive an email. We handle the form backend quietly and securely, so you can just focus on building your site.
Put Flora behind yours →