Subprocessors
A subprocessor is a company we engage that may process personal data on behalf of our customers when we provide the Stanch service. This page lists every subprocessor we use today, under the Data Processing Addendum.
1. Current subprocessors
| Subprocessor | What it does | What it receives | Where |
|---|---|---|---|
| Google Cloud (Google) | Hosts the Stanch service: the servers, the database, backups, secrets and operational monitoring. | All Customer Data the service stores (described in Annex 1 of the DPA). | Germany (Frankfurt). Database backups in the Netherlands; disk snapshots in the European Union. |
| Google Workspace (Google) | Sends the service’s email: invitations, sign-in and account notices, and the alerts a customer turns on. | Recipients’ email addresses and the content of those emails. Alerts carry only safe fields such as the device name, application, policy and detector names, never the content Stanch inspected. | Google’s data centres (global). |
| Anthropic, PBC | Generates the answers of Stanch Agent, the optional assistant in the console, with a Claude model. Used only if a customer turns Stanch Agent on. | The question a member of the customer’s team asks, after Stanch checks it with the customer’s detectors and replaces the names of known people and devices with neutral labels; and security metadata such as rule, detector and application names, decisions, counts, times, host names, file types and software versions. Never inspected content, file names, full web addresses or the names Stanch replaced. | United States. |
Inspection runs on the customer’s own devices: the endpoint agent and the browser extension check outgoing content on the computer and send the service a record of what happened, not the content. Content is kept only if a customer turns on evidence collection, and then only encrypted, in the service hosted on Google Cloud. Stanch uses no third-party service for analytics, advertising or error reporting in the product.
2. What is not a subprocessor
Some features send data to services that the customer chooses and configures, under the customer’s own agreements with those providers. They are not Stanch subprocessors:
- alert channels the customer connects, such as Slack, Microsoft Teams, Discord or its own webhook;
- the customer’s identity provider for single sign-on (for example Google, Microsoft Entra ID or Okta) and the customer’s directory when it connects one (Microsoft Entra ID);
- the AI tools, websites and applications whose use Stanch checks on the customer’s devices.
Our marketing website, stanch.ai, is hosted by Cloudflare, which also provides our DNS. That processing concerns website visitors, not customer data, and is described in our Privacy Policy.
3. How we tell you about changes
We will tell customers at least 30 days before a new subprocessor starts to process Customer Data, by email to each customer’s account owners and by updating this page. Anyone else can receive the same notices: write to contact@stanch.ai with the subject “Subprocessor updates”.
If a change is urgently needed to keep the service secure or running, we may make it with shorter notice and will tell customers as soon as we can.
A customer may object to a new subprocessor on reasonable data-protection grounds during the notice period. Section 6 of the DPA explains what happens next.
4. Contact
Questions about our subprocessors: contact@stanch.ai.