Subprocessor list
The Nebbos platform engages a defined set of subprocessors for platform operation. Each subprocessor, its function, its operating location, and the class of customer data it processes are enumerated on this page. Change-notification commitments are specified below.
This list is authoritative. Services not on this list do not receive customer data. Additions are notified in writing at least thirty days ahead of the subprocessor’s activation.
Current subprocessors
| Subprocessor | Function | Location | Data class |
|---|---|---|---|
| Amazon Web Services (AWS) | Primary cloud infrastructure — compute, storage, data plane | us-east-1, eu-west-1 | All operator-scoped data at rest and in transit |
| Cloudflare | Edge network, DDoS mitigation, web application firewall, static asset delivery | Global (Anycast) | Request metadata and static assets; no operator-scoped row data |
| WorkOS | Identity plane — single sign-on, directory synchronisation, user lifecycle | us-east-1 | Operator identity records, group memberships, session tokens |
| Anthropic, OpenAI, Google Vertex | Third-party model inference at the redacted-to-cloud tier | us-east-1, eu-west-1 | Prompt content with personally identifiable information redacted per per-operator tier policy; providers are contractually prohibited from training on transmitted data |
| Doppler | Secrets management — platform-side credentials only | us-east-1 | Platform credentials; customer credentials excluded |
| Sentry | Error tracking | eu-west-1 | Application-layer errors with personally identifiable information scrubbing; row-level payload excluded |
| Postmark | Transactional email delivery | us-east-1 | Recipient addresses and message body content |
Data residency
Operator-scoped structured data resides in the region assigned at deployment. The default region for Team-tier operators is us-east-1. Enterprise-tier operators may specify eu-west-1. Regional boundary crossings occur only through an explicit, audit-logged replication event.
Change process
- Proposed additions are notified in writing to every enterprise contact on file, and recorded as a dated entry in the history section of this page, at least thirty days ahead of subprocessor activation.
- Removals are notified within seven days of removal.
- Enterprise operators retain a thirty-day objection window during the notice period. Unresolved objections entitle the operator to terminate the affected contract for cause under the executed data-processing addendum.
Document requests
Written subprocessor confirmations and per-subprocessor data-processing addenda are available on request at enterprise@nebbos.ai.