Legal03 / 03
A plain-language explanation of the single preference currently stored by this website and how to change it.
- Effective date
- 3 September 2026
01What the site currently stores
The current website stores one consent preference in your browser's localStorage. The key is common-intelligence-consent-v1 and its value records either Accept all or Essential only.
02Why it is stored
The preference prevents the consent pill from asking for the same choice on every visit. LocalStorage is browser storage rather than a traditional cookie, but it is described here because it serves the same preference-management purpose.
03Optional technologies
No optional analytics or advertising technology is currently enabled. If one is introduced, this policy and the consent behaviour will be updated before it is enabled.
04Change your choice
Use Manage cookie settings below to reopen the existing consent pill. You can also clear site data in your browser, which removes the stored preference and causes the pill to ask again after you scroll beyond the opening view.
Other legal documents
Frequently asked
Our work starts from the people already responsible for the operation. The aim is to remove repetitive search, comparison and drafting, while making their judgment easier to apply and keeping accountable decisions with named human owners.
They help map the real process, choose the difficult cases, test early versions and define where review or refusal is required. An internal group learns to operate and improve the system before handover.
One senior sponsor, access to the people and systems involved, and agreement on the business measure before building begins. Leadership also protects time for operators to participate, because their knowledge is part of the system.
It should be frequent, expensive, evidence-heavy and close to a measure the company already trusts. The two-week diagnostic compares candidate workflows and tests the strongest one on real company data.
That is why it is tested on real exceptions before production. Corrections become part of the evaluation set, and the system is designed to ask for review when evidence is weak rather than appearing certain.
We build in the client environment wherever possible, use the minimum permissions each action needs, and make activity auditable. Data boundaries, retention, human review and prohibited actions are agreed before a production release.
The engagement is designed to reduce that dependency. The client receives the source, prompts, evaluation cases, runbooks and controls, and proves the handover by running the next cycle with its own team.
We establish the current cost and operating baseline together, then review the same measure after each release. If the workflow does not produce a credible financial or operating improvement, we do not expand it.