PrivConvert

Privacy in practice

How PrivConvert keeps file work local

PrivConvert is built so supported file and text operations run in your browser. This page explains what that covers, what may still use the network, and how you can inspect a tool yourself.

The important distinction

Local processing means the selected input is handled by browser code on your device. The site still needs network requests to load pages, application code, libraries, model assets, security services, and limited analytics metadata.

What stays in your browser

Supported tools pass selected files or pasted text to browser APIs and Web Workers. Intermediate artifacts and outputs may be kept in origin-scoped IndexedDB or OPFS storage while the job runs and until you download or clear them.

PrivConvert does not require an account and does not provide an account-based cloud conversion history. Tool pages publish their accepted input, output, browser requirements, and practical limits.

What may use the network

  • HTML, CSS, JavaScript, fonts, libraries, and tool model assets.
  • Cloudflare hosting, delivery, security, and page-performance measurement requests.
  • Plausible page views and configured product events with limited metadata such as tool slug, category, file counts, size buckets, MIME type, run status, duration, and output count.

The app's configured analytics events do not intentionally include selected file contents, filenames, raw pasted text, or generated output contents.

How to verify a representative tool

  1. Open your browser's Developer Tools and select Network.
  2. Load the tool once so required application and model assets arrive.
  3. Clear the request list, then select a non-sensitive test file.
  4. Run the tool and inspect request URLs, types, and payloads.
  5. Confirm that requests contain operational metadata rather than the selected file or generated output.

Some tools load a library or model when first used, so an entirely offline first run is not guaranteed. Browser support and cached assets also affect offline behavior.

Limits and cleanup

Browser memory, storage quotas, file formats, and device performance limit what a local tool can process. You can remove origin-scoped job data through your browser's site-data settings and delete downloaded outputs from your device.

Policy and questions

The full service disclosures are in the Privacy Policy. For questions, contact [email protected].