Pawste · Security
How Pawste keeps pastes private
What's locked, what our server keeps, and what we can't see, in plain words.
The short version
- Private links (the default) are encrypted on your device. GmCat stores only scrambled text and can't read it.
- Short links are not encrypted. Pawste says so wherever they appear. Use them for code and notes, not secrets.
- Short link + password is encrypted with your password, so GmCat can't read it, but a weak password could be guessed.
- No ads, no account, no tracking on paste pages, and no IP addresses saved.
How a private link works
- Your browser makes a random 256-bit key and locks the paste with AES-256-GCM using the browser's built-in Web Crypto.
- Only the locked text goes to our server. The key goes into the link after “#”, like
paw.gmcat.io/k7m2x9pqrt#pNfV…. - Browsers never send the part after “#” to a server, so we never see the key. The reader's browser uses it to unlock the paste.
With a password as well, the key becomes a mix of the link key and your password (stretched with PBKDF2, 310,000 rounds), so the link alone isn't enough.
Short links
A short link (paw.gmcat.io/k7m2x9pq) has no room for a key, so the text is stored as it is. That means GmCat could read it, and anyone with the link can. Add a password and the paste is locked with a key made from the password alone (PBKDF2, 600,000 rounds). Pick a long password: someone with the scrambled text could try to guess a short one.
What our server keeps
- The locked (or, for short links, plain) text and its earlier versions, until the paste expires or is deleted.
- When it was made and when it expires, whether it burns after reading or has a password, and a scrambled fingerprint of the edit token.
- Not your IP address. To stop abuse we keep a short-lived, salted fingerprint in memory only, and it's gone when the service restarts.
Leak Guard
Before you share, Leak Guard checks your text on your device for things like passwords, API keys, tokens, private keys, card numbers and recovery phrases, and offers to hide them. In the web editor nothing is sent to check. On the command line the check runs on our server, because that text is sent unencrypted anyway.
Burn after reading and link previews
Chat apps fetch a link to show a preview. That only loads the page, never the paste. A burn-after-reading paste is handed over, and deleted, only when a person presses “Open it now”.
Reports
Anyone can report a paste. A reporter can choose to include the key so GmCat can read it and decide. After reports from three different people a paste is hidden until it's reviewed.
Limits, honestly
- Anyone who gets the full link can read a private paste. Share links the way you'd share the secret itself.
- Like every web app, you trust the page code we send to your browser. You can read it yourself: the locking happens in pawste-core.js.
- Encryption can't protect a device that's already compromised.
Good to know
Which encryption does Pawste use?
AES-256-GCM from the browser's Web Crypto, with a random 256-bit key per paste. Passwords are stretched with PBKDF2-SHA-256 (310,000 rounds on private links, 600,000 on short links).
Can GmCat recover a lost private link?
No. We never have the key, so nobody can open the paste without the full link.
Do you sell data or show ads?
No ads, no selling, no account, and no tracking on paste pages.
More from Pawste
New paste
Share text or code with a private or short link.
Secure note
Send a password or secret that deletes itself after one read.
Code to image
Turn code into a clean picture for posts and slides.
Command line
Share files and command output with curl.
Pawste vs Pastebin
An honest comparison with other paste sites.