The NDAs in Your Inbox: Why Client Work Changes the Privacy Math
There's a moment in every consultant's career when they realize the software they type into isn't a personal choice anymore. It happens right after you sign an NDA and start drafting emails about the client's unreleased product, their financials, their strategy, the thing they'll fire you over if it leaks. Suddenly the sentence you're typing isn't your sentence. It's theirs. And the tool you type it into becomes part of your obligation to keep it safe.
I've been on both sides of that equation, as a consultant and as a software maker, and it changes how you should think about writing tools. Let me walk through it.
The sentence is no longer yours
Here's the shift that matters. When you work on client projects, your drafts stop being a record of your own thoughts and start being a record of someone else's secrets. The email about the acquisition, the spec for the product that hasn't launched, the summary of the board meeting, these aren't documents you own. They're documents you're trusted with, and everything you use to produce them inherits that trust.
Most people don't think about their writing tools this way, because most people's drafts are their own. But the moment your income depends on keeping client information confidential, the question changes from "is this tool convenient" to "where do the words I type actually go?" That's a different question, and it has a different answer than the convenience one.
The two ways a tool can handle your words
When you're choosing software to type client work into, you're really choosing between two architectures, and the difference isn't branding, it's where the sentence goes.
- Your draft is sent to a server to be processed
- The vendor's policy decides what happens to it
- An NDA does not bind a server you do not control
- Your draft is processed on your Mac, in the moment
- Nothing travels, so nothing can leak in transit
- Your NDA covers the only machine that sees the words
This is the structural argument I made in the privacy-math post, and it lands differently when client money is on the line. A cloud writing tool isn't evil. It's just a place where your client's sentence exists that isn't covered by your NDA. Some vendors have good policies, some have bad ones, and all of them can change their policies. Your NDA, by contrast, covers the machines you control, and a local tool keeps the sentence on exactly those machines.
The honest limits
I'm not going to pretend local software makes you bulletproof, because that would be the kind of overclaim I built this whole blog to avoid. A local tool doesn't protect you from a compromised Mac, from someone reading over your shoulder, or from you emailing the wrong person. It handles one specific risk: the risk that your client's words travel to a server you don't control and become someone else's data. That's a real risk, and it's the one most consultants never think about, but it's not the only risk.
I also won't pretend WriteAmp has no network use at all, because it does, and I published the full ledger of the three calls it makes. None of them carry your writing. The model downloads once, the update check runs quietly, and the license verifies. The sentences you type, including the client ones, never leave. That's the specific promise, and it's a narrow one, which is why it's true.
What to actually do
If you're a consultant signing NDAs, here's the practical version of this post, and it applies whether or not you ever buy WriteAmp.
That last one is the one I'd put money on. The most common client-confidentiality leak in modern consulting isn't a hacker. It's a consultant pasting a client's financials into a web tool to have them summarized, because it was convenient. Convenience is not a confidentiality strategy.
The close
I built WriteAmp partly because I got tired of the gap between how seriously consultants take client confidentiality and how casually the software they type into handles their words. A tool that finishes your sentences on your Mac is a tool where the NDA you signed is the only policy that applies. That's a small thing to say and a structural thing to build, and it's why the whole product is local.
If you type client work and you're wondering whether your writing tools are part of your confidentiality obligation, the answer is yes, they are. The trial is free for 30 days if you want a tool where the answer to "where do my words go" is "nowhere." The privacy page has the written version, and the settings screen shows you what it learns, because a tool you trust with client work should be one you can inspect.
Sources
- WriteAmp privacy page: the on-device architecture that keeps client work under NDA on your Mac
On macOS 26+ Macs, Apple Intelligence mode stays free even after the trial ends — you always keep a working path to suggestions.
Written by Amit Ashwini, who builds WriteAmp and runs its marketing. More: why the Tab key beats the chat box · mini, midi, and max compared · benchmark methodology.