PDF UNIVERSE
Security and processing limitations
Understand PDF Universe’s HTTPS transport, owner-bound sessions, expiring downloads, worker isolation and security limitations.
Transport and access controls
The website and processing API use HTTPS. Backend requests use signed, owner-bound browser sessions; artifact downloads use short-lived signed access URLs. These controls restrict access to the job owner but do not turn a public browser into a secret storage device. Protect your browser session and avoid sharing signed result links. Download authorizations expire within five minutes and can be reused within that period for preview, retry or range requests; file expiry revokes them. Browser sessions expire within 24 hours. Finishing a job keeps the session available for your next document.
Worker and application controls
The deployed native worker qualifies Linux filesystem and syscall restrictions before being marked ready. Application controls bound file sizes, page counts, concurrent jobs, request bodies and processing time. Passwords travel over HTTPS and are sealed by the backend before being stored with a job; the isolated worker receives the credentials needed for the operation. These are implemented controls, not a claim that all vulnerabilities are impossible.
Limits and availability
The current service accepts at most 100 MB per file and 500 pages per job, with one processing job at a time and a 30-minute processing timeout. Monthly job and transfer quotas apply. The free Space can sleep or restart. These limits can cause a job to be rejected or interrupted.
What the controls do not promise
The backend must read document contents to process them. Stored working files are not claimed to have separate end-to-end encryption. Application rate limits are not an upstream volumetric DDoS scrubbing service, and frontend hosting does not conceal the public backend URL.
Report problems safely
Report vulnerabilities privately to life.ff077@gmail.com. The disclosure contact and its expiry are published in /.well-known/security.txt. Include a non-sensitive description of the issue. Do not post document contents, passwords, browser session tokens or signed download URLs publicly. Reproduce an issue with a harmless sample when possible.
Private vulnerability reporting details · Email the security contact