Skip to content

Privacy Policy

Last revised: April 7, 2026

NoUpload was built on a single conviction: your files are your business. When you compress an image, merge PDFs, strip EXIF data, or convert a photo format on this site, that work happens entirely on your device. Files never leave your device — this is our core promise, and it is in our name.

Most online file tools require you to upload your files to a remote server, where they sit on someone else's infrastructure while being processed. We took the opposite approach. Every operation runs in your browser, using JavaScript and WebAssembly. Your photos, documents, and images stay right where they are.

Zero File Transmission

When you drag an image into our compressor, select PDFs for merging, or open a HEIC photo for conversion, the file is read by your browser — not uploaded to a server. The processing engine runs locally using your device's CPU and memory. The output file is also created locally. At no point during this workflow does any file data leave your machine.

We have no file storage, no upload endpoint, no processing queue, and no temporary file cache. If you open your browser's network inspector while using any NoUpload tool, you will see zero outbound file transfers.

No Personal Data Collection

NoUpload does not ask for or collect:

There is no account system. You do not log in, you do not register, and there is nothing to sign up for. You use the tools and leave.

Browser Storage

NoUpload uses your browser's localStorage to save minor preferences — like your last-used quality setting, preferred output format, or recently visited tools. This data is stored on your device only. It is not transmitted anywhere, cannot be accessed by us, and you can wipe it by clearing your browser storage.

We never store file data in localStorage, IndexedDB, or any other browser storage mechanism. Once you download your processed file and close the tool, the working data is released from browser memory.

WebAssembly Processing

Several of our tools — including the WASM image optimizer — use WebAssembly modules (compiled from open-source codecs like MozJPEG, OxiPNG, and libwebp) that run natively in your browser. These modules are downloaded once as static assets (just like JavaScript or CSS) and execute entirely on your device. They do not communicate with external servers during processing.

Analytics

We use lightweight, privacy-respecting analytics to understand general traffic patterns — such as how many people visit the site or which tools get the most use. This data is aggregated and does not identify you as an individual. It tells us "the image compressor was used 500 times today," not "this specific person compressed these specific photos."

Advertising

NoUpload shows ads through Google AdSense to fund the site. Google may use cookies to personalize advertisements based on your general browsing activity. You can adjust your preferences at Google's Ad Settings. Importantly, no information about the files you process is shared with Google or any advertising partner.

Changes

If we make changes to this policy, the revised version will appear on this page with an updated date. Our core commitment — no file uploads, no server-side processing — is fundamental to what NoUpload is and will not change.

Contact

Privacy questions? Email us at [email protected].