Subprocessors
Third parties that process data on our behalf, and what each one sees.
The third parties below process data on our behalf. The list lives here in public, so your security team can work through it before there is any conversation to have.
| Subprocessor | Purpose | Data processed | Location |
|---|---|---|---|
| Amazon Web Services | Hosting of the policy engine, decision log, and customer environments | Decision records, policy configuration, agent identifiers | eu-central-1, Frankfurt |
| Amazon Web Services (SES) | Transactional and support email | Contact details of named customer contacts | eu-central-1, Frankfurt |
| VGS | Card credential tokenization at the edge | Card data, before it reaches Saifuro | European Union |
| Datadog | Infrastructure monitoring and operational logging | Operational telemetry and system logs | European Union |
| Linear | Support and engineering issue tracking | Contents of support requests raised by customer contacts | United States |
Agent conversation content is not collected by Saifuro, so it is not passed to any subprocessor. Primary account numbers never enter Saifuro systems, and the only entry above that sees them is VGS, where tokenization happens before data reaches us.
The decision log and policy configuration stay in the European Union. The only subprocessor outside it is Linear, which holds support correspondence and no decision data.
Changes to this list
We notify customers at least 30 days before a new subprocessor begins processing customer data, which leaves time to object under the data processing agreement signed at onboarding.
Data residency and retention
The current region is eu-central-1 in Frankfurt. Additional regions are available on request. Retention windows for the decision log are set per deployment and recorded in the data processing agreement, which is provided for review before signature. The log is exportable by you at any time.
Last reviewed: 20 August 2026.