Where your content lives, and who handles it
Galerne stores your content in Paris and works only with European companies. This page lists each provider, what it does and which data it sees.
Four providers, all European
None of them has a US parent company. The same list, with addresses, is on the subprocessors page.
| provider | company | what it does | data it handles |
|---|---|---|---|
| Scaleway | Scaleway SAS, France | Runs the API, the studio and the databases, stores media files, and hosts the embedding model of semantic search. Region Paris (fr-par). | All content, accounts, media, logs |
| Bunny | BunnyWay d.o.o., Slovenia | CDN in front of media files and cached published reads. | Published content and media in cache, visitor IP addresses in request logs |
| Brevo | Brevo SAS, France | Sends sign-in codes, invitations and usage alerts. | Email addresses and names |
| Mollie | Mollie B.V., Netherlands | Takes payments and runs subscriptions, in euros. | Billing details; card data stays with Mollie |
One database per project
Each project gets its own Postgres database, next to a control database that holds accounts, members, tokens and billing. Content, history, branches, comments and media records of one project never share tables with another.
This keeps the boundaries simple. We can restore, export or delete one project without touching the others.
We run no language model
Galerne never sends your content to a language model. Agents bring their own: Claude, Mistral, GPT, or a model you run yourself. When your agent calls a Galerne tool through MCP, the result goes to your MCP client, and the client sends it to the model provider you chose. That transfer is your decision, under your contract with that provider. Our DPA says so in the same words.
The one model we use is an open embedding model, bge-multilingual-gemma2, for semantic search on the Business plan. Scaleway runs it in Paris. It turns published text into vectors, and the vectors are stored in your project database.
We do not train any model on your content.
Why the company behind your CMS matters
The US CLOUD Act of 2018 lets US authorities order a US company to hand over data it holds, wherever that data is stored. It applies to servers in Frankfurt or Paris when a US company runs them.
A CMS holds drafts, unpublished pages, the names and emails of your editors, and often personal data inside the content itself. Galerne, Scaleway, Bunny, Brevo and Mollie are European companies with no US parent, so the CLOUD Act does not reach the data they hold for you.
Your own choices still count. A site hosted on a US platform, or an agent that sends content to a US model provider, moves that content under other rules. Galerne shows you which agents have access, and you decide where your content goes from there.
What you can check
- exportDownload everything as NDJSON on every plan, with
galerne exportor the API - agentsEvery agent and OAuth client with access is listed per project, with a kill switch
- historyEvery change records who made it, person or agent
- audit logWho did what in the project, on Business
- deletionDeleting a project revokes its tokens at once. Its database and media files are erased 30 days later