EgoZ Subprocessors (DRAFT)
⚠️ DRAFT — NOT LEGAL ADVICE. Review with counsel and verify each vendor's current legal entity, location, and DPA before publishing.
Last updated: July 7, 2026
EgoZ engages the following subprocessors to provide the Service. We impose data-protection terms on each that are no less protective than our DPA, and will update this page before adding or replacing a subprocessor.
Infrastructure subprocessors (engaged by EgoZ)
| Subprocessor | Purpose | Data processed | Location |
|---|---|---|---|
| Railway ([railway.app]) | Application hosting + managed PostgreSQL database | All Customer Content at rest + account data | EU-West |
| Cloudflare (R2 object storage) | Backup storage of RAG document originals | Uploaded knowledge-base documents | EU [confirm bucket region] |
| Sentry | Error monitoring / diagnostics | Diagnostic events, PII-redacted before transmission | [confirm region/plan] |
| [EMAIL PROVIDER] | Transactional email (e.g. password reset) | Recipient email address | [region] |
R2 is optional: when object storage isn't configured, RAG document content still lives only in the EU-West database and no originals are sent to Cloudflare.
Model providers (Bring-Your-Own-Key)
Under EgoZ's BYOK model, you configure your own LLM provider and supply your own API key. EgoZ transmits your prompts/context to the provider you choose, using your key, to generate responses. Your relationship with that provider is governed by your agreement with them — they are your subprocessor as much as EgoZ's. Providers EgoZ can route to include:
| Provider | Used when |
|---|---|
| OpenAI | You configure an OpenAI key |
| Anthropic | You configure an Anthropic key |
| Azure OpenAI | You configure an Azure deployment + key |
EgoZ does not send your data to any model provider you have not configured, and does not fund or broker that inference.
Notifications
To be notified of subprocessor changes, [DESCRIBE MECHANISM — e.g. subscribe at CONTACT EMAIL, or watch this page].