Legal
Subprocessors
Third parties that process data on our behalf, and what each one handles.
Last updated
| Provider | Purpose | Data |
|---|---|---|
| Cloud infrastructure provider | Hosting for the control plane, datastores and object storage | All service data at rest and in transit |
| Probe hosting providers | Region-diverse measurement nodes | Assignment sets and observation batches (no account data) |
| Stripe | Subscription billing | Billing contact and payment details — held by Stripe, not by us |
| Resend | Transactional email — verification, password reset, incident alerts | Recipient address and message content |
| Public blockchain RPC provider | Publishing and reading evidence checkpoint commitments | Merkle roots only — never observation contents or account data |
Notice of change
We update this list before a new subprocessor begins handling customer data. Customers on plans with a data processing agreement receive advance notice by email and may object under the terms of that agreement.
What never leaves
Evidence anchoring publishes a Merkle root — an opaque hash. No domain names, observation contents or customer identifiers are written on-chain. See Evidence & verification.