Last updated: September 25, 2026
To run Transkripsie, we use third-party service providers (“sub-processors”) that may process personal data for the features you request. The list below describes intended data flows; the contractual status, retention terms, and international-transfer safeguards for each provider must be confirmed before the relevant processing begins.
We aim to give advance notice before adding or replacing a sub-processor that processes personal data. To subscribe to change notifications, email privacy@transkripsie.com with the subject line “Subscribe: sub-processor updates”.
| Sub-processor | Purpose | AI purpose | Location | Data shared |
|---|---|---|---|---|
| Hetzner Online GmbH | Application server, database and recordings on server disk and block-storage volume | — | Germany (Falkenstein) | Account data and stored service content handled by the configured hosting and storage environment; encryption coverage depends on production configuration |
| Recall.ai, Inc. | Meeting bot infrastructure for Google Meet, Zoom, Microsoft Teams, and Webex | Captures and relays live meeting audio/video for downstream speech recognition (does not generate AI output) | USA | Meeting join URL, bot session metadata, and the live meeting audio/video stream during recording |
| Soniox, Inc. | Speech-to-text transcription (batch uploads and live streaming) | Automated speech recognition and speaker diarisation | USA | Audio sent for transcription. Soniox storage and deletion depend on the API service used and the deletion workflow; we do not promise a fixed processing-window deletion period |
| OpenRouter, Inc. | Primary generative-AI routing layer | Summaries, chapter headings, meeting titles, chat responses, and translation | USA | Transcript text submitted for requested AI processing. Our requests ask OpenRouter to use only providers that do not keep prompts or collect them for training; retention and model-training treatment otherwise depend on the provider policy and any executed agreement |
| Microsoft Azure (via OpenRouter) | Runs the default language model for generative-AI features (OpenAI's GPT-5 mini) | Summaries, chapter headings, meeting titles, chat responses, and translation | Sweden (Azure Sweden Central) or another Azure region OpenRouter selects | Transcript text relayed by OpenRouter for requested AI processing; retention and model-training treatment depend on the provider policy and any executed agreement |
| xAI Corp. | Fallback generative-AI provider | Summaries, meeting titles, chat responses, and translation, used directly only if OpenRouter is not configured or we explicitly switch on a fallback to providers that may retain data | USA | Transcript text submitted for requested AI processing; retention and model-training treatment depend on the provider policy and any executed agreement |
| Anthropic, PBC | Fallback generative-AI provider | Summaries, meeting titles, chat responses, and translation, used directly (after xAI) only if OpenRouter is not configured or we explicitly switch on a fallback to providers that may retain data | USA | Transcript text submitted for requested AI processing; retention and model-training treatment depend on the provider policy and any executed agreement |
| Zoho Corporation | Transactional email delivery (sign-up, password reset, security alerts, receipts) | — | USA (Zoho US data centre) | Recipient email address, name, and message content |
| Google LLC | Google Calendar integration (only for users who connect a Google account) | — | USA | OAuth tokens and calendar event metadata (title, time, attendees, conferencing link) |
| Backblaze, Inc. | Encrypted off-site backups (B2 object storage) | — | USA | Encrypted database and audio backup artifacts when a backup run succeeds. Backup key custody, immutability, lifecycle retention, alerting, and complete media recovery are under operational review |
| Stripe, Inc. | Payment processing (when billing is enabled on your account) | — | USA | Name, email, billing address, and payment method tokens. Full card numbers are not transmitted to or stored by Transkripsie |
| Functional Software, Inc. (Sentry) | Application error monitoring and performance tracing, when enabled | — | USA | Stack traces, request paths, and diagnostic metadata when enabled; production enablement and scrubbing coverage must be confirmed |
| Healthchecks.io | Backup and restore-drill job monitoring, when configured | — | Germany | Operational ping metadata only when configured; current production alerting coverage is under review |
| PostHog, Inc. (US Cloud) | Optional product analytics and session replay on public website pages — only if enabled by us and the visitor opts in to analytics | — | United States (US Cloud) | Pages viewed, clicks, and session replays of public pages with all form inputs masked; random analytics identifiers. Visitor IP addresses are not forwarded (requests are relayed through our own domain). Never used inside the app, on recordings, or on shared links |
| Threadchat | Optional RAG integration (only for users who link a Threadchat account) | Optional transcript indexing for retrieval-augmented search (user-initiated integration only) | Varies (per-user VPS) | Transcript text, summaries, and metadata pushed for search/RAG indexing when the integration is enabled |
Last updated September 25, 2026. To subscribe to changes, email privacy@transkripsie.com.