Security

A plain list of the protections we have in place, and an honest note on what they cannot cover. We only describe what the site actually does.

At a glance

  • Your files move over HTTPS and are deleted automatically 30 minutes after they are created.
  • We do not sell your files or hand them to advertisers or to other users.
  • Account passwords are stored only as salted hashes, never as readable text.
  • Files are processed on our server, so they are not end-to-end encrypted.

How we treat your files

  • Each upload is stored under a random name that cannot be guessed.
  • Only supported file types are accepted, and every file is checked for type and size (100 MB at most).
  • Original file names are cleaned before use, and download addresses cannot be manipulated to reach anything outside the upload area of the server.
  • Every result gets its own download link. It stops working after at most one hour, and it is used up once the file has been downloaded.
  • Uploads, results and PDF Editor sessions are deleted 30 minutes after they were created or last used. A background job checks every minute, and if the disk is nearly full, files may be removed earlier.

Who can open a stored file? Other users cannot. The site operator can open an uploaded file from the admin panel while it is still stored, for example to look into an error or a report of abuse. After the automatic deletion, the file no longer exists on our server.

Connection

The site is served over HTTPS, which encrypts uploads, downloads and login details between your browser and our server. It also tells your browser to keep using HTTPS, not to guess file types, and to load scripts only from approved places.

PDF passwords

  • Protect PDF locks a file with AES-256 encryption. The password must have at least 8 characters.
  • Unlock PDF removes a password only if you enter the right one. It never tries to crack or guess.
  • We cannot recover a forgotten PDF password, so keep it somewhere safe.

Your account

  • Passwords are stored as salted PBKDF2-SHA256 hashes. We cannot read yours.
  • A new password needs 8 or more characters, with an uppercase letter, a lowercase letter, a number and a special character.
  • Verification links work for 24 hours and password-reset links for 1 hour.
  • Changing your sign-in email or deleting your account both require your current password.
  • When you change your password, your other devices are signed out automatically.
  • A fresh session is created at every login. The session cookie is HttpOnly and Secure, so scripts cannot read it and it is only sent over HTTPS. A session lasts up to one day.
  • The password-reset form replies the same way whether or not an email belongs to an account, so it cannot be used to find out who has one.
  • Forms and actions that change data carry a token that blocks cross-site request forgery.

Abuse limits

To keep the service available and to slow down password guessing and bots, the server limits how often one visitor can call it. Some examples per minute: 10 login attempts, 5 sign-ups, 3 password-reset requests, 5 contact messages, 30 requests to the conversion tools and 10 to the summarizer. Everyday use stays well below these numbers.

Site hardening

  • Input from forms is checked before it is used, and redirects after login are verified so a link cannot send you to an unsafe address.
  • A Content Security Policy and other browser protections limit where scripts and frames may load from.
  • Errors and unusual requests are written to server logs so problems can be found and fixed.
  • Card payments, if paid plans are ever switched on, would be handled by Stripe, so we would not see or store your card number. Paid plans are not active today.

What we cannot promise

  • No end-to-end encryption. The server must read a file to work on it, so do not upload a document you would not be comfortable sending to any third-party web service.
  • Ezorxpdf is run by one individual, not by a security team. We work to keep it safe, but nobody can guarantee that nothing will ever go wrong.
  • You are responsible for keeping your own password safe and for the files you choose to upload.

Report an issue

If you think you have found a security problem, please tell us through the Contact page or at [email protected], with what you found and the steps to reproduce it. While testing, please do not open other people’s data or disrupt the service. Every report is read. To learn how personal data is handled, see the Privacy Policy.