Skip to Content
Trust centerSubprocessor list

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

SubprocessorFunctionLocationData class
Amazon Web Services (AWS)Primary cloud infrastructure — compute, storage, data planeus-east-1, eu-west-1All operator-scoped data at rest and in transit
CloudflareEdge network, DDoS mitigation, web application firewall, static asset deliveryGlobal (Anycast)Request metadata and static assets; no operator-scoped row data
WorkOSIdentity plane — single sign-on, directory synchronisation, user lifecycleus-east-1Operator identity records, group memberships, session tokens
Anthropic, OpenAI, Google VertexThird-party model inference at the redacted-to-cloud tierus-east-1, eu-west-1Prompt content with personally identifiable information redacted per per-operator tier policy; providers are contractually prohibited from training on transmitted data
DopplerSecrets management — platform-side credentials onlyus-east-1Platform credentials; customer credentials excluded
SentryError trackingeu-west-1Application-layer errors with personally identifiable information scrubbing; row-level payload excluded
PostmarkTransactional email deliveryus-east-1Recipient 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.