Sub-processor list
Every company that processes customer data for Mushy, what it does, the data it handles and where.
Current version 1.0 · Effective
Under legal review
Sub-processors
| Name | Purpose | Data | Location |
|---|---|---|---|
| DigitalOcean | Hosting the app, its database and its files | All customer data, including accounts, workspace content, comments, media and sealed network tokens | United States, one region (New York) |
| Stripe | Payments, subscriptions, invoices and sales tax | Billing contact, billing address, plan and invoices; card details go to Stripe directly and never reach Mushy | [Counsel to complete] |
| Resend | Email, including sign-in emails, notifications and digests | Recipients’ email addresses and the emails’ contents | [Counsel to complete] |
| Anthropic | Model provider, labelling comments and running the built-in agent | Comment text and the content the built-in agent works on; never network tokens | [Counsel to complete] |
| Grafana Labs | Monitoring, with traces, metrics and logs | Workspace and request IDs and technical events; no content, tokens or commenters’ data | [Counsel to complete] |
| Sentry | Monitoring, with error reports | Workspace and request IDs and technical events; no content, tokens or commenters’ data | [Counsel to complete] |
| Support email through Google Workspace, URL safety checks on links in posts through Google Web Risk (pending counsel), and, in Google Cloud, key management for the token vault and encrypted off-site backups | Support emails and replies; the addresses of links in posts; wrapped vault keys, and nightly encrypted backups of the database and files | Google Cloud: United States (us-east4, Northern Virginia). Google Workspace and Google Web Risk: [Counsel to complete] | |
| The status-page provider [name to confirm] | The status page at status.mushymarketing.com | Service status and incident updates; no customer content | [Counsel to complete] |
Where customer data is stored
Mushy stores customer data in the United States, in DigitalOcean’s New York region. The keys that protect the token vault and the off-site backups are in Google Cloud’s us-east4 region in Northern Virginia. Each other company in the table processes only the data its row names, where its row says.
[Counsel to complete: confirm Google Web Risk as a sub-processor before URL safety checks are turned on.]
New sub-processors
- Mushy announces a new sub-processor at least 30 days before it starts processing customer data.
- Owners are told by email and in the app, and from then this page shows the new version of the list as upcoming.
- There is nothing to accept: the Data Processing Agreement already covers the companies on this list.
- Every version of the list stays online with its date, and the version history at the end of this page links each one.
[Counsel to complete: how a customer objects to a new sub-processor, and what happens if they do.]
Contact
EcoEarth Enterprises, Inc., Austin, Texas, USA. Email [email protected] about this list.