Back to Home
Privacy & Security Guaranteed

Privacy Policy

Last Updated: May 28, 2026. Learn how we handle your files with our absolute privacy guarantee.

Our Core Commitment: Zero Server Uploads

PDFIFY is engineered with a 100% client-side architecture. Your files are processed entirely in your web browser's local memory (RAM) using client-side JavaScript, WebAssembly, and local libraries. We do not upload, read, store, or see your files on any server.

1. Files & Document Content

When you select a document to split, merge, compress, protect, redact, OCR, or annotate:

  • The file is loaded directly into browser memory (RAM) via standard file APIs.
  • All manipulations, rendering, and processing take place on your local CPU.
  • Once completed, the resulting file is downloaded directly from your browser memory to your disk.
  • No document bytes or metadata are sent over the network to PDFIFY.

2. Information We Collect

To manage access and coordinate plans, we collect limited structural metadata:

  • Account Credentials: If you choose to sign up, your profile is securely managed by Clerk (email address, name).
  • Usage Analytics: For logged-in users, a simple operation count is updated in your Clerk privateMetadata to enforce the 5 operations/day limits. For guest users, this count is stored completely locally in your browser's localStorage.
  • Billing Information: If you upgrade to Pro, payment processing is handled securely by Stripe. We do not store or collect credit card details.

3. Third-Party Integrations

PDFIFY supports importing documents directly from Google Drive and Dropbox:

  • When you authorize Google Drive or Dropbox, the authentication popup runs natively on their official OAuth servers.
  • The chosen file is fetched client-side directly into your browser's memory using secure tokens.
  • We never receive, cache, or scan your Google or Dropbox credentials or other drive files.

4. Data Security

Since files remain client-side, the risk of data intercepts or cloud leaks is virtually eliminated. For features like PDF Encryption and E-Signatures:

We leverage browser native cryptographic engines (Web Crypto APIs) and standard encryption specifications. Any password you set to protect a PDF is applied locally and is never sent back to any API.

5. Changes to This Policy

We may update this policy to reflect enhancements in local processing technologies. Updates will be posted on this page with a revised date. Since we do not store your contact details unless you register, we encourage guest users to review this page periodically.

Contact Us

If you have any questions regarding this Privacy Policy or local processing security, please reach out to us at security@pdfify.io.