Encrypted before it leaves the keyboard.
Every keystroke is wrapped on your device. The server stores opaque ciphertext keyed to a vault only you can open. There is no read-side for us to misuse.
A bench for everything you've started. Tasks in flight, notes still in the thinking, this morning's scratch — sealed in your browser before any of it leaves. We host the ciphertext. You hold the key.
A local MCP server hands your sealed vault to Claude, Cursor, or anything that speaks the protocol. The process holds your identity keys in RAM and seals every byte before it hits the cloud.
Start a task. Pick it back up. The bench remembers what you touched last — and quietly nudges you to wrap a few up when the loops pile up.
Every keystroke is wrapped on your device. The server stores opaque ciphertext keyed to a vault only you can open. There is no read-side for us to misuse.
Quick-add parses dates, priorities, and projects from natural language. “Email Sam tomorrow 3pm p1 #inbox” lands where it belongs, with the date you meant.
npx @paperjot/mcp pairs your laptop in two minutes. Claude Desktop, Claude Code, Cursor — point any of them at the bench and they read your loops as markdown files. Paperjot’s servers see nothing change.
Sixteen features, set in type. Every one runs on the same end-to-end encrypted vault.
Notes, queries, and threads — set in the same press, sealed under the same lock.
Begin where the page is empty.
Pulled this onto today — sealed before send.
Confirmed. Shipping by Friday.
We can't read your work. Neither can our hosting provider, our employees, or anyone with a subpoena. The math, not the policy, is what makes that true.
— How Paperjot is built · libsodium · X25519 · XChaCha20‑Poly1305