Where the search runs
- The search in the corpus runs on our server at Infomaniak, a Swiss hosting provider.
- Embeddings, the vectors used to find relevant passages, are computed locally on that server.
- No third-party AI API is used for search.
Trust and hosting
Where Janine runs, and what it can see
A plain description of our current technical setup, including what is not covered yet.
Where is Janine hosted, and who processes the data?
The corpus search runs on Circulab's server at Infomaniak, a Swiss hosting provider. Embeddings are computed locally and no third-party AI API is used for search. MCP access is read-only, token-protected and encrypted over HTTPS. Talents that generate text use the Claude API from Anthropic, a US company.
What MCP access allows
- Read-only: Janine cannot write, edit or delete anything, and does not store your documents.
- Protected by a personal token: without a valid token, every request is refused.
- Encrypted in transit: all traffic goes over HTTPS.
- Your token gives access to a defined scope of the corpus, and nothing else.
- Today, the content of your MCP queries is not logged.
Talents and Anthropic
- Talents that generate text, such as a business model synthesis or a vulnerability analysis, use the Claude API from Anthropic, a US company.
- Talents that only read the corpus, such as the weekly watch, call no AI model.
- When resources are added to the corpus, their summaries and keywords are produced with the Claude API. This concerns our documents, not your queries.
Your own AI tool
- The results Janine returns are then handled by the AI you use (Claude or another), under that provider's terms.
Need a 100% European chain?
Ask us. We study each request case by case; there is no ready-made sovereign offer today.
Mention “100% European chain” in your message.
Not covered yet
- No standard SLA or DPA (data processing agreement): available on request for organisations.
- This page describes our current technical setup. It is not a contractual commitment.