PRIVACY NOTICE

What we collect,
and what we never do with it.

Written to be read, not to be survived. Every claim here has a procedure behind it.

Read the Trust page
0client data used to train any model

Privacy notice

EFFECTIVETo be set at publicationVERSIONv2.0CONTROLLEREvolevant LLC, operating AI Change LoopGOVERNING LAWTo be set at publication
01

Who we are

AI Change Loop and Enterprise Architecture Diagnostic are trademarks of Raheel Malik. Evolevant LLC is the operating entity and the contracting party. Both are named because they do different jobs, and a policy that names only one leaves the other undefended.

02

What we collect

Business contact details, programme metadata, and diagnostic responses. Responses are captured by programme, stratum and function. Individual respondents are not identified in any output and a diagnostic may be administered anonymously.

03

What we exclude

Protected health information, patient-identifiable data, regulated clinical data and sensitive personal data are excluded by default. The exclusion is acknowledged before submission, not stated afterwards.

04

Buyer records and delivered files

Where a publication is purchased, the storefront processes the transaction as merchant of record. Buyer identity is stamped into the delivered file as an anti-piracy measure. You are told this before purchase, on the checkout, not on the download.

05

Subprocessors

A register of every vendor that processes, transmits or stores client data is maintained inside the platform. The published list is generated from that register and never maintained separately, so the two cannot drift apart. It is published at aichangeloop.com/subprocessors.

06

Retention

Portal authentication is removed 90 days after a recorded engagement close. Programme records are retained four years from close, matched to the limitation period for a contractual claim rather than a tax standard.

07

Deletion

Approved deletion requests are targeted for completion within 30 days, subject to named retention exceptions. Requests, authority validation, scope, exceptions and completion are logged.

08

Benchmark consent

Benchmark participation is captured separately from service consent and separately again from marketing consent, so the three are never bundled. A client who declines is excluded from benchmark calculations.

09

AI and your data

Client data is never used to train a public model. The interpretation layer writes interpretation only; every figure is computed by the scoring engine. The public assistant has no access to any programme record.

10

Your rights

Access, correction, deletion and objection, exercised through the contact route on this page.

This page is the wireframe representation. The paste-ready text lives in the corrected Privacy Policy reference and its 29 August extension. Nothing here is published until the five open rulings are settled.

Questions before you start

Ask anything about data handling, scoping or the record format.

Start a conversation
OR READ THE THINKING

Loop Insights

Framework implementation, the Orien case work, and the questions worth putting to a steering committee. Published openly.

Read the insights