Company
Changelog
A dated record of what changed and why — weighted towards security and privacy decisions, because those are the ones that affect whether you should trust this service.
We keep this page because a security product that changes silently is a security product you cannot evaluate. If we alter a cryptographic parameter, change what we store, or revise a documented guarantee, it is recorded here with a date.
This log starts from the point we began publishing it. It is not a reconstruction of earlier history — we would rather have a short honest record than a long invented one.
- Privacy
Advertising removed from note and share pages
The advertising script previously loaded on every page, including the note editor and shared-note screens. It is now loaded only on editorial content pages — the blog, feature pages, guides and reference material. Note editing and shared-note viewing are a tool and a password gate, not places to serve advertising. - Security
Note and share URLs excluded from indexing
Note URLs and share links now carry anoindex, nofollowdirective at the HTTP header level, and share paths are disallowed inrobots.txt. Previously a blanketindex, followheader applied site-wide, which invited crawlers to enumerate an unbounded space of note addresses. - Documentation
Security architecture and threat model published
Full technical documentation of the encryption design is now public, including exact algorithms and parameters, a field-level description of what the server stores, and an explicit threat model listing the adversaries this design does not defend against. Both pages are written against the shipping code and carry a review date. - Documentation
Editorial policy and responsible disclosure published
Our editorial policy now documents sourcing standards, the technical review process, correction handling and review cadence. A responsible disclosure policy sets out how to report a vulnerability and the response times we commit to.
Open trade-offs
Things we know are imperfect and are actively weighing. Listing them publicly keeps us honest, and lets you judge whether any of them matter for your situation.
- PBKDF2 rather than Argon2id. Argon2id is memory-hard and resists GPU attacks better. PBKDF2 is the only password-based KDF the Web Crypto API exposes natively across all browsers we support. Discussed in full on the security architecture page.
- No independent audit. The design is documented so it can be evaluated, but no third party has reviewed the implementation. We state this rather than let its absence be inferred.
- Browser-delivered cryptography. We serve the code that performs the encryption, which is the fundamental limitation of all web-based crypto. See the threat model.
- Text only. No file or image support today.
Suggesting a change
Write your first encrypted note
No account, no email address, no download. Type a note, set a password, and share the link.
Open the notepad