[1]What this register is
A subprocessor is a vendor Throughline would use to process customer data on its behalf. This page is the canonical, complete record of them: what each one is for, what data it can touch, and where it runs. Clause [5] of the data processing addendum gives this register its contractual force; the wider security posture lives at /trust.
The register is deliberately short: three vendors, matching what the pricing FAQ already claims. Cloud hosting, error monitoring, transactional email. Shipment contents never leave the infrastructure provider's environment, inside Throughline's own account, and no other vendor receives them.
[2]Current subprocessors
| Subprocessor | Purpose | Data category | Shipment contents | Region |
|---|---|---|---|---|
| Amazon Web Services | Cloud infrastructure. All service compute and storage runs here, inside Throughline's own account. | All service data, encrypted at rest | Stores, encrypted | US (us-east-1) or EU (eu-central-1), per residency choice |
| Sentry | Application error monitoring | Stack traces and diagnostic metadata, scrubbed of payloads before sending | No | United States |
| Postmark | Transactional email: alerts, digests, account mail | Recipient name, email address, message metadata | No | United States |
Scrolls sideways on small screens; the page itself never does. A register with more vendors than reasons is a register that grew unsupervised: each row here exists because removing it would remove a capability.
[3]How changes are announced
- 30 days' notice. Before any subprocessor is added or replaced, notice goes by email to every account administrator, at least 30 days before the change takes effect: the same window the pricing FAQ and the DPA promise. One number, stated three places, kept once.
- This page updates first. The register changes the day notice is sent, with the change dated in the log below, so the page is never behind the email.
- Objection. Clause [5] of the DPA gives the customer a written objection right within the notice window, and a real exit with a refund if the objection cannot be resolved.
- Nothing to sign up for. Notice arrives because you have an account, not because you remembered to join a mailing list.
[4]Change log
- 2026-08-26 · Initial register published: Amazon Web Services, Sentry, Postmark. [version 1.0]
A register without a change history asks to be trusted; one with a history can be checked. That is the entire difference this page exists to show.