Where your data lives, and what happens to it
This page exists so your IT provider can assess us without sitting through a sales call.
What we commit to
The specifics are contracted, not advertised.
Your deployment boundary, the data flow and the technical controls that apply to it are documented for your environment during the audit, and contracted before any build starts. We’d rather be held to a document you’ve read than to a paragraph on a website.
Your data does not train anyone’s model.
Not ours, not a third party’s. It’s in the contract.
Access mirrors the permissions you already have.
If someone can’t open a file today, the co-pilot won’t surface it to them tomorrow.
Everything it does is recorded.
Every retrieval, generation and action goes to an append-only, signed log: who asked, what was retrieved, what was produced, who approved it, when. Exportable, and yours.
You keep the asset, and we destroy our copies.
Your prepared corpus, configuration and audit log are yours. On termination they’re returned and our copies destroyed within 30 days, confirmed in writing.
Nothing leaves your environment to be assessed.
Including during the audit.
What we won’t claim
We’re not going to list certifications we don’t hold or imply an accreditation we’re mid-way through. Ask us directly what we have and what we’re working towards and you’ll get a straight answer on a call. What we will do is put the deployment architecture, the data flow and the controls in writing during the audit, so your IT provider can assess the actual system rather than a logo wall.
We also won’t publish a control matrix on a marketing page. Encryption, identity integration, retention periods, log formats and deployment topology are stated for your deployment in the audit document, where they’re specific enough for your IT provider to check and binding enough to be worth checking. A list here would be less precise and commit us to less.
What we need from you to assess us
Read access to the relevant document stores, one technical contact who knows how those systems are actually wired, and a signed confidentiality agreement. We work under yours rather than ours if you prefer, and most firms do.
Nothing is copied out of your environment to be assessed. The audit reads what is already there, and the deployment architecture is written before any of it moves.
The risk we think you should actually worry about
It usually isn’t a breach of the AI system. It’s the confidential document a well-meaning senior person pasted into a free public tool last Thursday because they were under deadline and it was the fastest thing available.
You can’t police that with a policy memo. You displace it by giving people something better that happens to be safe.
Send us your questionnaire
If you have a vendor security assessment, send it before the first call rather than after. We’d rather answer forty questions up front than discover a blocker in week three. If something in it disqualifies us, we’ll tell you on the phone.
Book a technical callBring your IT provider or your MSP. The call is for them, not for you, and we don’t need you on it.