Data and security
It stays yours. Here is exactly how.
This is the first question any serious organization asks, and it deserves a specific answer rather than a reassuring one. This page is written to be forwarded to whoever in your organization is responsible for risk.
What we commit to.
These terms are the same for every engagement and are written into the proposal.
- The machine sits inside your building, on your network, under your controlFor on-premise deployments, the hardware is physically in your facility and administered under your policies.
- Your data, documents and everything built from them belong to youIncluding the model, its configuration, the indexes built from your documents, and the outputs. There is no license back to us.
- For on-premise work, the build happens on your hardware or through access you control and can revokeWe do not copy your document store to our systems to work on it. Access is granted by you, logged by you, and ends when you say so.
- For cloud work, data passes only through enterprise services that do not train on customer dataBusiness-grade agreements with written terms, named in the proposal, so IT can review them before anything is connected.
- Access is limited to the people doing the work, protected by two-factor authentication, and removed at handoffNamed individuals, not a shared account. At acceptance, our access is removed and you confirm it.
- You own every credential and every accountEvery account created during the engagement is created in your name, on your domain, with you as the administrator.
- Data is encrypted at rest and in transitOn the machine, in backups, and on every connection between systems.
- We complete any vendor security questionnaire as part of procurementBefore contract, not after, and in full.
Where the data lives, by deployment.
The assessment recommends one of these in writing, with the reasoning. Regulated or proprietary information goes on hardware you control.
| Consideration | On hardware you own | In your own cloud tenant | Inside the systems you already run |
|---|---|---|---|
| Where data lives | Your building, your network | Your account with an enterprise provider, under your agreement | Your existing systems. Nothing moves |
| Who can see it | Only you, and named individuals during the build through access you revoke | You, and us only to support it, under your access controls | You and anyone you already authorized |
| Model training | Nothing leaves. No outside model sees your data | Enterprise services that do not train on customer data, named in the proposal | Same, where a model is used at all |
| Internet required | Optional | Yes | Yes |
| Right for | Regulated data, proprietary data, public records, anything that cannot leave | Multi-site reporting and workflows where the data is already in the cloud | Automation inside an ERP, case system or document store |
| At the end | It never left | Your tenant. You revoke our access | Nothing changes |
The hardware, specifically.
For the IT director who wants to know what is going in the rack.
Single office or department
A compact dedicated server running headless on your network, with battery backup and encrypted backups. Administered like any other server you own. Specification provided in writing before purchase.
Larger deployments
GPU servers from established vendors, sized to your user count and the models required. Rack-mounted in your facility or your colocation, on your network segment, under your monitoring.
Network and identity
The machine follows your network policy and your firewall rules. Users authenticate through your existing identity provider where one exists. Nothing calls out to the open internet unless you decide it should. Updates are scheduled with you, documented, and reversible.
Backups
Encrypted, on a schedule you approve, to a destination you control. Restore is tested at acceptance.
End of a hardware agreement
Renew, purchase outright, or have your data transferred to you and the machine securely wiped before it is returned. You choose. Documentation of the wipe is provided.
Regulated work.
Healthcare, legal, municipal and defense-adjacent organizations each carry specific obligations, and those obligations follow the data, not the tool. We do not start regulated data work until the agreements that govern it are in place, such as a business associate agreement in healthcare, and until the recommended architecture satisfies them. For most regulated work that means hardware you control.
We do not claim certifications we do not hold. What we will do is answer every question on your security questionnaire specifically, show you where every record lives, and put the commitments above in the contract.
Who can see what, including us.
During the build, named people on our team through access you grant. At handoff, that access is removed and you confirm it. During ongoing support, access is granted per incident, through you, and logged. We never hold a standing credential to your systems that you did not issue and cannot revoke.
If we stop working together.
Everything is yours and stays where it is. The documentation delivered at acceptance is written so your own IT team or another provider can administer the system without us.
We will tell you in plain language where every record lives and who can see it. If we cannot answer that clearly, we have not built it right.