EasyPDFKit
Loading tools and optimizing the interface for a smooth PDF workflow.
Legal
A plain-language overview of how EasyPDFKit handles processing paths, technical data, and document-related privacy considerations.
Last updated: 18 March 2026
Processing
Many workflows are designed to run locally in your browser, but some tools may depend on runtime or server-side support.
Collection
Service diagnostics, request metadata, and operational logs may be collected to keep the product reliable and secure.
Responsibility
You should decide whether a document is appropriate for browser-based or server-assisted handling before using a tool.
This Privacy Policy explains how EasyPDFKit handles information when you use our PDF workflows, including compression, signing, merging, splitting, conversion, rotation, organization, numbering, and protection features.
The service is designed to minimize unnecessary data handling, but the exact processing path can differ by tool, browser capability, file type, deployment environment, and operational requirements.
Many workflows are designed to process files directly in your browser. In those cases, file content typically remains on your device during processing and is not intentionally stored by us as part of ordinary use.
Some features may rely on server-side processing, temporary runtime handling, or environment-specific tooling depending on the task being performed. This can happen for compatibility, performance, or feature reasons. You should assume that processing behavior may vary across tools and review whether a workflow is appropriate for your document sensitivity.
We may collect limited technical information necessary to operate, secure, and improve the service. This can include browser type, device information, IP-related network data, crash details, request metadata, performance measurements, and service diagnostics.
We do not intentionally collect document content from files processed entirely within the browser in normal operation. However, metadata, diagnostic events, or transient processing information may still arise as part of application delivery, debugging, abuse prevention, or server-side tool execution.
We may use cookies, local storage, analytics tools, or similar technologies to support core functionality, remember basic preferences, understand site usage, and improve stability and performance.
Your browser may allow you to block or clear cookies and related storage, but some site behavior may be limited if you do so.
We aim to avoid retaining user file content longer than reasonably necessary for the requested processing workflow, service operation, troubleshooting, or security protection.
Technical logs, diagnostic information, and operational records may be retained for a limited period for reliability, abuse prevention, incident response, and service improvement. Retention periods may vary based on infrastructure, legal obligations, or security needs.
We apply reasonable administrative, technical, and operational measures intended to protect the service and reduce unauthorized access, misuse, or disruption. However, no internet-based system or storage environment can be guaranteed to be completely secure.
You remain responsible for choosing appropriate devices, browsers, network environments, internal approval processes, and password-sharing practices when working with sensitive or regulated documents.
Some parts of the service may rely on third-party libraries, infrastructure providers, hosting systems, analytics tools, or runtime services. Those providers may process limited technical information as part of delivering functionality, security, or uptime.
Their privacy and security practices are governed by their own terms and policies, and we encourage you to review them where relevant to your use.
You are responsible for deciding whether to use the service for a particular file, for maintaining your own backups, and for reviewing all outputs before sharing, storing, or relying on them.
If your documents are confidential, regulated, privileged, or subject to contractual controls, you should apply your own internal review before using any browser-based or server-assisted processing workflow.
EasyPDFKit is not directed to children, and we do not knowingly collect personal information from children through the service.
We may update this Privacy Policy from time to time to reflect product, legal, operational, or security changes. Updated versions become effective when posted on this page unless stated otherwise.
Your continued use of the service after an update indicates acceptance of the revised policy.
If you have privacy-related questions about this policy or how the service operates, use the Help page linked in the site footer for the current support path.