Privacy Policy
How QuietPDF handles uploaded files, account data, telemetry, and retention.
This notice explains what data QuietPDF processes, why it is processed, where it is hosted, how long it is retained, and how to contact us about privacy questions.
Who controls the data
Privacy requests should be directed to [email protected].
QuietPDF controls the account, support, usage, and technical data needed to operate the service. Uploaded document content is handled to perform the task requested by the user.
What data we process
We process account records where sign-in is used, uploaded and generated files, usage and fair-use events, support communications, and technical logs needed to operate the service.
Guest workflows also rely on HTTP-only session ownership tokens so uploads remain isolated per browser session.
Why we process it
Data is processed to authenticate users where applicable, run requested document workflows, enforce ownership and fair-use rules, deliver outputs, and investigate service or security incidents.
OCR processes document content only when the user requests an OCR workflow.
Retention and deletion
Temporary uploaded and generated files are scheduled for deletion after 30 minutes unless a feature explicitly requires a different retention path.
Account, support, usage, and security-relevant records may be retained longer where necessary for service operation, abuse prevention, or legal obligations.
Cross-border processing and subprocessors
Production hosting is designed around Germany. If you access the service from Turkey or another country outside the hosting region, your data may be processed or stored across borders as required to operate the service.
The current subprocessor list is published separately and should be reviewed together with this notice.
Your rights
Depending on your jurisdiction, you may have rights to request access, correction, deletion, restriction, transfer, or objection to certain processing activities.
Submit requests to [email protected]. We may request additional information to verify the requester before fulfilling the request.