Redefining encryption

PageProof’s use of encryption in proofing and approval is a world-first. This next generation approach to encryption takes data encryption to a new level.

Encryption explained

We like to explain encryption and decryption by asking people to visualise a shredder, and an un-shredder - if there was such a physical device, something that puts back together perfectly what was previously shredded.

In PageProof, as the owner of a proof, you have a shredder. Your team of proofers have unshredders.

You turn a perfectly readable file into indecipherable content and only those who you’ve asked to proof it will be able to put it back together perfectly. That is encryption and decryption.

Going the extra security mile

You will see when visiting that the site is prefixed with https. Https signals the browser to use an added encryption layer of SSL (secure sockets layer) to protect the traffic when it is travelling to the server.

Rather than just relying on https and encryption performed when a file is received by the server (you might see the term 'at rest' used to describe this), PageProof goes the extra security mile to encrypt your file and its comments in your computer or tablet’s browser before it travels to PageProof’s servers via https (SSL).

To encrypt and decrypt data, we generate a 2048-bit RSA keypair which uniquely identifies you. These keys are then used with AES256 (Advanced Encryption Standard cypher) for encrypting and decrypting your proof and its comments. Your keys are encrypted and remain solely your keys.

We look after the encryption and decryption behind the scenes during your use of PageProof for proofing and approval, asking you for no extra effort other than logging in with your email and password to begin. How simple is that.