Subprocessors
Not yet in effectVersion 2026-10-24Last updated October 31, 2026
Draft for launch
This document is not yet in effect. It describes Attemper as it will work when it launches, and it may change before then.
The short version
- Three companies host and deliver Attemper: one for the database, sign-in and the storage of the data file you download, one for the application, one for email.
- The services you connect are not on this list. They receive data because your runbooks send it to them.
- We add a new subprocessor here, and email workspace owners, at least 15 days before it starts.
This summary helps you read the document. It is not part of it, and the full text below is what applies.
What this page is
A subprocessor is a company Attemper uses to process customer data on our behalf. Our Data Processing Addendum lets us use the companies listed here, requires each to protect the data at least as well as the Addendum requires of us, and keeps us responsible for them.
Current subprocessors
| Company | What it does for Attemper | Data it processes | Location |
|---|---|---|---|
| Supabase | Hosts Attemper's database and handles sign-in, including the authorization step when you connect an agent; stores the data file you download, for about a day | Account details, workspace data, Customer Content, Run Records, encrypted Credentials, the data file you download | United States |
| Vercel | Hosts and runs the Attemper application and its scheduled jobs | All data the application handles while it handles it, including request logs | United States |
| Resend | Sends the emails Attemper sends about your runs, and the email that carries your download link | Your email address and the content of each email: the runbook's name, what started the run, the step that is waiting or stopped with its tool and connection, the values in that step (up to 2,000 characters), the reason a run stopped (which can quote the connected service's reply), and a link to the run; for a download, your workspace's name and the link to your data file, which works only with your sign-in | United States |
When paid plans launch, the company that sells them for us, or our payment processor, will be added here before it processes any data.
Before we run any training on customer records, we will add here every company that stores or processes training data for us, at least 15 days before it starts.
What is not on this list
The services you connect. When a runbook calls a code host, a payment provider, your database or any other Connected Service, it sends data there on your instructions. Those services act under your own agreement with them, not for us, so they are not our subprocessors.
Webhook senders. A service that calls one of your webhook addresses sends data to Attemper for you. It is a source of Customer Content, not a subprocessor.
Changes to this list
We add a new subprocessor to this page, and email the owner of every workspace, at least 15 days before it starts processing customer data. The Data Processing Addendum explains how to object.
Version history
| Version | Date | What changed |
|---|---|---|
| 2026-10-24 | October 24, 2026 | First draft, for review before launch. |