P
plain.tools

Verify our claims

We believe privacy claims should be verifiable, not just stated. Here's how you can confirm that our tools actually work the way we say they do.

Our privacy claims

No server uploads

Your files never leave your device. All processing happens in your browser using JavaScript and WebAssembly.

How to verify: Open browser DevTools (Network tab) while using any tool. You'll see no outbound requests containing your data.

No tracking

We don't use analytics that track individual users. No cookies, no fingerprinting, no user profiles.

How to verify: Check the Network tab for third-party requests. Review our source code for analytics implementations.

No accounts required

Use any tool without signing up. We don't need your email or personal information.

How to verify: Simply use the tools. No signup prompts, no login walls, no personal data collection.

Local processing only

PDF operations use pdf-lib and other WebAssembly libraries that run entirely in your browser.

How to verify: View the source code. Check the browser's DevTools to see WebAssembly modules loading locally.

How to verify yourself

1

Open DevTools

Press F12 or right-click and select 'Inspect' to open your browser's developer tools.

2

Go to Network tab

Click the Network tab to monitor all HTTP requests made by the page.

3

Use any tool

Load a file and process it. Watch the Network tab for any outbound data transfers.

4

Verify no uploads

You'll see only static asset requests. No file data is sent to any server.

View the source

Open source verification

Our code is open source. You can inspect exactly how each tool works, what libraries we use, and verify that no data is transmitted to external servers.

View on GitHub

Technical architecture

WebAssembly processing

PDF operations use compiled WebAssembly modules (pdf-lib, etc.) that execute entirely within your browser's sandbox. No server-side processing.

Web Workers

Heavy computations run in Web Workers to keep the UI responsive. Workers operate in the same browser context with no network access to external servers.

File API

Files are read using the browser's File API and processed in-memory. Downloaded results are generated client-side using Blob URLs.

No persistent storage

We don't store your files anywhere. Once you close or refresh the page, all data is cleared from memory. No localStorage, no IndexedDB for file storage.