Subprocessors
The organisations we engage to process Customer Data on our behalf, as the Data Processing Addendum defines it: the data you sync into a replica, the results it serves, its log of statements, and the incident records derived from it.
| Subprocessor | Purpose | What it processes | Location |
|---|---|---|---|
| Amazon Web Services | Cloud infrastructure | Everything the Service holds: the synced copy and the statement log on each replica’s encrypted volume; your database credentials in Secrets Manager; the credentials of one run in the function that runs Mason’s checks of your database; the incident and diagnostic records in their encrypted log group; the control plane’s database and logs; and the email the Service sends. | Ireland (eu-west-1) |
| GitHub | Diagnostics | Our diagnostics workflow runs on a GitHub-hosted machine. When one of our operators runs it for a replica, it reads that replica’s incident records (failed and slow statements with their values replaced, error messages, each synced table’s columns and types, and deployed projects’ structure) to report them as shapes with every name and value removed, and, when asked, encrypts the records to the key of the session investigating. The run’s log keeps the shapes report and the encrypted records. | United States |
| Anthropic | Support and diagnostics | When one of our operators asks for them to investigate a fault, one replica’s raw incident records, encrypted to a key held by the Claude session doing the investigating. Only that session can read them, and they are never sent without a specific fault to investigate. | United States |
What is not on this list, and why
- Our sign-in provider (WorkOS) and our website host (Vercel) process the data of the people who hold accounts, which we control ourselves. They are described in the Privacy Policy.
- Let’s Encrypt issues each replica’s TLS certificate. It receives the replica’s host name and nothing else.
- The tools, clients and agents you connect to a replica (a BI tool, a SQL client, an MCP client, a coding agent) are yours. What they read is your own use of your data.
Changes to this list
Before a new subprocessor processes Customer Data, we email the address of your account at least 15 days ahead and update this page. The DPA’s Section 1(h) says how to object, and what happens if we cannot resolve your objection. The date at the top of this page is the record of its last change.
Questions
Email Henry Marshall, COO, at harry@embeddable.com.