Naposledy upraveno 2026-08-30
Sub-processors
Tento dokument vydáváme pouze v angličtině. Závazné je anglické znění — překlad by byl druhou smlouvou, která se s originálem může rozejít.
The companies we use to run vitrinka, what each one does, where it processes, and the safeguard that covers it. This page is the authoritative register referenced by the privacy policy and the data processing agreement.
1How changes are announced
We add a sub-processor only when the service needs it. Organisation owners are emailed at least 30 days before a new sub-processor starts processing customer content, naming the company and what it will do; the data processing agreement gives you the right to object. This page is updated on the same day the notice goes out, and the date above always tells you the register's version.
2Current sub-processors
| Entity | What for | Location | Safeguard |
|---|---|---|---|
| Hetzner Online GmbH, Gunzenhausen, Germany | Servers and object storage — everything vitrinka stores lives here, encrypted before it arrives | Germany and Finland (EU) | EU processing — no transfer. Art. 28 data processing agreement with Hetzner. |
| Amazon Web Services EMEA SARL (Amazon SES) | Transactional email: verification, resets, invitations, notifications, billing and incident notices | EU (Frankfurt region, eu-central-1) | EU region processing under the AWS GDPR Data Processing Addendum, which incorporates Standard Contractual Clauses for any restricted transfer. |
| Stripe Payments Europe, Ltd. and Stripe, Inc. | Subscriptions, payment and invoicing — card data goes straight to Stripe and never touches us | Ireland and United States | Stripe Data Processing Agreement; EU–US Data Privacy Framework and Standard Contractual Clauses for US processing. |
| Anthropic, PBC | The model provider behind eve, our AI service — receives request content only when your workspace runs an AI action on plan credits | United States | Commercial agreement with a data processing addendum incorporating Standard Contractual Clauses; no training on your content. |
| Apple Inc. · Google LLC · Mozilla Corporation (web-push services) | Delivering web-push notifications — only if you enable push, and only via the service your own browser uses | Depends on your browser | Push payloads carry a title, short body and link; delivery runs on your consent, under the browser vendor's push-service terms. |
| Telegram Messenger Inc. | Notifications to a Telegram chat — only if you deliberately link one | Outside the EU | Used only on your consent; unlink the chat in notification settings to stop it. |
| GitHub, Inc. | GitHub sign-in, if you use it; commit metadata and, when you file an issue from a board, the issue title and text derived from your annotation — only if you connect the GitHub app | United States | GitHub Data Protection Agreement; EU–US Data Privacy Framework. |
3Deliberately not on this list
- An AI provider your organisation connects with its own key
- OpenRouter, OpenAI, Anthropic, an OpenAI-compatible endpoint or your own eve — connected by you, under your contract. It processes on your behalf, not ours: it is your processor, and which one you trust is your call, not a row we can add or swap.
- An AI assistant you connect to a workspace
- What a Claude or ChatGPT connection's tool calls return goes to the provider you connected, as part of your conversation with it, under that provider's policy. You are the one sending; the privacy policy's section 7 has the details.
- Sentry and umami
- Error tracking and product analytics run self-hosted on our own Hetzner servers. No third party receives them, so there is nothing to list.