These are the third parties that may process data on our behalf for managed deployments, and what each is used for. We keep the list short and current, and notify customers of material changes in line with the Data Processing Addendum.
| Sub-processor | Purpose | Region |
|---|---|---|
| Amazon Web Services | Hosting, storage, secrets (KMS / SSM) | US / EU (per tenant) |
| Amazon SES | Transactional email (enquiries, alerts) | US |
| Reasoning backend (configurable) | AI triage of findings — a hosted API, or Amazon Bedrock in-VPC, or fully local | Per configuration |
In-VPC / self-hosted deployments have zero external sub-processors for data processing — the console and the classification model run entirely inside your own AWS account, with no data egress.
Change notifications. We notify customers of any new sub-processor before it begins processing customer data, in line with the DPA. To join the notification list, email info@araghatta.com. A signed sub-processor list is available as part of the DPA.
Last updated: 14 August 2026 · This is the canonical sub-processor list; it is also summarised in the Trust Center.