Sweeping for the last readable corners.
Neeos seals the things you write so our servers can't read them. This week I went looking for what we'd missed.
Most of what you put in Neeos is sealed on your phone before it reaches us, so the server stores something it can't read. It's easy to say. It's much harder to be sure that every last place follows the rule. Over September 11th to 13th, I went looking for the places that didn't.
What turned up
- The titles of document conversations were being saved readable. They're now sealed first.
- Attachment filenames were not yet sealed. They are now.
- The text of an answer that failed could end up stored in a readable place, even though the successful version wouldn't. It's now kept out.
- A search index file was accepted by the server in a form it shouldn't have been. The server now refuses anything that isn't properly sealed.
Why this is a sweep, not a feature
None of these were dramatic. Each was a small spot where good intentions hadn't been carried all the way. But “nearly everything is sealed” is a very different statement from “everything is sealed”, and the gap between them is exactly where a promise falls apart.
I'll keep describing this honestly: some metadata still has to be readable for the app to function, and our architecture page keeps the exact list of what is and isn't sealed.
Written October 21, 2026 from the build log, and dated to when this happened.