Everyone who touches the data.
A complete list. If we add one we will add it here.
| Provider | What it does | Location |
|---|---|---|
| Cloudflare | Site and worker hosting, DNS, KV storage for page counts and registry records, inbound email routing | Global CDN, EU entity |
| Plausible | Cookieless aggregate analytics | EU |
| Resend | Outbound email | EU (Ireland) |
| Google Workspace | Mailbox where inbound mail is delivered and read | EU/US |
| Sentry | Error monitoring for the registry worker; exception type, message and stack only, payloads scrubbed | US |
| GitHub | Public source code, issues and discussions | US |
| Sigstore | RFC 3161 timestamps and the Rekor transparency log for registry receipts; public by design | Public infrastructure |
Engagement work is different: if a pilot or Sprint involves your data, what we may touch and where is fixed in the engagement agreement before anything starts, and a data processing agreement is available on request. We do not send client material to any provider above beyond what is needed to do the work, and we do not use it to train anything.