Policy

Sub-processors

The hosted deployment runs on the providers below, each named with what it does and the data class it touches. This is the one list; every other page points here. A sealed deployment inside your boundary, which would need none of them, is not built yet. Any addition is announced here before it is enabled.

Current list

The named list is issued to customers. The vendors, the data each one touches and where it runs are named in the data-processing addendum, which is delivered to a customer account. They are not published here. The categories are: cloud infrastructure and database in one United States region; identity verification and payments; a model provider for the separate assistant route, which receives only the text a person sends to it; web hosting; and storage for the public estate. A change is notified to customer accounts before it takes effect.

If you connect an optional integration

Anything you connect is yours, not ours: your warehouses and your own systems are not our sub-processors. Events and deliveries to your systems carry only the fields each event declares, to hosts your organization allowed. Consumer modules in the same service call exchange and public market-data services for their own users; no EOS module sends them data.

Change notice

Any addition to this list is published here at any time before it processes customer data. This page is versioned and prior versions remain retrievable.

Request the two-week EOS assessment: $15,000, read-only, first finding targeted in 14 daysRead-only throughout. If you continue to the $50,000 pilot, the $15,000 assessment fee is credited.