PDFreevert File Security

Our website and API enforce HTTPS/TLS encryption. TLS secures communication between your browser and PDFreevert, as well as internal communication between processing workers and cloud storage.

TLS provides transport-layer protection. It does not constitute end-to-end encryption where files remain encrypted with user-exclusive keys during processing.

Uploaded files and converted outputs are stored in Cloudflare R2. Cloudflare documentation states that R2 objects and metadata are automatically encrypted at rest using AES-256 with provider-managed keys.

Our storage bucket uses an Asia-Pacific location hint. Location hints optimize routing performance on a best-effort basis but do not guarantee strict jurisdictional data residency.

Application databases store task metadata, system logs, and support inquiries; they do not store file contents.

Each conversion task executes within an isolated, temporary workspace on our processing server. Workspaces are created with restricted file system permissions and deleted automatically upon successful job completion.

Worker workspaces and object storage lifecycles operate independently. If a processing worker encounters an unexpected crash, object storage purges remain active, and recovery logs assist in system cleanup.

PDFreevert never exposes database credentials, storage keys, or signing secrets to the client browser.

Our access controls include:

• Short-lived, signed session credentials for API access;
• Upload session tokens whose plaintext values are held only by the browser, while only SHA-256 hashes are stored in the database;
• Cryptographic verification linking upload sessions, processing jobs, and output downloads;
• Short-lived signed URLs for downloading outputs;
• Strict rate limits on API endpoints and job generation; and
• Global queue limits to prevent resource exhaustion attacks.

Anyone possessing an unexpired session token or signed URL can download the associated output. Users must protect these links and avoid sharing them publicly.

PDFreevert inspects file extensions, size limits, and binary signatures before accepting uploads. Tools enforce additional limits on page counts, file quantities, and password parameters.

For cloud imports from Dropbox or public URLs, our API accepts HTTPS endpoints only and enforces redirect restrictions, private-network IP blocks, and file-size caps to mitigate Server-Side Request Forgery. While these checks prevent common exploit vectors, complex file formats are treated as untrusted input.

Files are configured to expire 3 hours after upload. An automated worker scans storage buckets every 1 hour to delete expired objects in batches.

Key retention principles:

• The expiration timestamp determines when an object becomes eligible for purging;
• The cleanup schedule determines when deletion execution occurs;
• Transient network errors may defer object deletion to the next scheduled cycle; and
• A signed download URL with 10 minutes validity will expire before the underlying object is purged from storage.

Support inquiries and feedback entries are retained in our database for 365 days. Operational logs and metadata follow independent retention schedules.

System logs track operational health, including HTTP methods, sanitized paths without query strings, response codes, processing times, request IDs, and client IP addresses. System logs do not record request payload bodies, file contents, passwords, raw session tokens, download URLs, or support messages.

Google Analytics data collection follows the regional opt-in rules defined in our Privacy Policy. Analytics events never contain file names, document text, job IDs, download links, passwords, or customer support details.

PDFreevert relies on specialized infrastructure providers: Cloudflare operates R2 storage and D1 databases; our hosting provider runs processing workers; Resend manages transactional email delivery; Google and Dropbox manage cloud authentication workflows.

While we configure these services securely, third-party infrastructure remains governed by the operational policies and security controls of the respective providers.

PDFreevert operates as an independent software utility. We do not currently publish third-party penetration-test results, SOC 2 reports, ISO 27001 certifications, HIPAA attestations, PCI DSS compliance certificates, or eIDAS trust certifications.

Users should evaluate PDFreevert based on the technical controls explicitly documented here rather than assumed enterprise compliance certifications.

You can reduce document-processing risk by following these practices:

• Upload only files you have authorization to process.
• Remove sensitive or confidential personal data before upload when feasible.
• Maintain local backups of all original documents.
• Download converted outputs immediately after completion.
• Do not share temporary session tokens or signed download URLs.
• Maintain updated browser software and secure local devices.
• Report security anomalies, exposed links, or vulnerabilities through our Contact page.

Please report security concerns to support@pdfreevert.com or select the Security option on our Contact page.

Include the affected tool name, UTC timestamp, browser version, error codes, and reproducible test steps. Do not attach real confidential documents, live passwords, or active API keys. Use synthetic test files whenever possible.

Good-faith security reports conducted without compromising user privacy or service availability will be investigated promptly.