DEV Community

Cover image for Your grammar checker uploads every word you type. I built one that never leaves your Mac.

Your grammar checker uploads every word you type. I built one that never leaves your Mac.

Rudratosh Shastri on October 19, 2026

Open the network tab while you use most AI writing tools. Watch what happens as you type an email, a performance review, a message to your lawyer, ...
Collapse
 
omyvnss profile image
Om Yaduvanshi •

the 'touched the internet twice' line is doing a lot of work, and i mean that as a compliment. most privacy pitches collapse on the exact things they quietly exclude. one small crack in the story though: the license check sends the mac's name. that is not your writing, so the rule technically holds, but it is one identifying string crossing the wire. worth naming in the architecture section before someone else names it for you.

Collapse
 
rudratosh profile image
Rudratosh Shastri •

the license check sends the mac's name... one identifying string crossing the wire

Fair, and you're right to make me name it before someone else does. It's not your writing — but it is one identifying string, once, at activation, and "touched the internet twice" should say what crossed, not just how often. Adding it to the architecture section explicitly: device name at license check, nothing after. Precision is the whole pitch; hand-waving the one exception undercuts it.

Collapse
 
omyvnss profile image
Om Yaduvanshi •

precision being the whole pitch is a good way to put it. i'd say the license ping matters less for how often it fires and more because it's the one moment where the "your words never leave" story has an exception. that's exactly the line worth naming plainly, good call.

Thread Thread
 
rudratosh profile image
Rudratosh Shastri •

the one moment where the "your words never leave" story has an exception

Exactly — which is why it has to be named plainly, not buried. The frequency is almost irrelevant; it's that there is an exception at all when the whole pitch is "no exceptions." The honest version states it as a boundary: device name at license check, once, and never a word of your text — so the reader audits the exception instead of discovering it later. A privacy claim is only as strong as the thing it admits.

Thread Thread
 
omyvnss profile image
Om Yaduvanshi •

fair. and the bar in that last line is brutal, which is the point. most tools name the exception only after someone finds it. naming it yourself is what makes the rest of the claim hold.

Thread Thread
 
rudratosh profile image
Rudratosh Shastri •

naming it yourself is what makes the rest of the claim hold

Exactly that. The exception you disclose is credibility; the one someone finds for you is a retraction. Same fact, opposite outcome — and the only difference is who said it first.

Collapse
 
sujalkhatri profile image
Sujal Khatri •

The one-rule constraint is what makes this land. "No text leaves the device. Ever." is a principle you can actually test — and "snippets don't touch the model at all" is the perfect example of the discipline it takes. Keeping the deterministic feature deterministic is a detail only someone who honored the constraint would write.

Worth saying: this philosophy extends past AI. Plenty of everyday text chores — deduping a list, converting case, checking word frequency, generating a slug — also get routed to cloud sites when they could run entirely client-side. I ended up building a free set of small text tools for exactly that reason: BulkTextKit. Everything runs in the browser, no uploads, no account. Different problem space from BriskType (no AI involved), same belief that your words shouldn't have to travel anywhere to be processed.

One-time $39 is also the right call. A tool that needs you to keep paying keeps needing you — and needing your data. That tension is worth naming.

Collapse
 
rudratosh profile image
Rudratosh Shastri •

Keeping the deterministic feature deterministic is a detail only someone who honored the constraint would write.

The line I most wanted someone to catch — thank you. And yes, "does this actually need a server?" extends way past AI; most text chores are embarrassingly client-side. Good to see BulkTextKit taking the same stance in the no-AI space. Agreed on one-time pricing too: a tool that needs you to keep paying keeps needing your data — worth naming out loud.

Collapse
 
vardum profile image
Vardum (formerly VEIL) •

Two small models instead of one bigger one is interesting. Was that for speed, or was one model bad at doing both jobs? Mail is the app I'd want it in first.

Collapse
 
rudratosh profile image
Rudratosh Shastri •

Two small models instead of one bigger one — speed, or was one bad at both?

Mostly the RAM budget, then speed. The "Faster" model keeps autocomplete under a keystroke's latency on an 8GB Air where one bigger model would swap; the "Higher quality" one does better rewrites if you can spare the memory. Not one-bad-at-both so much as one-size-doesn't-fit-both-machines — you pick per device. And agreed, Mail's the first app most people want it in; it's supported out of the box (the browser/Slack-type apps are what's still in beta).

Collapse
 
vardum profile image
Vardum (formerly VEIL) •

That makes sense. Picking the model per machine is smarter than one size for everyone, and 8 GB Airs are everywhere. Good to hear Mail already works.

Thread Thread
 
rudratosh profile image
Rudratosh Shastri •

Picking the model per machine is smarter than one size for everyone, and 8 GB Airs are everywhere.

Exactly the constraint that drove it — the floor hardware sets the default, not the top. Appreciate you reading it.

Collapse
 
arcwrightai profile image
arcwrightai •

Local-first is the right call for anything that touches your writing. Privacy shouldn't be a premium feature.

Collapse
 
rudratosh profile image
Rudratosh Shastri •

now a days, privacy is GOLD