Sub-processors of client personal data
These providers process personal data on our behalf when we operate an assistant for a client. They are authorised under section 5 of the data processing agreement.
Which providers handle a particular assistant depends on the delivery it runs on: our Cloudflare-hosted delivery, or our AWS regional delivery in the London region. Your deployment record confirms the delivery for your assistant.
| Provider | Purpose | Data processed | Location and safeguards |
|---|---|---|---|
| Cloudflare, Inc. and affiliates | On the Cloudflare-hosted delivery: hosting the assistant and its administration; short-term conversation storage; private storage of approved content and release records; the gateway through which model requests are sent; the classifier that assigns fixed topic categories for aggregate reporting; network security and access control. On the AWS regional delivery: only the sign-in step of our central administration site, which passes an administrator's identity to the regional service. Conversations, approved content and model requests for that delivery do not pass through Cloudflare. | On the Cloudflare-hosted delivery: conversation content in transit and in short-term storage; technical data such as IP addresses; pseudonymous session identifiers; approved client content; administrator identities. On the AWS regional delivery: administrator identities only. | Headquartered in the United States with a global network. Storage can be restricted to a jurisdiction where a deployment is configured for it. Transfers are covered by the standard contractual clauses and UK addendum in the Cloudflare data processing addendum. See also Cloudflare's sub-processors and its Workers AI data usage terms, which state that customer inputs and outputs are not used to train models. |
| Anthropic, PBC | The language model that generates each answer on the Cloudflare-hosted delivery, called through its commercial API. On the AWS regional delivery, Anthropic models are served through Amazon Bedrock in the London region instead, and Anthropic, PBC does not receive the data. | The question, the recent conversation context and the approved content relevant to that question, sent with each request; the generated answer. | Headquartered in the United States. Transfers are covered by the standard contractual clauses in the Anthropic data processing addendum, which is incorporated into its commercial terms. Those terms state that Anthropic may not train models on customer content. Inputs and outputs are deleted within 30 days as standard; zero data retention can be arranged for a deployment and is recorded in that deployment's order form. |
| Amazon Web Services, Inc. and its EMEA affiliate | Hosting assistants deployed on our AWS regional delivery: the chat and administration runtime; short-term conversation storage; private storage of approved content and release records; encryption keys and secrets; and model inference through Amazon Bedrock. On that delivery, Anthropic Claude models served through Amazon Bedrock generate each answer, and an Amazon model (Amazon Nova Micro by default) assigns the fixed topic and outcome categories used for aggregate reporting. | Conversation content in transit and, in standard configuration, in short-term conversation storage; the question, the recent conversation context and the approved content relevant to that question, sent to the model with each request, and the generated answer; technical data such as IP addresses processed in transit; pseudonymous session identifiers and session control metadata; approved client content; administrator identities. Central reporting holds fixed categories and counts only, never conversation content. | United Kingdom, in the AWS London region (eu-west-2). The runtime, storage, encryption keys and model inference are configured for that region only, with no cross-region inference profile, replica or fallback. AWS is headquartered in the United States, and AWS account, billing and service-management metadata are not confined to the region. In standard configuration, conversation state is deleted within 72 hours of the conversation starting and is not covered by point-in-time recovery or replicas. Amazon Bedrock invocation logging is turned off. AWS states that, for the models we use, Amazon Bedrock does not store model inputs or outputs by default (see its abuse detection terms for the exceptions), that model providers have no access to prompts or completions, and that customer data is not used to improve the base models. The AWS GDPR data processing addendum, including its UK GDPR addendum, forms part of the AWS Service Terms. |
Providers we use to run our own business
These providers support Simple Things as a company. They do not process candidate conversations or other personal data from a client's assistant, so they are not sub-processors under the data processing agreement. Our privacy notice explains how they handle the personal data of people who contact us.
| Provider | Purpose | Data processed | Location and safeguards |
|---|---|---|---|
| Cloudflare, Inc. | Serving this website and, when it is enabled, storing enquiries sent through the enquiry form. | Technical data for site visits; enquiry form contents. | Enquiry storage is configured for Cloudflare's European Union jurisdiction. Cloudflare's data processing addendum applies. |
| Cal.com, Inc. | Booking a call with us. | Name, email address, chosen time and anything you add to the booking. | United States. Cal.com privacy policy. |
| Zoho Corporation | Business email and calendar. | Correspondence with us, including enquiry notifications. | Region depends on the account. Zoho privacy policy. |
| Google LLC | A second mailbox that receives a copy of enquiry notifications. | Enquiry notifications and related correspondence. | United States. Google privacy policy. |
How we tell you about changes
We update this page, with the date at the top, before a new sub-processor processes client personal data. Care plan clients receive written notice at least 30 days in advance and may object under section 5 of the data processing agreement. If you would like change notices sent to a particular person, tell us at hello@simplethin.gs.