Sub-processors
| Sub-processor | What it does for us | Data it processes | Where |
|---|---|---|---|
| Amazon Web Services (AWS) | Hosts our service: the functions, the API front door, the work queues (IDs only), schedules, our registry, logs and console sign-in | Your contacts’ data in memory while our functions run; your account’s data at rest | United States |
| Google (Google Workspace) | Our email: support, notifications and the website’s contact form | Whatever you or your staff send to our addresses, such as console users’ emails and setup-help requests | United States |
Your contacts’ data at rest is in your own AWS account, under your own agreement with AWS: AWS is your provider for that storage, not our sub-processor. Emails go out through your own Amazon SES.
Not sub-processors
Section titled “Not sub-processors”- Mailchimp, when you import from it. You connect your own Mailchimp account and tell us to read it; we don’t send it any data.
- Your own tools that receive our events from your EventBridge bus.
Changes
Section titled “Changes”We update this page before a new sub-processor receives personal data. To object, email support; see Processing details.