Skip to content

Passage judge and data location

The judge scores short passages from documents and memories against a question. It does not write the final answer.

What leaves Snipara

Each scoring request sends the question, passage title and passage text to a judge provider. Passage text is limited to 6,000 characters per candidate. These passages can contain customer document or memory content.

Provider order

Standard projects use Jev (TypeSafe, through OpenRouter, hosted in the United States) first, with Loes Beslis (HostYourAI, hosted in the EU) as the fallback. The judge is optional: when it is not enabled, retrieval returns its ranked passages without this stage.

Project control

The per-project setting Allow the judge hosted in the United States is on by default. Turn it off to use only the EU judge. Partner and integrator projects never use a judge outside the EU; their setting is disabled.

The policy identifies partner projects from an integrator-client link or a business-partner workspace on the project team. Unknown projects or failed policy lookups restrict judging to the EU. This rule governs where passages are judged; it is not a residency guarantee for every processor.

Provider regions

Providers are tried in order, and each one carries a region. A provider whose region is unknown is treated as outside the EU, so it never receives passages from an EU-only project. Memory recall has its own judge setting.

Abstention and failure

The first provider that answers scores the candidates. Below its support threshold, document retrieval returns no supporting source; recall returns no supporting memory. Optional second rounds are off by default. Missing keys, policy exclusions and failed providers skip entries. An exhausted chain keeps the previous ranking and does not turn an outage into an abstention.

Privacy policy and trust boundaries describe the wider data flow. No certification or universal EU or Swiss residency is implied.

Last updated: September 24, 2026