Data residency

Storage, compute and the AI that reads your pages all run in the EU (AWS Frankfurt, eu-central-1). One step does not: the check that two flagged passages are really about the same thing runs on TypeSafe’s Jev classifier (System One) in the United States. Jev receives the specific contradicting paragraphs with their page title, section and surrounding context — not whole pages, never the whole space.

Need that step in the EU too? Require European Union residency on the Residency tab in WikiFix Admin. The check then runs on Claude Sonnet on AWS Bedrock in Frankfurt, and every step is in the EU. It costs more credits: Sonnet is a far more expensive model than Jev, so the same scan draws more from your allowance.

The options

Setting	What it means
No requirement (default)	We pick the best model for each step, wherever it runs — today Frankfurt for everything but the one US check. It promises nothing: your content may be processed outside the EU.
European Union	Every step runs on an EU-resident model. More credits per scan.
United States	We cannot serve this today. Our infrastructure is pinned to Frankfurt, so a US requirement is refused rather than served from the EU and labelled US. You can record it; scans stop until we can meet it. If that is a deal-driver, tell us at security@wikifix.ai.

A requirement we cannot meet stops the scan

The scan stops before any work is done — no pages read, no AI calls, nothing billed. It does not fall back to a model elsewhere and carry on. The run is marked failed with the reason, and the Residency tab shows it.

The other route: your own key

On a paid Advanced plan, bring your own Anthropic API key: the AI work runs on Claude under your Anthropic account, spends no credits, and never touches Jev. That is outside what this setting controls — Anthropic processes it under your agreement with them, wherever they do. See Credits & capacity.

Storage is always AWS Frankfurt, whatever you set. Residency governs which models read your content, not where it is kept.