Fathom's EU routing is automatic, but its scope is configurable

The workload

Fathom Analytics documents a specific data-routing setup rather than a single hosting location. Verified: the EU companies page states that 'EU isolation is enabled automatically' — visitor requests from the EU, UK, Switzerland, Norway, Iceland and Liechtenstein are routed to European infrastructure where personal request data is processed before anonymized analytics continue, and raw EU visitor IP addresses and user agents do not reach the company's US infrastructure. A founder using the default setup does not need to configure anything for this baseline routing; the configuration step only appears for a stricter option.

What the documents show

Verified: the same page states that a founder who wants all global traffic, not only EU traffic, routed through Europe can enable 'Extreme EU Isolation' by pointing the tracking script at a separate EU-specific endpoint, documented on Fathom's EU isolation documentation page as cdn-eu.usefathom.com, which also names Falkenstein, Helsinki and Nuremberg as its EU server locations. Verified: the page states that Fathom is a Canadian company and that the European Commission has issued an adequacy decision recognizing Canada's data protection framework for covered transfers, while also stating explicitly that the decision 'isn't a blanket exemption' from other privacy obligations. Verified: a signed data processing agreement is offered separately, and Fathom's own DPA text states it is governed by the laws of British Columbia and lists its sub-processors.

The operating cost

EU-region routing at the default level carries no separate fee beyond the standard pageview-tier price, since the pages describe it as built into the base product rather than an add-on. The DPA itself is offered at no additional charge for signature, per that page. Configuring Extreme EU Isolation costs only the engineering time to change one script tag, a one-time task rather than a recurring fee, as the documentation describes it.

The stop condition

The documents do not claim that EU hosting alone satisfies GDPR, and this entry does not extend that claim either; whether a specific integration meets GDPR depends on facts the compliance-side entries on this site cover, not on where Fathom routes a request. Editorially, the stop condition for relying on default EU isolation is the point where an organization's own policy requires all traffic, not just EU-origin traffic, to be EU-processed — at that point the documentation itself says the default setting is insufficient and Extreme EU Isolation is the documented alternative.

• Does the organization's own policy require all traffic to be EU-processed, or only EU-origin visitor traffic?
• Has the DPA been signed, and does its Canadian governing-law clause fit the organization's own compliance requirements?
• Is the adequacy decision's limited scope, as the page itself states it, being treated as broader than the page claims?

Fathom's own pages describe a routing choice and a document, not a compliance guarantee, and they say so directly when read past the marketing framing at the top of the page.