What 100% Client-Side Processing Means for Privacy

When you visit a website that offers to edit your PDF, compress an image, or format your code, the standard architecture looks like this:

1. You select a file.
2. Your browser uploads that file to a remote server.
3. The server processes the file (and potentially saves a copy).
4. You download the result.

This is a server-side architecture. It's easy to build, but it's terrible for privacy.

SAMAST is built differently. We use a 100% client-side architecture.

What is Client-Side Processing?

When we say a tool is "client-side," we mean that the actual computation happens inside your web browser (the "client") using your device's CPU and memory.

When you use our Merge PDF tool, we send you the Javascript code required to merge PDFs. Your browser then runs that code on your files locally. The files never leave your computer.

How to Verify Our Claims (Don't Trust, Verify)

In security, you shouldn't just trust marketing copy. You can easily verify our "no upload" claim using your browser's Developer Tools.

1. Open this website and go to any of our tools.
2. Press F12 (or right-click and select "Inspect") to open Developer Tools.
3. Go to the Network tab.
4. Use the tool (e.g., select a PDF to merge or paste a JWT to decode).
5. Look at the Network tab. You will see zero network requests containing your file data or sensitive text.