Most analytics tools treat data residency as a paid upgrade or a support ticket. You sign up, you start sending events, and only later do you find out the data took a detour through a region you never chose. By then it is already in someone else's logs.
leatmap takes the opposite stance. Every plan, including the free one, is EU-resident by default. There is no toggle to find and no tier to reach first.
Residency is a routing decision, not a promise
A privacy policy that says "we store data in the EU" is only as good as the path each event actually travels. The moment ingestion runs through a US edge, or a sub-processor buffers your payloads outside the EU, the promise is broken before the data ever lands.
leatmap runs the collector inside the EU and keeps the full path there:
- Events are received by an EU-resident collector, not a global edge that forwards later.
- Sessions, journeys, and the rest of your analytics live in EU-resident storage.
- leatmap does not transfer event data to sub-processors outside the region you choose.
The result is simple to reason about. The data arrives in the EU and stays in the EU.
Pin it to a region you choose
EU-resident is the floor, not the ceiling. On Business, you can pin a workspace to a specific supported region at creation, and leatmap holds your event data there. If your obligations change later, residency can move, with a grace window so nothing breaks mid-flight.
That matters because "the EU" is not one place to a regulator or a procurement team. Being able to name the region, and prove it, is the difference between a confident answer and a hedge.
Why this is a product feature, not a legal one
Residency is usually framed as a compliance burden. We think it is a product feature, because it removes a whole class of work from your plate:
- No re-architecting your analytics when a customer in a regulated industry asks where their data lives.
- No scrambling for a data processing agreement at the worst possible moment.
- No quiet cross-border transfers to explain away in a security review.
You ship the tracking plan, and the residency question is already answered.
The short version
If you have to ask where your analytics data lives, the tool has already failed you. leatmap answers the question up front: in the EU, by default, on every plan, pinned to a region you control on Business.
See how the rest of the platform is built the same way on the pricing page, or read why we enforce consent and PII rules at the collector instead of the browser.
