Approval and onboarding
New sub-processors require an approved business purpose, security review, contract review, and documented data flow before customer data is processed.
NatorOS uses sub-processors only when they help us operate, secure, support, or improve the service. These guidelines describe how we review those providers and keep processing aligned with customer commitments.
A sub-processor is a third party that may process customer data on behalf of NatorOS to provide the service.
Hosting, storage, networking, observability, and security systems used to run NatorOS.
Support, incident response, analytics, and administration tools used by authorized NatorOS personnel.
AI, workflow, and automation services used when a customer deployment or workflow requires them.
Tools a customer connects directly, such as Slack, Google Drive, GitHub, CRM, ERP, or ticketing systems, are governed by the customer's own authorization choices.
We identify why the provider is needed, what product surface depends on it, and whether a narrower alternative exists.
We document the categories of customer data involved and keep access limited to what the provider needs for the approved purpose.
We review controls such as encryption, access management, auditability, incident response, business continuity, and relevant assurance reports.
We require appropriate confidentiality, data-processing, security, deletion, and onward-transfer commitments before production use.
We assess reliability, supportability, data residency needs, customer requirements, and the ability to remove or replace the provider if needed.
New sub-processors require an approved business purpose, security review, contract review, and documented data flow before customer data is processed.
NatorOS periodically reviews active providers, monitors relevant security changes, and reassesses access when a product surface or customer commitment changes.
When a material sub-processor change affects customer data processing, NatorOS communicates through the customer's agreement, account channel, or support/privacy contact.
Customer data is processed only for approved service purposes and is not used to train shared foundation models.
Enterprise customers can request details about sub-processor usage for their deployment, including data-flow context and security-review materials where available.