Security & Data Protection

Security is built into the foundation of Online PDF Edits. We prioritize privacy, data minimization, and secure processing at every stage.

Security by Design

Our platform is designed to reduce exposure by minimizing server interaction and avoiding permanent file storage.

Encrypted Connection
Secure Processing
No Permanent Storage

Product Security

Technical safeguards are in place to protect document integrity and prevent misuse.

Encrypted Transport

All communication between your browser and our servers is encrypted using HTTPS with modern TLS standards.

Temporary Processing

Editing never touches a disk: your PDF is parsed, changed, and exported from memory. Tools that shell out to a converter — compress, merge, encrypt, delete or extract pages — write one short-lived temp file into a private directory and delete it the moment the job returns.

Abuse & Access Protection

We use request validation, rate limiting, and origin controls to reduce unauthorized or automated access to our APIs.

Operational Security

We follow internal best practices to protect infrastructure, access, and system configuration.

Restricted administrative access
Environment isolation (development vs production)
Secure configuration and secrets handling
Ongoing monitoring and logging

Privacy & Compliance

We align with global privacy principles focused on transparency and data minimization.

Privacy Principles

Our approach aligns with GDPR and CCPA principles such as purpose limitation, data minimization, and user control.

Processed in the EU

Your PDF is processed on a single dedicated server in France, inside the European Union. It is not distributed across regions and it does not leave the EU to be edited.

Nobody reads your document

No one reviews the contents of your file — there is no queue to review and nothing kept to open. The one exception, so you hear it from us: if you choose to send feedback, that message includes the file’s name (never its contents) so a bug report can be understood.

Logs record timing, not content

What gets recorded is how long things took — parse and export timings, page counts, file sizes. No text from your document, no images, and no copy of the file. It exists to keep the editor fast, and that is all it can be used for.

No File Retention

There is no retention window to wait out, because there is no store to delete from: your document is never written to a database, a bucket, or an account. It is not used for training, analytics, or sharing. The only file that ever reaches a disk is a temp file for the converter tools, and it is removed as soon as that job finishes.