Who processes what

Who touches your data today, and your child's data tomorrow? Here's the list, dated. We update it whenever something changes.

Today: the waitlist

This site sells nothing. It asks for one thing, your email, to tell you when Poumi launches. Three processors make that work.

Processor Country What it sees What it keeps
Brevo France Your email address, the moment you sign up. Your email address, until you unsubscribe (or three years after our last contact).
Cloudflare United States (company), European infrastructure for this form. Your form submission, long enough to forward it to Brevo. Nothing. The worker passes your email along, it doesn't store it.
Plausible European Union Your visit: page, referrer, device type. No cookies, no identifiers. Aggregated statistics. Nothing that points back to you.

One thing worth being precise about: Cloudflare is a US company. The worker that relays this form is set up to keep data in Europe, but the company itself stays under US law. We'd rather tell you than hide it behind "hosted in Europe."

Tomorrow: the product

Nothing is for sale yet. This is the architecture we picked for Poumi, the one that will run once the plush can talk. It isn't live.

Processor Country Planned role
Scaleway France (Paris) Hosting and compute: the servers that will run Poumi.
Supabase European Union Database: parent accounts, settings, Poumi's memory.
Mistral France The language model that will understand questions and prepare answers.

This is the architecture we chose, not the one already running. We'll republish this page the day it goes live, under the same rule: name, country, role.

Version dated 15 August 2026. See also our exit commitment and our approach.