The AI that “runs locally” doesn’t run locally
─────────────────
It happens every day, in hundreds of firms. You open a case file, ask for a summary, get a draft in thirty seconds. The document never left your desk: you can see it, it’s right there. Nobody sent it anywhere.
Except that’s not what happened. And if you answer for your clients’ confidentiality, the difference is not a technical detail. It’s everything.
"Local" describes where the file is read, not where it is processed
The new desktop AI assistants arrive with a reassuring promise: they work on the files on your computer, locally. The word is chosen with care, because it is exactly what a professional wants to hear.
But how they work is documented by the vendors themselves. The agent reads the files from the folder you point it to — that part does happen on your machine. Then, to produce an answer, the content of those files is sent to an execution environment on the vendor’s servers, where the model runs. What stays local is your chat history. Not the processing of your documents.
This is not an accusation: it is their official documentation. The problem is that “local” means something else in everyday language, and nobody has an interest in clearing that up.
The journey of a "local" document
1. You select the folder. The agent reads the firm’s files from your disk. So far, everything is genuinely local.
2. The content leaves. To process your request, the text of the documents is transmitted to the vendor’s infrastructure.
3. The answer comes back. Within seconds. But the content of the case has already crossed the Atlantic.
The file on your desk never moved. Its content did.
Jurisdiction matters more than geography
The natural next question: what if the servers were in Europe?
Not enough. The US CLOUD Act allows American authorities to obtain from a US provider the data that provider controls, regardless of where it is physically stored. A European data centre operated by an American company remains under American jurisdiction.
For a court brief, a balance sheet or a tax file, the decisive question is not where the data sits, but who answers for it.
This is not theory: it has already happened
February 2026. A federal judge in New York ruled that 31 documents generated with the consumer version of a well-known AI assistant were not covered by attorney-client privilege: the service’s terms of use allowed data to be shared with third parties.
Convenient, fast — and admissible against you in court.
That precedent is what makes everything else concrete: this is not a theoretical compliance risk, but a protection that failed in a courtroom.
What Swiss law requires
Confidentiality cannot be delegated. For lawyers, Art. 321 of the Swiss Criminal Code speaks, and it applies to you, not to whoever wrote the application. For fiduciaries and accountants, the duty of care and loyalty of Art. 398 of the Code of Obligations applies, together with the revised Swiss Data Protection Act (nFADP), which requires you to know where processing takes place and to have a contract governing it.
The substance does not change: sending client records to a foreign service without adequate contractual safeguards exposes the firm. Not the vendor. The firm.
The four questions to ask any provider
They apply to us as much as to anyone else. There are four, and they take two minutes to answer — if the answers exist.
- Where is the document processed, not just where is it stored?
- Under which jurisdiction does the party processing it operate?
- Who signs the data processing agreement with the firm under the nFADP?
- How do you verify what was done, and by whom?
If the answer to all four is “don’t worry, it runs locally”, you now know what to reply.
The alternative is not giving up on AI
That would be the wrong conclusion, and not even a practical one: the advantage of working with these tools is real, and whoever gives it up hands it to their competitors.
The choice is not between intelligence and professional secrecy. It is between vendors who answer those four questions and vendors who hope nobody asks them.
ZeroEdge AI is our answer: processing and storage on Swiss infrastructure, separate encryption for every client, sources cited on every statement, an access log, and a data processing agreement signed by a company based in Chiasso. The question “where did my documents end up?” has one answer, written into the contract: in Switzerland. Always.
The service, in detail, at ai.zeroedge.ch.
Bring a case file. Watch where it goes.
Thirty minutes, at your office, on your real documents: what the AI answers, how it cites its sources, and where it works — with the contract that guarantees it.
Without a single piece of data leaving Switzerland.
We are starting with the clients we can serve best today: fiduciary and accounting firms — the first demonstrations and the pilot programme are open now. Are you a lawyer? The legal vertical is in the works: write to us and we will let you know when it opens.
Book a demonstration → · sales@zeroedge.ch
ZeroEdge AI is built and supported by Inn-Tech SAGL, Via Maestri Comacini 8, 6830 Chiasso, Switzerland. Sovereign AI, made in Switzerland.
Cover image generated with AI.
