Trust
Sub-processors.
Everything that touches customer data, and what each one does. This list supersedes any earlier version — the previously published page was out of date and omitted five live services.
| Service | What it does | Where | What it touches |
|---|---|---|---|
| Supabase | Application database and authentication | EU — Frankfurt | All stored content: transcripts, reports, memos, personal reads, account data |
| Vercel | Web application hosting | EU — Frankfurt region | Requests in transit; no persistent storage of content |
| Our own GPU machine (OVH infrastructure) | Self-hosted transcription. Not a transcription vendor — the software runs on hardware we operate | EU | Audio, transiently, and the transcript it produces |
| Anthropic | The models that perform the analysis, called server-side | See note below | Transcript content and generated artefacts |
| Resend | Transactional email — memos, personal reads, sign-in links, and the transcript sent to the host | Not yet documented | Email addresses, the contents of memos and reads, and the full meeting transcript as a file attachment |
| Inngest | Background job orchestration | Not yet documented | Metadata and identifiers, not content |
| Stripe | Payments and subscriptions | Not yet documented | Billing data. No meeting content. |
| Upstash | Rate limiting | Not yet documented | Request counters and identifiers, not content |
| OAuth sign-in and calendar read access for capture discovery | Global | Calendar event metadata: title, time, join link, organiser | |
| Microsoft | Calendar access for Teams meetings | Global | The same calendar metadata |
Two honest notes.
We have not documented the processing region for every service in this list, and we will not assert an EU-only guarantee we cannot evidence. Where a cell says not yet documented, that is what it means — ask us and we will find out rather than guess.
We use no analytics and no error-tracking service. If one is added it will appear on this list before it goes live.
Access tokens for calendar connections are encrypted at rest. Payment card data never reaches our systems — Stripe's hosted checkout handles it.
Questions: info@unseendynamics.ai. See also the privacy notice.