Skip to main content

Privacy Policy

Your privacy is a product constraint, not a marketing line. OpenToolsKit is built to keep document processing local while making source, attribution, and sponsor boundaries explicit.

No Server Uploads

Your files are never uploaded to our processing servers. Browser-based tools run locally where applicable.

Local Processing

Document operations are performed with JavaScript, WebAssembly, and workers directly on your device.

Automatic Cleanup

Working data is cleared when the tab closes or when you reset the tool flow.

Clear Boundaries

Support, source, advertising, and partner surfaces stay separate from file processing and are labeled when present.

Last updated: April 22, 2026

1. Introduction

OpenToolsKit ("we", "our", or "us") is committed to protecting your privacy. This policy explains the data boundaries for our browser-first tools, public source links, and clearly labeled third-party sponsor placements.

2. How the service works

OpenToolsKit is designed around local processing where applicable. That means:

  • Most document processing happens directly in your browser
  • Your working files are not sent to OpenToolsKit processing servers
  • We cannot inspect the content of files that stay on your device
  • Your downloads stay available without sponsor interaction

3. Information we collect

3.1 Your files

We do not collect your uploaded working files for processing. They remain in your browser unless you explicitly open an outbound third-party link or use a feature that states otherwise.

3.2 Usage signals

We may rely on limited browser-side state to support language preference, theme choice, recent history, and frequency caps such as "show once per session."

4. Local storage and session state

OpenToolsKit may use your browser's local storage or session storage to:

  • Remember language and theme preferences
  • Store recent tool history and saved in-browser workflows
  • Limit repeat exposure for non-core ad formats during the same session

5. Ads and partner offers

OpenToolsKit may show labeled ad placements or partner suggestions when enabled. These surfaces help fund the open-source service, but they are separate from the browser-side file tools.

  • Core tool results remain available without clicking an ad or partner link
  • Partner links, when enabled, are labeled and open away from the current tool flow
  • Third-party networks may deliver creatives, links, landing pages, and their own tracking technologies

6. Third-party services

We may rely on third-party providers for static hosting, outbound sponsor routing, ad inventory, and public source distribution. OpenToolsKit does not individually author every advertisement or every third-party destination page shown by those networks.

7. Source availability and attribution

OpenToolsKit is based on PDFCraft under AGPL-3.0. The live site links to the public repository and keeps attribution visible through the footer, support page, and NOTICE file.

8. Contact and support

For privacy questions, support requests, bug reports, and source review, use the contact page. General users can email support, and developer-facing reports can use the public GitHub issue tracker.

100% Private - Files never leave your device

Your documents are processed securely in your browser