Subprocessors
| Company | What they do for us | Data involved | Location |
|---|---|---|---|
| Amazon Web Services, Inc. | Hosting, database storage, encrypted backups, secrets storage, and delivery of the service's email (Amazon SES). | All Customer Data and account data. | United States (AWS US East (Ohio), us-east-2) |
| Anthropic, PBC | The AI model behind the SOC agent, only for organizations that use it. Not permitted to train on this data under its commercial terms. Organizations that add their own Anthropic key use Anthropic under their own agreement instead. | Summaries of failing checks, which can include resource names such as bucket names and AWS user names. | United States |
| Zoho Corporation | Our business email, used to receive and answer messages you send us. | The contents of emails you send us. | United States |
Services you connect yourself
When you connect GitHub, SOC Binder reads repository settings through GitHub’s API on your instruction. GitHub is your vendor rather than ours for that data, and your own agreement with GitHub governs it. The same applies to AWS when we read your AWS account.
Not subprocessors
Let’s Encrypt issues our TLS certificates and receives no customer information. We use GitHub to host our own source code and build pipeline; no Customer Data goes there.
If you choose to sign in with Google, Microsoft or GitHub, that provider confirms who you are under its own terms; it receives no Customer Data from us.
Text messages: we have not chosen a text-message provider yet. One will be listed here before any text is sent through it.
Changes
We update this page before a new subprocessor begins processing Customer Data. Customers with a signed Data Processing Addendum can ask to be notified by email at legal@socbinder.com.