Sub-processors
These are the companies that process data on our behalf to deliver the Service. Section 6 of the Privacy Policy describes what each one receives, and the Data Processing Addendum governs the terms. We publish an updated list here at least 30 days before a new or replacement sub-processor begins processing customer content, and notify account holders at the email address on their account.
Current sub-processors
| Sub-processor | Purpose | Location | Transfer mechanism |
|---|---|---|---|
| Anthropic, PBC | AI generation and analysis of content submitted to AI features | United States | Standard Contractual Clauses |
| Railway Corp. | Application hosting and database | United States | Standard Contractual Clauses |
| Stripe, Inc. and Stripe Payments Europe, Ltd. | Payments, billing and tax | European Union and United States | Standard Contractual Clauses |
| Postmark (ActiveCampaign, LLC) | Transactional email | United States | Standard Contractual Clauses |
| Cloudflare, Inc. (R2) | Off-site database backups, encrypted by us before upload | European Union | Not applicable — stored in the EU |
| Functional Software, Inc. (Sentry) | Error monitoring | European Union | Not applicable — stored in the EU |
Others, and why they are not on the list
Sign-in providers. Google and LinkedIn act as independent controllers when you choose to sign in with one of them. They receive no customer content, and you never have to use them: an email address and a password work everywhere they do.
Content delivery: none. Our pages used to load typefaces from Google Fonts and icons from the jsDelivr network, which meant every visitor's IP address — including a customer's colleagues opening a business case shared with them — reached two companies we had never named. We now serve those files ourselves, so no page you load contacts anyone but us.
Changes
Section 7 of the Data Processing Addendum sets out the notice period and your right to object. Questions go to [email protected].