Security & File Handling

How Novaxera protects the files you upload — and exactly what happens to them.

In short: files travel over HTTPS, are processed automatically on Novaxera's server, the upload is deleted as soon as processing finishes, and the result is deleted within 60 minutes. There are no accounts and no file storage.

Encryption in transit

All traffic to novaxera.cloud uses HTTPS. Browsers are told to always use HTTPS for the site (HSTS), so files and passwords are encrypted on their way to and from the server.

Automatic deletion

Your original upload is deleted as soon as processing finishes, whether it succeeded or failed.
Result files are deleted by an automatic cleanup job within 60 minutes, whether or not you downloaded them.
Files opened in the PDF editor are deleted when you save, or within 60 minutes.

No accounts, no storage

Novaxera has no user accounts, file history or cloud storage. There is nothing to sign in to, so there are no passwords or profiles that could leak.

Passwords for PDF protection

Protect PDF encrypts files with AES-256. Passwords entered in Protect PDF and Unlock PDF are used only for that operation and are not stored or logged. Unlock PDF never guesses or cracks passwords.

Download links

Download links contain a random identifier, are excluded from search engines (noindex) and stop working once the file is deleted.

Website security

Security headers: HSTS, X-Content-Type-Options, Referrer-Policy, Permissions-Policy and frame protection.
Upload forms are protected against cross-site request forgery.
Uploads are limited to 50 MB per file.

What we don't claim

Novaxera is a small, independent service. It does not hold formal certifications such as ISO/IEC 27001. If your organization requires certified vendors, check those requirements before uploading confidential files.

Reporting a security issue

If you find a vulnerability, please email support@novaxera.cloud with "Security" in the subject. Please don't access other people's data or disrupt the service while testing. Our security.txt has the same contact.