TRUST

Where your data sits,
and who can see it.

Access is scoped by active assignment. Never by tier, never by seniority.

See the subprocessor register Read the privacy notice
0client data used to train any model

What we do not claim

01

No certification is claimed

No SOC 2, HIPAA, ISO, FedRAMP or GDPR certification is held, and none is asserted. Where a control is designed but not yet operating, we say so rather than describing intent as fact.

02

Encryption at rest is vendor provided

It is a property of the subprocessors in the published register, and it has not been independently verified by us. It is stated here as what it is.

03

The assistant is scope tested, not adversarially tested

Isolation has been tested for scope adherence. Adversarial testing is a condition before the public assistant goes live, and it is named as such rather than assumed.

How access works

Company RoleWhat the organisation has appointed you to do.
Programme RoleWhich programmes you are actively assigned to.
Permission ClassWhat that assignment lets you see and record.
Gate decisionsOnly the Transformation or PMO Lead may record one.
Sector calibrationYou may see your own. The cross sector matrix stays inside the platform.

What Ari will not do

Ari is present across the whole journey. Its limits are published for the same reason the scale is.

No client dataThe public assistant answers from published doctrine only. It has no access to any programme record.
No scoring internalsBase weights, the sector calibration matrix and index formulas are declined by design, and Ari says so rather than guessing.
No advice it is not qualified to giveNo regulated, legal, medical or financial advice, and no pricing quotation.
No silent handling of sensitive dataConfidential or personal information should not be entered. Ari says this before you start, not afterwards.
Logged and reviewedAssistant interactions are reviewed against these limits, and the review cadence is recorded.

The documents behind the claims

Every statement on this page has a document behind it. These are those documents.

SECURITY

Security FAQ

How data is held, transmitted and separated, and what has and has not been independently verified.

Read the FAQ
COOKIES

Cookie notice

What is set, why, and what happens when you decline. Non-essential is off by default.

Read the notice
AI

AI use notice

Where AI is used, what it writes, what it never writes, and what it is never given.

Read the notice
VENDORS

Subprocessor list

Every vendor that processes, transmits or stores client data. Generated from the internal register, never maintained separately.

See the list

Commitments

No training on client data

Your programme data is never used to train a model.

Attribution on every record

Every gate decision carries a name and a date.

Method published

You can check the measurement before you trust the number.

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