Under the GDPR, a sub-processor is any business or contractor through which customer data may pass while using a Metabase service. We use partners for some business processes that are not core to our expertise but are critical to our customers having a quality experience.
Here is our list of sub-processors and why we use them:
Service | Location | Why we use it |
---|---|---|
Apollo.io | United States | Enrichment of customer data. |
Amazon Web Services | United States | Hosting for Metabase Cloud accounts, data warehouse for analytics. |
Census | United States | Data transfer from internal tools to hosted applications. |
Clari | United States | Customer call summarization and analysis. |
Clickhouse | United States | Data warehouse for Metabase Storage option. |
Common Room | United States | Community engagement. |
Customer.io | United States | Email communications. |
Docusign | United States | E-signatures for contracts. |
Fillout | United States | Forms used for marketing and product research purposes. |
Fivetran | United States | Data ingestion for analytics purposes. |
Google Analytics | United States | Anonymous url and product usage analytics. |
Grain | United States | Summarization and analysis of calls. |
HotJar | United States | Understanding website visitor behavior. |
Klenty | United States | Customer support and sales communications. |
Mailchimp | United States | Email communications. |
Pipedrive | United States | Sales pipeline management. |
Pylon | United States | Customer support. |
Sentry | United States | Application error logging. |
Snowcat | United States | Anonymous url and product usage analytics. |
StitchData | United States | Data ingestion for analytics purposes. |
Stripe | United States | Customer payments. |
Vercel | United States | Hosting for parts of metabase.com and internal tools. |
VWO | United States | Website experimentation. |
Zapier | United States | Internal business process automation. |
Zendesk | United States | Customer support. |