🔒 Files never leave your device. All PDF processing happens 100% locally in your browser RAM.
Local Processing Safeguards

Privacy Policy

PDF Toolkit is built on a zero-trust, client-side execution architecture. We believe your files are your business, and they should never leave your sight.

🔒

100% Local

Files are processed in your local browser's memory using WebAssembly. No uploading to cloud servers.

👁️

Zero Tracking

We do not collect file contents, metadata, passwords, or personal parameters. Your data stays entirely in RAM.

🌐

Offline Ready

You can disconnect your internet entirely after loading PDF Toolkit and use all tools with absolute confidence.

1. Scope and Philosophy

At PDF Toolkit, we have re-engineered standard web utility applications. Traditional online PDF editors require you to upload documents to external servers, creating substantial privacy and cybersecurity risks. Our suite operates on a completely opposite philosophy: **zero-server data transfer**. All scripts, operations, and file manipulation binaries execute locally within your device.

2. Document Content Processing

Any file you upload (including PDFs, image assets, bookmarks, metadata configurations, or decryption passwords) is loaded into your web browser's local memory partition (`ArrayBuffer`, WebAssembly memory space, and JavaScript variables).

These documents are never routed to, stored on, or processed by our server infrastructure. No background API queries are executed. When you download a modified file, it is compiled locally and retrieved from your browser RAM.

3. Analytics and Operational Metrics

We prioritize clarity:

  • No Document Loggers: No tracking systems read, index, or audit your document data, titles, keywords, text strings, annotations, or sizes.
  • Anonymized Site Performance: We may utilize lightweight, privacy-focused client-side analytics to record static page views (e.g. how many times page sizes are checked) to help prioritize tools. However, these metrics contain no document contents, filenames, or identifying credentials.

4. Password and Decryption Protection

When utilizing tools like the **PDF Password Remover** or protected viewers, the decryption processes run within your device using client-side libraries. The encryption keys remain in local memory and are discarded immediately upon page refresh or site termination.

5. Cookies and Local Storage

We use Local Storage strictly to store basic application configuration settings (such as your dark mode UI preference). Local Storage data never leaves your web browser and can be cleared at any time through your browser settings.

6. Google AdSense & Third-Party Advertising

PDF Toolkit partners with Google AdSense to serve advertisements on our website. To ensure transparency and compliance with Google's Advertising Policies, please note the following:

  • Third-Party Vendors: Third-party vendors, including Google, use cookies to serve ads based on a user's prior visits to this website or other websites on the internet.
  • Advertising Cookies: Google's use of advertising cookies enables it and its partners to serve personalized or non-personalized ads to users based on their visits to PDF Toolkit and/or other sites on the Internet.
  • Opting Out of Personalized Ads: Users may opt out of personalized advertising by visiting Google Ads Settings. Alternatively, users can opt out of third-party vendor use of cookies for personalized advertising by visiting www.aboutads.info.

7. Updates to This Policy

As PDF Toolkit expands to offer new offline utilities, we will continue to update this policy to specify security characteristics. All subsequent revisions will strictly preserve the absolute offline-local execution architecture.

Last updated: June 20, 2026Version: 1.1.0 (Fully Client-Side)