Data security

Your improvement evidence, protected and provable

Improvement projects hold your cost data, your defect rates and your process weaknesses. This page sets out exactly what protects them, and is honest about which controls are ours and which we inherit.

Controls we operate

These are built into Ci Flow. You can see each one working in the product.

Row-level access, enforced at the data layer

A project is readable only by the person who created it or someone named on its member list. It is editable only by the creator or someone on its editor list, and deletable only by the creator. These rules live with the data, not in the interface, so they hold even if a request bypasses the screen that should have stopped it.

Read access and write access are granted separately

Adding a stakeholder so they can follow a project does not give them the ability to change its evidence. Membership and editing are two different lists, which means a sponsor can watch a tollgate build without being able to alter the numbers behind it.

Audit trails on company changes and AI usage

Company-level changes are recorded against the person who made them. Every AI interpretation is logged with the user, the action and the amount consumed, so an organisation can see exactly who ran what and when.

One controlled path for every AI call

Every AI request in the product passes through a single internal wrapper. That wrapper applies your administrator's chosen model, enforces the monthly allowance for the user, records the usage and cleans the response before anything is stored or displayed. There is no second route around it.

The AI cannot change a number

Statistics are produced by a deterministic engine validated against NumPy and SciPy. The model receives the finished calculation as a source of truth it is not permitted to alter, and only writes the explanation. Run the same worksheet three times and the figures are identical to nine decimal places. Forty-seven automated test suites run on every release to keep it that way.

Your improvement data is yours

Project evidence, worksheets, process maps and tollgate records belong to your organisation. We do not sell customer data, and we do not use your project content to train public models.

Controls we inherit

Ci Flow is built on an enterprise cloud application platform. These controls are operated and certified by that provider, not by us, and we say so rather than borrowing the badge.

Independently audited platform

Ci Flow runs on a cloud application platform whose security controls are covered by an independent SOC 2 Type II audit and an ISO/IEC 27001 certified information security management system. Those certifications are held by the platform provider.

Encryption in transit and at rest

The platform encrypts data in transit with TLS 1.2 or higher, and data and backups at rest with AES-256.

Key and secret management

Application secrets and API credentials are isolated in managed key infrastructure rather than held in application code.

Monitoring and testing

The platform operates 24/7 security monitoring, runs internal and third-party penetration testing against OWASP methodology, and maintains a bug bounty programme for independent researchers.

Privacy framework

The platform supports GDPR obligations including a Data Processing Agreement on request, along with user deletion workflows. We can pass a DPA request through to the provider on your behalf.

Payments

Subscription payments are handled by PCI DSS certified payment processors. Ci Flow never stores your card details.

Straight answers

Is Ci Flow itself SOC 2 or ISO 27001 certified?: No, and we will not imply otherwise. Ci Flow holds no security certification in its own name. The platform we are built on holds SOC 2 Type II and ISO/IEC 27001, and Ci Flow inherits those controls. We think telling you that plainly is worth more than a badge you cannot verify.
Where is our data stored?: Your data is held in the cloud infrastructure operated by our platform provider. If your procurement process needs a specific region or a written statement on data residency, contact us and we will get you the detail in writing before you commit.
Can we get a Data Processing Agreement?: Yes. A DPA is available through our platform provider and we will arrange it. Ask through the contact page and tell us which entity needs to sign.
Does our project data train AI models?: No. Your project content is used to produce interpretations for you. It is not used to train public models and it is not sold.
What happens if we leave?: Your work is exportable while your account is active. Tollgate sessions export to PowerPoint, tool outputs export individually, and project data can be extracted before you close the account. Export before you cancel.
Who can see a project inside our company?: Only the person who created it and the people they name. Access is not company-wide by default. An administrator does not automatically read every project.

Need this in writing for procurement?

Send us the security questionnaire. We will answer it accurately, including the questions where the answer is no.