October 25, 2026
# Best web search APIs with EU data residency (2026)
Few web search APIs document a way to process requests in the EU. As of October 14, 2026, Staan hosts its service in Europe, Linkup offers guaranteed local processing on enterprise agreements, and Parallel offers EU data residency for Search API requests in basic mode. Brave, Exa, Tavily, Perplexity, Firecrawl, and SerpApi don't document an EU processing option.
Parallel makes one of the products in this guide. We held every vendor, including ourselves, to the same rule. A claim goes in only if the vendor states it in its own public documentation. Vendor pages change, so treat each fact as true on the date we checked it, and ask vendors directly about anything that matters to you.
## What EU data residency should mean for a search API
Data residency means your requests are processed, and any stored data is kept, in the EU. For a search API, that applies to the whole request, not only the server that receives it. Ask where queries are processed, where the index lives, where inference runs, where pages are fetched from, and what leaves the region.
A country or location setting is often mistaken for residency, but it changes which results you get back, not where your request runs. Sovereignty is a separate question: it's about whose laws apply to the provider. Our explainer on data residency vs data sovereignty[data residency vs data sovereignty] covers the difference.
## Search APIs that offer EU data residency
| Vendor | Documented EU option (October 14, 2026) | What to know |
|---|---|---|
| Parallel | Search API requests in basic mode sent to the EU endpoint, as an optional feature | Minimal billing metadata goes to the US. Live fetch is global and can be turned off. Extract isn't covered |
| Linkup | Guaranteed local processing on enterprise agreements, and Bring Your Own Cloud for selected deployments | By default, queries may be processed in several regions |
| Staan | Infrastructure hosted in Europe | A US fallback supplements some results unless you ask Staan to turn it off |
| Brave | None documented | Provided by a US company |
| Exa | None documented | Offers zero data retention on Enterprise plans |
| Tavily | None documented | Relies on Standard Contractual Clauses for transfers to the US |
| Perplexity | None documented | Hosted in North America |
| Firecrawl | None documented for its cloud service | Its open-source version can be self-hosted on EU servers |
| SerpApi | None documented | A US company. ZeroTrace mode stops search data being stored |
## Parallel
Parallel offers EU data residency as an optional feature, with the commitments set out in the customer's DPA. It covers Search API[Search API] requests in basic mode sent to the EU endpoint. For those requests, the endpoint, the full search index, and inference all run in the EU. EU traffic has zero data retention by default.
**Our concessions.** Only minimal billing metadata goes to the US. That means IDs, the SKU, and a timestamp, never the inputs you send or the outputs we return. Live fetch, which retrieves public pages at request time, runs globally because pages are hosted all over the world. It's optional and can be turned off. The Extract API isn't covered and runs on the default endpoint. Parallel is a US company, so EU residency doesn't change its jurisdiction.
## Linkup
Linkup's data processing documentation[data processing documentation] says it runs infrastructure in several regions, and that by default queries may be processed across them. Under an enterprise agreement, Linkup can guarantee local processing in a chosen geography.
**In Linkup's favor.** Its security documentation[security documentation] describes Bring Your Own Cloud for selected high-tier deployments, where processing runs inside the customer's environment. No other vendor here documents that level of isolation.
## Staan
Staan's FAQ[FAQ] says its infrastructure is hosted in Europe and is subject to European law. It also describes a US fallback that supplements some results when needed, which customers can ask to disable.
**In Staan's favor.** If you need a European provider on European infrastructure, Staan makes the strongest claim of any vendor here.
## Brave, Exa, Tavily, Perplexity, Firecrawl, and SerpApi
None of these six documents an EU processing option, though some offer other privacy controls.
- - **Brave.** Its API privacy notice[API privacy notice] says the service is provided by Brave Software Inc. in the US, with zero data retention for enterprise customers. Brave runs its own index[own index].
- - **Exa.** Its docs offer zero data retention[zero data retention] on Enterprise plans.
- - **Tavily.** Its privacy policy[privacy policy] names a US company and says transfers to US service providers rely on Standard Contractual Clauses.
- - **Perplexity.** Its FAQ[FAQ] says compute is hosted on AWS in North America.
- - **Firecrawl.** Its privacy policy[privacy policy] tells users in Europe that their information is transferred to the United States. Firecrawl is open source, and its self-hosting guide[self-hosting guide] lets a team run it on its own servers, which puts data location in the team's hands along with the operations.
- - **SerpApi.** Its privacy policy[privacy policy] names a Texas company and says international transfers rely on safeguards such as Standard Contractual Clauses. Its ZeroTrace mode stops search data from being stored.
## How to choose an EU search API
Start with the requirement your legal or security team wrote down.
- - **"Requests must be processed in the EU."** Parallel, Linkup on an enterprise agreement, and Staan all document an option. Ask each one what still leaves the region.
- - **"The provider must be European."** Staan is the only vendor here that is.
- - **"Queries can't leave our own cloud."** Linkup's Bring Your Own Cloud is the documented option.
- - **"Nothing may be stored."** That's zero data retention, which is a separate question from location. Most vendors here offer it on some plans, and Parallel applies it to EU traffic by default.
Then test with your own queries, in your users' languages, before you commit.
To use Parallel in the EU, see parallel.ai/europe[parallel.ai/europe] or talk to sales[talk to sales].
## FAQ
### Which web search APIs offer EU data residency?
As of October 14, 2026, Parallel, Linkup, and Staan document a way to process search requests in the EU. Brave, Exa, Tavily, Perplexity, Firecrawl, and SerpApi don't document one.
### Does Parallel's EU endpoint keep all data in the EU?
For Search API requests in basic mode, the endpoint, the full search index, and inference run in the EU, with zero data retention by default. Minimal billing metadata goes to the US and never includes inputs or outputs. Live fetch is global and can be turned off.
### Does Parallel's EU data residency cover the Extract API?
No. It covers Search API requests in basic mode sent to the EU endpoint. Extract runs on the default endpoint.
### Is zero data retention the same as data residency?
No. Zero data retention is about whether a vendor stores your data. Data residency is about where it's processed and stored.
### Does a country setting keep my search requests in the EU?
No. A country or location setting changes which results come back. It doesn't change where the request is processed.
## Sources
All accessed October 14, 2026, except Firecrawl and SerpApi, accessed October 16, 2026.
- - Parallel: Privacy Policy[Privacy Policy]
- - Linkup: Data processing and privacy[Data processing and privacy], Security and compliance[Security and compliance]
- - Staan: FAQ[FAQ]
- - Brave: Search API privacy notice[Search API privacy notice], Brave Search API[Brave Search API]
- - Exa: Zero data retention[Zero data retention]
- - Tavily: Privacy policy[Privacy policy]
- - Perplexity: FAQ[FAQ]
- - Firecrawl: Privacy policy[Privacy policy], Self-hosting Firecrawl[Self-hosting Firecrawl]
- - SerpApi: Legal documents and privacy policy[Legal documents and privacy policy]