French WordPress hosting for the strictest regulator in Europe.
The CNIL does not wait for complaints. It publishes decisions about specific tools, and French sites are the ones that find out what those decisions mean.
Measurement is the exposed part.
French enforcement has concentrated on analytics, fonts and everything else a page quietly fetches from elsewhere.
Nothing measures before consent
Analytics that runs and then respects a preference has already recorded the visit. Measurement is held until a choice is made, which is the distinction French decisions have turned on.
No fonts or scripts fetched from elsewhere
A webfont loaded from another provider sends the visitor's address to that provider on every page view. The platform serves nothing from outside, so the only external calls are ones you chose.
Storage in the EU, named
Site, backups and logs sit in the EU and we will say where. French organisations are asked this in procurement more often than anywhere else we operate.
Delivery for a compact audience
France is geographically small and densely connected. There is no performance reason to accept an origin that turns every uncached request into a long trip.
Records in French when needed
Processing agreements and subprocessor lists are provided in a form a French legal team can actually file.
The rules are the same. The enforcement is not.
France applies the same regulation as its neighbours and applies it harder, with named decisions about named products. A setup that passes elsewhere gets tested here.
- Measurement blocked until consent is recorded
- No third-party assets injected by the platform
- EU storage location named for site, backups and logs
- Agreements provided in usable form
Fast is the easy requirement.
Serving France quickly is straightforward. What takes work is a page that does not reach out to anywhere the visitor did not agree to.
What we change for French sites
Enforcement here focuses on what a page fetches and when it measures, so that is where the configuration goes.
| Setting | What we do | Why |
|---|---|---|
| Measurement timing | Held until a consent choice exists | French decisions have turned on analytics that ran first and honoured a preference afterwards, by which point the visit was already recorded. |
| External asset fetching | Nothing served from outside the site by default | A font or script pulled from another provider transmits the visitor's address to that provider on every view, which is a transfer nobody entered in a register. |
| Storage disclosure | EU location named for site, backups and logs together | French procurement asks this earlier and more precisely than elsewhere, and a network-level answer ends the conversation. |
| Log retention | Windowed rather than open-ended | Keeping request logs indefinitely accumulates personal data for a purpose nobody documented at the time it was collected. |
| Documentation format | Agreements and subprocessor lists supplied for filing | A French legal team needs something to attach to a record, not a summary given over a call. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Why is France stricter than other EU countries?
Can I use Google Analytics on a French site?
Do you load web fonts from elsewhere?
Where is my French site stored?
Pass the test before it is set.
Move the site to an EU origin - migration is free, records provided.