I totally agree about the "burn after reading" feature or about "Burn after X secs". Before sending the content: 1) The paste text is encrypted using aes-256-

I totally agree about the "burn after reading" feature or about "Burn after X secs". Before sending the content: 1) The paste text is encrypted using aes-256-cbc algorithm. 2) A secure random token (a simple ID) is generated. 3) The secure random secret key is generated. 4) The url will be http://yaap.it/paste/<ID>#<secret_key&#62 http://yaap.it/paste/<ID>#<secret_key> 5) The encrypted content and the ID is sent to the server. The anchor (the secret key) is never sent ! 6) When you give the url to someone, the ID and the secret key is still in the url. So the content can be decrypted (client-side too) thanks to this information. To shorten the paste url, you can use an external service. BUT, the external service will have the secret key. It depends on what you want. Maybe an idea ?