Subprocessors
AEGIS by Hu engages the third parties listed below to deliver the platform. Each receives only the personal data described, under a signed Data Processing Agreement. Customers receive at least 30 days’ advance notice of any addition or replacement and may object on data-protection grounds, per clause 6.2 of the customer DPA.
Active subprocessors
| Vendor | Purpose | Personal data | Region | Certifications | DPA |
|---|---|---|---|---|---|
| Supabase | Primary database; row-level data store | All customer-uploaded personal data | EU (Ireland, AWS eu-west-1) | SOC 2 Type II | DPA |
| Clerk | Authentication (SSO, MFA, session management) | End-user emails, names, IPs, device metadata | US (Clerk offers no regional hosting option on any plan) | SOC 2 Type II | DPA |
| Vercel | Application hosting (Next.js front-end + edge middleware) | All request-level data in transit; no persistent storage | Serverless functions in dub1 (Dublin, EU); edge middleware global | SOC 2 Type II, ISO 27001 | DPA |
| Sentry | Error / exception monitoring | Stack traces, user IDs in error context (PII scrubbed via beforeSend hook) | EU | SOC 2 Type II, ISO 27001 | DPA |
| Better Stack | Logs + uptime monitoring + status page | Application log lines; may contain user IDs and tenant IDs | EU | SOC 2 Type II | DPA |
| GitHub (Actions, repository) | Source control + CI/CD | None expected — the repository holds no production data; CI processes test data only | US | SOC 2 Type II, ISO 27001 | DPA |
| Anthropic | AI / LLM-backed features (analysis, narrative generation) | Whatever the customer submits to an AI route — may include personal data depending on use case; transmitted under DPA terms with no training-data retention | US | SOC 2 Type II, ISO 27001 | DPA |
| OpenAI | Text embeddings for agent retrieval | Agent input text submitted for embedding — may include personal data depending on what the customer submits to an agent | US | SOC 2 Type II | DPA |
| Resendplanned | Transactional email | Recipient email + message body | EU | SOC 2 Type II | DPA |
Per-vendor notes
- Supabase
- One database for every tenant today. Regional projects for the UK, DIFC, Singapore and Hong Kong are designed for but none is live (see docs/DATA_RESIDENCY.md).
- Backups: daily automatic backups by Supabase in the same region. Point-in-time recovery is not confirmed on the current plan, so it is not claimed; a paid plan with point-in-time recovery is planned for the first paid pilot.
- Onward subprocessor: AWS (their host) — see Supabase's own subprocessor list.
- Clerk
- Residency: Clerk hosts sign-in data in the US and offers no regional hosting option on any plan (checked on clerk.com/security, 13 Nov 2026). Before the first EU regulated customer goes live with real data, we will hold either a dated commitment from Clerk or a move to a provider that hosts in the EU.
- MFA: TOTP and passkeys are supported. MFA is not yet required for every user.
- Vercel
- Production hosting. The function region is pinned in apps/web/vercel.json; edge middleware runs at the edge location nearest the request and stores nothing.
- Better Stack
- Listed so that the register does not under-disclose. The application has no Better Stack client: it writes structured logs to the hosting platform. Whether a log drain to Better Stack is switched on in the hosting console is not confirmed; if it is not, this entry will be marked planned.
- Anthropic
- Training-data retention: disabled by default for paid API customers under Anthropic's commercial terms. We do not opt in.
- Routes that send data to Anthropic: any /api/* route that opens a governed model call through the agent-call wrapper in apps/web/src/lib/agents/callAgent.ts, including the narrative surfaces that reach it through apps/web/src/lib/aiComplianceEngine.ts. No data leaves the platform when the AI kill switch is engaged, the tenant budget is exhausted, or no API key is configured — those calls return a deterministic rendering instead, and the surface says so. The customer DPA flags this as a sub-processing relationship; the UI labels AI-backed actions explicitly.
- OpenAI
- Added 3 Aug 2026 after a register-accuracy check. OPENAI_API_KEY has been set in the production environment since ~May 2026, so apps/web/src/lib/agents/embeddings.ts has been sending agent input text to api.openai.com in production while this register omitted the vendor.
- Scope is embeddings only — text submitted to the embeddings endpoint for agent retrieval. Not used for generation.
- The embeddings path is conditional on OPENAI_API_KEY; unsetting it removes this sub-processor.
Non-personal-data vendors
Vendors used in adjacent contexts (marketing site, billing) that don’t process customer personal data and therefore aren’t subprocessors in the GDPR sense. Listed here for transparency only.
| Vendor | Purpose | What we send |
|---|---|---|
| Cloudflare | DNS / DDoS protection on the marketing domain | DNS queries only |
| Stripe (planned) | Billing | Customer billing contact + payment data only — separate from platform data; their own DPA applies |
Sub-subprocessors
We do not maintain a public list of our subprocessors’ own subprocessors. Customers can request these from each vendor’s public subprocessor page (linked above) or ask us via the DPO email.
Last reviewed: 2026-11-22 (page renders the live data from @/lib/subprocessors).