PDF security and local processing

What stays on your device

The PDF engine runs in the browser with WebAssembly. The document stays in memory during the session, and export creates a file for you to download. Closing or refreshing the tab ends the current session.

  • The PDF is not stored on the server by default
  • The file name and document text are not sent to advertising services
  • PDF thumbnails and metadata remain separate from audience measurement

Functional data

Your language choice can be kept for one year in a functional cookie and local storage. Consent preferences depend on your region and the site configuration. They must not contain information taken from the PDF.

Precautions

Local processing cannot protect a device that is already compromised and does not replace your organization’s security rules. On a shared computer, save the result in a safe location, close the tab after use, and remove copies you no longer need. A drawn or imported signature is not automatically a cryptographic signature.

Signature drawn on a phone

When this option is available, the QR code temporarily links two browsers for ten minutes. The phone encrypts the drawn signature before sending it. The European relay receives neither the PDF, the decryption key, nor clear-text strokes. The touch page has no advertising or analytics and stores nothing in local storage.