Subprocessors
Subprocessors are third parties that may process data on Align's behalf in the Align-hosted cloud offering. Self-hosted deployments run in your own infrastructure and can avoid most of these entirely (see the notes column).
| Subprocessor | Purpose | Data processed | Notes |
|---|---|---|---|
| Amazon Web Services (AWS) | Hosting, database, storage, cache | All tenant data (encrypted at rest) | Region configurable. Self-host runs on your own infra. |
| Anthropic | Default LLM for decision extraction & analysis | Source text after PII redaction | Default provider. Disable by self-hosting with a local LLM. |
| OpenAI | Optional/fallback LLM | Source text after PII redaction | Only if configured as provider/fallback. |
| Grafana Cloud | Infrastructure telemetry (OpenTelemetry) | Metrics/traces, no customer decision content (redacted in span processor) | Opt-in; OTel is off by default. |
| PostHog | Product analytics | Usage events / metadata, not decision content | Cloud app only. |
Data-handling notes
- PII redaction before LLM egress. Before any text is sent to an LLM subprocessor, Align redacts emails, names, phone numbers, SSNs, IP addresses, and API keys (Microsoft Presidio, on by default).
- Zero cloud LLM egress option. Point Align at a local LLM (Ollama/vLLM) to keep all inference in your environment.
- Telemetry excludes customer content. When OpenTelemetry is enabled, SQL parameters and HTTP request/response bodies are scrubbed before export.
- Billing. Payment processing (e.g. Stripe) applies only if/when self-serve billing is enabled for your account; design-partner accounts have no billing subprocessor.
This list is reviewed as the stack evolves. Material changes to subprocessors will be reflected here.