Swiss WordPress hosting for a country surrounded by a union it left out.
Switzerland is not in the EU and not covered by its rules by default. It has its own law, its own regulator, and four official languages on a great many sites.
Its own regime, not a copy.
Assuming GDPR compliance covers Switzerland is the most common mistake here, and it runs in both directions.
A separate law with separate duties
The revised Federal Act on Data Protection is its own regime, not a translation of the European one. Obligations overlap heavily and differ in specifics, so the agreement names which applies.
German, French, Italian and Romansh
A Swiss site is routinely three or four complete versions rather than one with a language switcher. Each is cached separately and declared, so none is read as a copy of another.
Where the data sits, in writing
Swiss organisations are asked this early and precisely, and often need the answer to be a specific place rather than a region a provider has named.
Cross-border transfers documented
Data moving between Switzerland and the EU is a transfer under both regimes. It is recorded with a basis rather than treated as internal because the countries are adjacent.
Served close to a small, dense market
The country is geographically compact and well connected, so there is no performance reason to accept a distant origin.
Compliant in Europe is not compliant here.
Most Swiss sites inherited a GDPR-shaped setup because their agency built for the EU. The technical half usually transfers. The paperwork names the wrong law.
- revFADP named explicitly in the agreement
- Swiss–EU transfers recorded with a basis
- Each national language cached and declared separately
- Storage location given as a place
Four sites wearing one domain.
A four-language Swiss site is four full caches, and the measurement worth having is a cold request in the least-visited of them.
What we change for Swiss sites
Two facts drive it: a domestic regime that is nobody's copy, and sites that genuinely exist in several languages at once.
| Setting | What we do | Why |
|---|---|---|
| Regime | revFADP named in the agreement rather than inferred from GDPR | Switzerland has its own law and regulator, and an agreement citing the European regulation leaves a Swiss controller without the document they actually need. |
| Swiss–EU transfers | Recorded with a basis rather than treated as domestic | Adjacency is not membership, so data crossing that border is a transfer under both regimes even though the rules largely agree. |
| National language caching | Cached independently per language with each declared | Swiss sites commonly publish three or four full versions, and serving one from another's cache entry makes them read as duplicates to a crawler. |
| Residency disclosure | Given as a named location for site and backups | Swiss procurement asks this early, and an answer describing a provider's regional network does not satisfy it. |
| Origin distance | Kept short for a compact domestic market | The country is small and densely connected, so accepting a distant origin costs latency for no compensating benefit. |
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.
Does GDPR compliance cover a Swiss site?
Is sending data to the EU a transfer?
How are three or four language versions handled?
Where exactly is a Swiss site hosted?
Answer under the right law.
Move the site across. Migration is free, records provided.