Data residency

Every page you send URLpipe is fetched, rendered and stored on our own servers in Europe, on every plan. Turn on EU processing and the AI model runs there too, so no part of a request leaves the EU.

What already runs in Europe

We run our own infrastructure rather than renting capacity wherever it is cheapest. That means the parts of a request you might expect to be spread across regions are not:

• The headless Chrome that loads your URL, and the network it fetches from
• The Postgres that holds your account, your request history and your stored results
• Every operation that never calls an AI model — /html, /markdown, /screenshot, /console and /lighthouse

So for most of the API the answer is already yes, with nothing to switch on. /markdown is worth calling out: it converts the rendered page itself rather than asking a model to, so the cleanest way to feed European web content to your own LLM never leaves Europe either.

What the EU setting changes

Three operations ask an AI model a question: /meta, /keywords and /summarize. That model is the one step that can sit outside Europe. Switch your organization to EU processing and those calls go to a European endpoint instead, where they are decrypted inside the EU and served only by EU providers — with no fallback to a host outside it.

What stays the same

• The same endpoints, the same request and response shapes, the same API keys
• The same credit costs — EU processing carries no surcharge
• The same retention guarantee. On either setting we route only to hosts that neither log your prompts nor keep them, so the model provider retains nothing either way. Residency is the part the setting changes.

What to expect when you switch

• The European model is a different one, so summaries and keyword lists may read a little differently. The response shape does not change.
• Results stored before you switched are still served from your history until they age out. Send max_age=0 on a request to skip stored results and have it processed fresh under the new setting.

A note on what the law actually asks

The GDPR does not require personal data to stay inside the EU — transfers are lawful under an adequacy decision or standard contractual clauses. Residency is usually asked for by a customer, a procurement process or a data protection officer who would rather not run a transfer impact assessment at all. This setting is how you give them that answer without changing anything else about your integration.

For what we store, for how long, and who processes it, see the privacy policy.