Security and file processing

Processing model and scope

Tools.4PDF.Net processes PDFs on the server. During an anonymous session, the browser creates a job, uploads files, tracks status, and receives a result link after the worker finishes. Resource-intensive tasks use a separate queue so the interface remains responsive during processing.

This page describes the technical measures currently in use. It does not claim that the system cannot be attacked or provide any TLS certification, compliance badge, or legal guarantee that the service has not published and verified.

Session isolation and access control

Each job belongs to an anonymous session. The API checks the session before showing status, creating a download link, or deleting the job. Files are not stored in a public directory.

The session cookie is HttpOnly, SameSite=Lax, and signed. The signature helps the server detect a modified cookie, while HttpOnly limits access from page JavaScript. The current tools do not require an account, but you must still protect your device and browser session.

• Upload and download links are signed and short-lived.
• Storage object names do not use the user's file name directly.
• The API checks size, MIME type, and format signature before processing.
• Permission to view status, create links, and delete jobs is checked against the session.

Files, links, and data lifecycle

Input files and results stay in private storage. A signed URL grants access only to its related object and action for a set period. It does not make the file public. Do not forward active upload or download URLs to anyone else.

Job access expires after one hour. Cleanup runs every five minutes, so physical deletion may occur shortly after expiration, especially when jobs are queued. This mechanism limits how long files remain available for a job, but you should still delete a task when you finish.

Protecting sensitive data

Passwords used to encrypt, decrypt, or sign PDFs are protected with AES-256-GCM before they are written to the database. The worker decrypts this data only while performing the job.

Encrypting stored sensitive values reduces the impact of unintended access to stored data. Sending confidential information through an online service still carries risk. Provide only the options a task needs, never email passwords to support, and use a test certificate when checking the digital signing flow.

Input validation and result reliability

Before processing, the API checks size, MIME type, and format signature to reject some unsuitable inputs. This is one layer of defense. It does not prove that every accepted file is safe or error-free.

PDFs may contain complex structures, embedded fonts, images, forms, signatures, or damaged data. OCR, conversion, repair, compression, and digital signing results vary by file. Open and check the output before using it for legal records, long-term archiving, or an important process.

• Keep the original and a backup before editing.
• Upload only the pages and data the task needs.
• After processing, check the contents, page order, searchability, and protection settings.
• Do not treat Tools.4PDF.Net as a repository or your only copy.

Your responsibilities and security limits

No online system removes every risk. Do not upload private keys or documents beyond what a task needs. For digital signing, use a test certificate if you are only checking the process.

You are responsible for protecting your device, browser, session cookie, and downloaded files; ensuring you have the right to process documents; keeping signed links private; and deleting jobs you no longer need. If a document requires special controls, decide whether an online service is suitable before uploading it.

This security information describes how the service works. It is not legal advice, a risk assessment for an organization, or a promise that any measure is suitable for every type of data.

Reporting an incident or vulnerability

Report security issues to support@4pdf.net. Include the tool name, time observed, browser, error code, and steps to reproduce the issue with a nonsensitive sample file. Do not attach real documents, passwords, private keys, digital certificates, or active download links.

Do not exploit an issue beyond what is needed to demonstrate it, access another session's data, disrupt the queue, or publish details that may put users at risk before the issue is reviewed. Reports are assessed by severity and reproducibility. The service does not publish a fixed response time.