← Back to Trust & Security
AI Model Register
Version: v1.3
Last updated: 07.08.2026
Next review: 01.10.2026
This register separates the contracting partner, the underlying model provider, and the customer-facing model. Verification status shows what is confirmed from code: partial = route or default region appears in code, but region/retention/ZDR need separate config or contract evidence; no = active use or route is not confirmed from code. ZDR enforcement is not currently visible in code (no ZDR/no-logging headers).
| Model family | Contract partner | Route | Processing region | Retention | Verification |
|---|---|---|---|---|---|
| Gemini | OpenRouter | OpenRouter API | US for now | OpenRouter does not retain prompts/responses; ZDR header enforcement not visible in application code | partial |
| Claude | OpenRouter | Not confirmed as an active route | Not confirmed | Not confirmed | no |
| GPT | OpenRouter | Not confirmed as an active route | Not confirmed | Not confirmed | no |
| Image models | Must be verified separately | Must be verified separately | Not confirmed | Not confirmed | no |
| Transcription / meeting | Recall.ai | Meeting agent pipeline | eu-central-1 (confirmed) | Retention and deletion practices are not confirmed from code | partial |