There is a category of work where the conversation about AI ends early, and it does not end for the reasons people expect. Not cost. Not capability. Not scepticism about whether the technology is any good.
It ends because the material is not the holder's to share.
Holding something on someone else's behalf
A great deal of valuable material is held rather than owned. Somebody gave it to you for a purpose, and that purpose did not include handing it to a third party so that a machine could read it.
The obligation might come from a contract you signed, a duty attached to the kind of work you do, an undertaking given to a client, or simply a promise made to a person who trusted you. The source varies. The consequence does not: you cannot unilaterally decide that sending it somewhere else is fine, because it was never yours to decide.
This is why the usual reassurances land badly with people in this position. Assurances about retention and encryption are answers to a question they are not asking. Their question is whether the material leaves at all, and the honest answer from any service that reads it on its own computers — including ours — is that it does, because it has to be read somewhere. What differs between services is not that fact; it is the terms.
The quiet compromise most people make
Faced with that, almost everyone does the same thing. They use AI for the material that does not matter, and keep the material that does out of it.
The general correspondence goes in. The client work does not. The marketing copy goes in. The file does not. It is a reasonable compromise and it has an obvious cost: the assistant is helping with the easy part of the job and is excluded from the part where help would actually be worth something.
Over time this produces a quiet cynicism about the whole category — the sense that AI is fine for drafting a newsletter and irrelevant to real work. That conclusion is correct about public AI and wrong about AI. The difference is not a setting, and it is not a promise: it is who holds the material, under what written terms, and what you can demonstrate about it afterwards.
Where our own service stands
We should be plain about our own arrangement. With us, your material does move: into an encrypted space of your own in our private cloud on Amazon Web Services, under a written scope that names what we hold and why, agreed before anything is loaded. Every record in that space is scoped to you. When your assistant reads it, the traffic to its models travels private networking inside the same boundary, not the public internet; the stores that hold it have no public endpoints. Nothing is pooled with anyone else's material, nothing is shared, nothing is used to train anyone else's model — and whatever the assistant does is logged. You can ask for a complete copy at any time, and when the service ends your space and everything in it is deleted, confirmed to you in writing.
That changes the shape of the obligation question without making it vanish. With a public service, you are asking whether the material may sit on a consumer product's computers, under terms you did not write and cannot vary. With us, you are asking whether it may be held by one named party, under written terms you approved first, with a deletion you can point to afterwards. For many obligations that is a different and easier question. For some it is not: if your obligation is that the material may not leave your premises at all, then our service does not meet it today, and we would rather say so here than after you have paid. Dedicated hardware is a door the architecture keeps open — we do not promise a date, and we do not promise it will happen.
The questions worth taking to whoever advises you
If this is your situation, these are the questions that actually decide it. They are worth putting to the person who advises you on such things rather than to a vendor, including us.
- Where is the material permitted to be processed, and by whom?
- Does a machine reading it count as disclosure under the arrangements you are under?
- Who is permitted to hold a copy, and for how long?
- What must you be able to demonstrate afterwards about what happened to it?
- What are you required to tell the person the material concerns?
Notice that none of those is a technical question. They are all questions about your obligations, and the technology is only relevant insofar as it changes the answers.
What we will and will not claim
We will claim this: your material lives in an encrypted space of your own, scoped to you and nobody else, under a written scope you approved before anything was loaded. The traffic between your assistant and its models stays inside our own cloud boundary, on private networking, never the public internet. Nothing is pooled, nothing is shared, nothing is used to train anyone else's model. What happens to it is logged, and when the service ends, deletion is confirmed to you in writing.
We will not claim that this makes you compliant with anything, because compliance is a judgement about your circumstances that we are not in a position to make. Anyone who tells you their product makes you compliant is selling you a conclusion they are not qualified to reach.
Questions to ask before anything sensitive goes in →
Every promise we make, in plain words →
Your own AI. Your own material. One assistant, yours alone.
$9,995 the first year — everything included. $5,995 each year after. The first year costs more because it contains the preparation — your archive prepared and loaded by hand under a written scope, and your assistant built on it — as well as the first year of the service; every year after is the service running.
Or add the Archive Assessment first — $1,950, credited in full
You order and pay at checkout; we write back within days — a decline returns every dollar, and until our letter confirms the year you may withdraw in writing. From that letter the year is final, and it arrives on the date the letter names. Prefer to write to us first?