Remote signature - Encrypted sending
Get an encrypted PDF signed remotely
Recipient without an account - Separate from local mode
When you need someone else to sign a document, the PDF cannot stay only on your device. Parapheo therefore encrypts the document in your browser before sending it. The server receives an encrypted file and the decryption key is not stored with that file.
The remote signature workflow
- Prepare the PDF in the tool. You can check the document and, if needed, add any elements you have to place on it before sending.
- Enter the recipient. Add their email address, their name and an optional message explaining the request.
- The PDF is encrypted before the transfer. The key needed to read it is not kept by Parapheo with the encrypted file.
- The recipient verifies their address, then signs. They do not need to create an account to complete this step.
- Retrieve the result. The request gives access to the final PDF and to a technical evidence certificate.
What is stored and what is not
The remote workflow requires tracking data: the requester's and the signer's addresses, the status and dates of the request, as well as the encrypted file and hashes used as evidence. The encrypted document is deleted after the period stated in the service. The decryption key is not saved with the file.
For more detail on the two types of processing, see the privacy policy. It explicitly distinguishes local mode, where the PDF never leaves the device, from the encrypted remote mode.
What the evidence certificate confirms
The technical certificate presents the information recorded by the workflow, including the steps and the document hashes. It helps document how the request unfolded. It does not by itself turn the service into an advanced or qualified signature, and it is no substitute for analysing the requirements that apply to your document.
When to avoid this mode
Do not use it just to add your own signature: local mode is more direct in that case and does not transfer the PDF. Where an advanced or qualified signature, stronger identity verification or specific retention is required, check the applicable requirements before sending a request.
Frequently asked questions
Does the recipient need to sign up?
No. They verify their email address to access the request and sign the document in their browser.
Can the file be read on the server?
The document is encrypted in the browser before it is sent. The key needed to read it is not stored with the file.
Is this a qualified signature?
No. Parapheo describes this workflow as a simple electronic signature. To understand the differences in terminology and level, read the task-by-task comparison.