What we do with your data, your code, and your leverage.

We hold neither. A firm of this size claiming an audited certification it has not completed is the fastest way to fail a security review, so: not yet. What we can give you is the written controls on this page and a straight answer to any questionnaire.

We minimise by default. The teardown transmits nothing at all, we do not de-anonymise visitors by IP, and analytics are cookieless — which is also why there is no cookie banner on this site.

Both are required before we run a post-paid pilot or sell a layer-two assessment — that is our own gate, not a regulator’s. If you are evaluating us, ask for the certificates. A firm that cannot produce them should not be holding your data.

A real DPA, not a template with our name substituted in, lands before the first enterprise conversation. Ask for the current draft if you need to review it sooner.

Not published yet, because where this site and our pilot environments run is still an open decision — and we would rather answer it once, properly, than list a provider we then move off. You will be told before a subprocessor changes, and the list is published with that decision.

A mutual NDA before you send anything

Signed first, not alongside. If we have not signed, do not send us an invoice export.

One named recipient

A single person receives and works on your data, named in the NDA before it is shared. Not a team inbox, not a shared drive with the door left open.

Raw exports deleted within 30 days of delivery

Your invoices, expense reports and app inventories are destroyed once the plan is delivered. Only the derived plan is retained.

Used for your plan and nothing else

Not for benchmarking, not for training anything, not to inform a pitch to anyone else. It produces your plan and then it is gone.

Documented environment isolation, per client

One client per environment, documented rather than assumed.

Encrypted at rest and in transit

Unremarkable, and worth stating plainly rather than implying.

No production credentials in our systems

Test data wherever the workflow allows it. Where it genuinely does not, scoped credentials with an agreed expiry — never a copy of your production secrets.

A breach-notification commitment

In writing, with a stated timeframe, agreed before the pilot starts rather than drafted during one.

Protection is contractual, never covert

No hidden dependencies, obfuscation, kill switches, time bombs, or undisclosed retained ownership. Every mechanism protecting us is a term you can read before you sign.

Evaluation licence during a pilot; full assignment on payment

You get the running application, not the repository, until you pay. On payment the repository transfers, the IP assigns in full, and we deploy into your cloud. Source is available for inspection under NDA on request.

One protection per pilot, and you choose it

Either it runs on our infrastructure, or it runs in your cloud against a deposit — never both. The client picks which risk to carry.

Your data is never leverage

Under no circumstances is client data withheld, in any dispute, at any stage. Operational data created during a pilot is yours and is exported on payment — or on request if you decline the work.