“This sentence matters.”
Encrypt locallyThe server helps
things arrive.
It does not read them.
Pro Preview: shared workspace content is designed to be encrypted before it reaches the relay. Connection metadata remains visible, and an external security audit has not yet been completed.
Encrypted payload
7f9a21c48b73e05dWorkspace routing
7f9a21c48b73e05dNo readable annotationEncrypted payload
7f9a21c48b73e05d“This sentence matters.”
What the relay sees.
Encryption protects annotation content, not every piece of connection metadata.
Readable to the relay
- That a workspace exists
- Workspace scope and room routing
- Connection timing, volume, and IP address
Not readable to the relay
- Notes and highlighted text
- Drawn annotation content
- Workspace keys and decrypted payloads
The key stays with you.
Workspace keys remain in the browser profile or in a password-protected encrypted backup you create. This backs up keys, not all annotations. Personal notes are not claimed to be encrypted at rest.
Lose both, lose access.
If the original key access and recovery material are both lost, Quillcrypt cannot decrypt the workspace for you.
7f9a21c48b73e05d... inaccessible without the keyA careful boundary.
Designed to protect against
The relay or its persisted storage reading annotation contents.
Outside this protection
A compromised device, an unlocked browser session, a collaborator copying content, or the public webpage itself.
Useful questions.
Can Quillcrypt recover my workspace key?
No. Export an encrypted key backup and store it like a password.
Does the relay store updates?
It can persist opaque encrypted update history so an offline client can catch up. That storage still contains metadata and must be protected operationally.
Has Quillcrypt had an external security audit?
Not yet. The repository contains an audit scope, but internal automated verification is not an independent audit.
Keep the key to yourself.
See how it works ↗