Legal
Subprocessors
Last updated: 27 July 2026
Ad Astra Computing uses the following subprocessors to provide AER. A subprocessor is a third party that processes personal data on behalf of our customers. We will update this page before engaging a new subprocessor; customers who want notice of changes can write to [email protected] and we will notify them by email.
Current subprocessors
| Provider | Entity and location | Purpose | Data in scope |
|---|---|---|---|
| Cloudflare | Cloudflare, Inc. United States (global edge network) | Hosting and compute (Workers), database (D1), session storage (Durable Objects), object storage (R2), content delivery, DDoS protection and transactional email delivery | All service data, including account contact details, tenant configuration and recorded event metadata |
AER records metadata only by design: model names, token counts, tool names, hosts and paths. Prompts, completions, request bodies and headers are never captured, so they can never reach a subprocessor.
Transparency services that are not subprocessors
| Service | Purpose | Data in scope |
|---|---|---|
| Sigstore Rekor (Linux Foundation) | Public append-only transparency anchoring of records | Record hash and Ed25519 signature only. No personal data and no event content ever reaches the log, so Rekor is not a subprocessor; it is listed here for completeness |
Related documents
The privacy policy describes what AER records and how long it is retained. The data processing agreement incorporates this subprocessor list by reference; contact [email protected] to execute a DPA.