Security, in plain terms.
Valtou Canvas is built so that we never receive or store your notes. This page explains exactly how — the algorithms, what a share link contains, what we defend against, and where the limits are.
Summary
- Notes are stored only in your browser. There is no account and no server-side copy.
- Share links are end-to-end encrypted in your browser and the encrypted note lives in the link’s fragment, which is never sent to any server.
- The site is static files with a strict Content-Security-Policy and no third-party scripts.
Algorithms
- Cipher
AES-256-GCM (Web Crypto API)Authenticated encryption: any change to the link is detected.- Nonce
96-bit random IV, fresh per linkNever reused; generated with crypto.getRandomValues.- Link key
256-bit random keyUsed in “link is the key” mode; travels in the fragment.- Password KDF
PBKDF2-SHA256, 600,000 iterations, 128-bit random saltMatches OWASP’s 2023 guidance for PBKDF2-SHA256.- Compression
deflate-raw (CompressionStream)Applied before encryption to keep links short.- Encoding
base64url, canonical onlyURL-safe; non-canonical encodings are rejected.
All cryptography uses the browser’s built-in Web Crypto API. We do not ship our own implementations of AES or PBKDF2, and we do not use third-party crypto libraries.
What a share link contains
Everything after # is the payload. It is versioned so the format can evolve:
#v1.k.<key>.<iv ‖ ciphertext ‖ tag> link is the key
#v1.p.<iterations>.<salt>.<iv ‖ ciphertext ‖ tag> password protectedThe header (v1.k, or v1.p.<iterations>.<salt>) is passed to AES-GCM as additional authenticated data. Changing the version, the mode, the iteration count or the salt makes decryption fail, so an attacker cannot downgrade a link to weaker settings. Iteration counts outside a safe range are rejected before any work is done, and decompressed notes are capped at 1 MB.
What never reaches our servers
- The text of any note, local or shared.
- Encryption keys and passwords — they never reach our servers.
- The fragment of a share link (everything after “#”). Browsers do not send it in requests or in the Referer header.
- Who you share with, or how many notes you have.
Threat model
What Canvas protects against
- A breach of our servers or storage
- There is nothing to steal: we serve static files and never receive or store your notes, keys or passwords.
- Network observers
- HTTPS everywhere (HSTS), and the note is never in a request in the first place.
- Tampered links
- GCM authenticates the ciphertext and the header (version, mode, iterations, salt). Any change fails to open.
- Malicious shared content
- Raw HTML in Markdown is not rendered; output is sanitised with DOMPurify; remote images are blocked; links cannot navigate the app.
- Script injection
- A strict Content-Security-Policy allows only our own scripts, by origin and hash. No third-party code runs on the page.
What it cannot protect against
- The code we serve
- Canvas runs code delivered from our site. If our hosting were compromised or we were compelled to change it, modified code could capture what you type before it is encrypted. The app is static and you can inspect every file it loads, but you are trusting that delivery — as with any web app.
- Anyone with the full link
- In “link is the key” mode, the link is the secret. If it is forwarded, screenshotted or synced, whoever has it can read the note. Use a password for anything sensitive.
- Weak passwords
- Passwords must be at least 12 characters. PBKDF2 slows guessing, but a common password can still be guessed offline by someone who has the link. Use several random words.
- A compromised device
- Malware or a malicious browser extension on the sender’s or recipient’s device can read what you can read. Encryption cannot help there.
- Local storage is not encrypted
- Notes saved on your device are protected by your device and browser profile, like any other local file.
- Link history
- We remove the key from the address bar after opening a link, but chat apps, email and browser sync may keep their own copy of the link you pasted.
How the site is served
- Static files on Amazon S3 behind CloudFront; no application server, no database.
Content-Security-Policy:default-src 'self', scripts allowed by origin and exact hash only, no external connections, framing forbidden.Referrer-Policy: no-referrer, HSTS,X-Content-Type-Options: nosniff, and a Permissions-Policy that turns off camera, microphone, location and more.- No analytics, no tracking pixels, no cookies, no fonts or scripts from other domains.
Check it yourself
- Open your browser’s developer tools and switch to the Network tab.
- Write a note and create a share link. No request carries your text.
- Open the link: the only requests are for the app’s own files, and none include anything after the
#.
Found a problem? Please tell us at valtou.com so we can fix it.