Subprocessors
Last updated: {{EFFECTIVE_DATE}}
A subprocessor is a third party Hexa engages to process data on our behalf in order to provide the service. We keep this list short on purpose. This page names our current subprocessors and is kept up to date as it changes.
Current subprocessors
| Subprocessor | Purpose | Location |
|---|---|---|
| Amazon Web Services (AWS) | Cloud infrastructure that runs Hexa: compute, the application database, object storage for artifacts, transactional email delivery, and encryption key management. | United States {{CONFIRM_REGION, e.g. us-west-2}} |
That is currently the extent of it. Hexa's runtime does not send your data to a third-party model provider to operate; if that changes, this list will be updated first. {{LEGAL: confirm there are no other processors, e.g. error monitoring, analytics, or a separate email vendor, before publishing.}}
Not subprocessors: what you connect
The providers you connect through Hexa (your CRM, email, calendar, issue tracker, or any API you register) and the AI client you use (for example Claude) act on your instruction and under their own terms. Hexa brokers access to them under your approval policy and holds your credentials server-side (see Security & governance); it does not add them as its own subprocessors. You control which are connected and can disconnect any of them at any time.
Changes to this list
We will post updates here before a new subprocessor begins processing customer data, and notify customers as required by our data processing agreement. {{CONFIRM_NOTICE_MECHANISM_AND_DPA_REFERENCE}}
Questions
For a copy of our DPA or questions about data processing, contact privacy@hexahq.ai {{CONFIRM_CONTACT_EMAIL}}.