Writer privacy and security
Your script is encrypted in your browser before it syncs or reaches a co-writer. We never hold the key, so we can’t read your work.
How encryption works
- Your browser makes the key when you turn on encrypted sync or start a co-writing room.
- Every script and room edit is encrypted (AES-256) in your browser before anything is sent. A room key lives after the # in the invite link, which browsers never send to a server.
- Our servers store and relay encrypted data only. We never receive your passphrase, recovery key or room keys.
What leaves your device
| Action | What is sent |
|---|---|
| Writing solo | Nothing |
| Canvas & ink | Nothing. Canvas & ink settings, saved looks and desk photos stay in your browser. |
| Encrypted sync | Encrypted data only |
| Co-writing rooms | Encrypted edits and chat between room members |
| Timestamped Draft Certificate | A fingerprint (SHA-256 hash) of the script, plus the title and author name you enter. We pass only the fingerprint to an independent RFC 3161 timestamp service (FreeTSA, with DigiCert as backup). The script itself never leaves your device. |
| Education verification (manual review only) | Enrollment documents (manual review only): stored privately, seen only by BlockReel admins, deleted after review. Schools and teachers never see your scripts. |
| Script Lab submission | Your script, readable, to BlockReel. Human readers need to read it, so Lab submissions are not encrypted like the rows above. See the Script Lab rules for how it is stored and who sees it. |
Honest limits
- Encryption protects data on our servers. It cannot protect a device someone else has unlocked.
- We can see who is in a room, when, and from which IP address, but not what you write.
No analytics or tracking scripts run in the editor.
Report a security issue: [email protected]