SUBPROCESSOR REGISTER

Every vendor that touches
client data, named.

The privacy notice commits to publishing this. Here it is, generated from the register held inside the platform.

Read the privacy notice Read the Trust page

Current subprocessors

A subprocessor is any vendor that processes, transmits or stores data on behalf of a client. Vendors used only for internal operations, and which never touch client programme data, are not listed.

VENDOR
PURPOSE
DATA
PROCESSING LOCATION
CloudflareHosting and edge
Serves this site and runs the platform worker.
Request metadata. No programme records.
Global edge
Microsoft 365Business tenant
Correspondence and document storage for the operating entity.
Business contact details, correspondence.
EU and US
AirtableProgramme record
Holds the programme record, readings and gate decisions.
Programme data, scores, gate decisions.
US
TallyForm intake
Structured intake where a form is used rather than direct correspondence.
Business contact details, intake responses.
EU
AnthropicModel provider
Generates report narrative from measured scores. Never generates a number.
De-identified scores and layer readings.
US
PayhipStorefront
Sells the practitioner guides. Handles checkout and delivery.
Buyer name, email, transaction record.
EU and US
MakeAutomation
Superseded. No longer in the processing path.
None.
Not applicableRetired
BeehiivNewsletter
Discontinued. No longer in the processing path.
None.
Not applicableRetired

Payment card details are never seen or stored by AI Change Loop. Checkout is handled entirely by the storefront. Protected health information, patient identifiable data and regulated clinical data are excluded from the platform by control, not by policy alone.