Sub-processors
A sub-processor is an outside company that handles personal data for us, such as a hosting or email provider. We list every one below, and the tools we run on our own servers are not on the list because no outside company handles that data.
Last updated
What a sub-processor is
When we use another company’s service to store, send or process personal data for us, that company is a sub-processor. We choose them carefully, and they may use the data only to provide their service to us.
We list every one
The table below names each sub-processor, its purpose and the region where it processes data. We keep it current: a new provider is added to the table before it handles personal data.
Tools we run ourselves
These tools run on our own servers, so no outside company handles the data in them. They are not sub-processors:
- PostgreSQL (database)
- Redis (queues and rate limits)
- Garage (file storage)
- ClamAV (virus scanning of uploads)
- Umami (cookieless analytics)
- GlitchTip (error tracking)
- Uptime Kuma (uptime monitoring)
Changes to this list
We tell clients by email at least 30 days before a new sub-processor starts processing client data.
Questions about a sub-processor?
Current sub-processors
| Provider | What they do for us | Where |
|---|---|---|
| Google Cloud (Vertex AI) | AI models for the assistant, lead summaries and drafting: Gemini for anything with personal data, Claude only for work without personal data | India (Mumbai) for personal data; global for work without personal data |