Sub-processors

1. How to read this list

A sub-processor is a third party that may process customer data on our behalf while we provide the service. We impose data protection obligations on each of them and remain responsible for their performance, as set out in the data processing addendum.

We give notice before adding or replacing one. Ask us to be notified directly and we will add you to that list.

2. Current sub-processors

• Model provider — routes document reading, transcription, extraction and assistant requests to vision and language models. Processes the content of the specific request. Configurable: Business and Enterprise customers may point the deployment at their own endpoint instead.
• Infrastructure and content delivery — hosting for the application, database and file storage, and TLS termination at the edge for the public endpoint. Processes all customer data at rest and in transit.
• Email delivery — sends invitations and transactional messages. Processes recipient names and email addresses only, never customer content.
• Error tracking — receives crash and error reports where the deployment enables it. Processes technical diagnostics and may incidentally include identifiers; off unless enabled.

3. What is never sent

• We do not send customer content to analytics, advertising or marketing platforms — we use none.
• We do not send customer content to model providers for training, and we contract on that basis.
• We do not share customer data between workspaces; tenancy is enforced in the data model, not by policy alone.

4. On-premises

An on-premises deployment has no vendor sub-processors. Hosting, storage, email and error tracking are yours, and the model endpoint is whatever you configure — including a model running on your own hardware, in which case no customer content leaves your network at all.

5. Questions

For the current named list with entity details and locations, or to be notified of changes, write to hossein.khaksar@samafinancials.com.