PRIVACY POLICY

At PDF Studio, privacy is an architectural guarantee rather than an afterthought. When you compress, split, or merge a PDF document, all processing occurs strictly inside volatile RAM memory buffers (via Python's io.BytesIO).

Your uploaded PDF documents, text contents, embedded images, and processed files are NEVER saved, cached, written, or retained on any hard drive or persistent disk storage. Once the streaming response delivers your file back to your browser, all PDF byte streams are immediately released and wiped from volatile system memory.

To protect our infrastructure against distributed Denial of Service (DDoS) attacks, automated scraping abuse, and excessive resource exhaustion, our backend records minimal, non-identifying operational audit logs into an isolated database table:

• Client IP address (collected for real-time abuse mitigation and rate-limiting)
• Action type performed (e.g., compress, split, merge)
• Document page count
• Byte sizes (original size, processed size, compression ratio)
• Processing time duration in milliseconds
• Timestamp of execution

This telemetry data is stored securely in an isolated PostgreSQL instance, is strictly decoupled from any identity records, and is never sold, shared, or matched with personal profiles. We never log or inspect document contents.

PDF Studio does not place third-party advertising cookies, browser fingerprinting scripts, or behavioral analytics trackers on your device. We do not participate in cross-site ad networks.

Our infrastructure follows industry best practices for transport layer security (TLS 1.3 encryption for all network transfers) and automatic container recycling. For questions, audits, or data privacy requests, you may contact our engineering team via the repository channels.