Does the site make any network requests?
Yes. It loads site and codec assets, and public content pages can load analytics or advertising. The workspace does not send selected image bytes, filenames or watermark text.
Local processing · no image upload
Compress images without uploading
BatchMint performs decode, resize, compression and export in the browser so selected image data stays on the device by default.
Images do not need to be uploaded because modern browsers can decode pixels, run WebAssembly codecs in Web Workers and create downloadable Blobs on the device. BatchMint serves the application and codecs, while the selected image data follows a separate local-only path.
Open workspaceUse cases
- Work with unreleased product photography
- Process client images without adding a cloud-transfer step
- Continue previously loaded workflows on unreliable connections
Why an upload is unnecessary
Canvas APIs expose decoded pixels, WebAssembly provides browser versions of image codecs, and Web Workers keep heavy encoding away from the main interface. The output can be constructed entirely in memory and written to a user-selected folder or ZIP.
This design removes BatchMint's image-storage role. It does not make the entire browser or device private: extensions, operating-system software and services you later upload to remain outside BatchMint's control.
Which network requests still exist
The browser still requests HTML, JavaScript, CSS, fonts and WASM codec assets. Public content pages can load approved analytics or advertising resources, while the processing workspace excludes the AdSense site script.
- Selected image bytes are not application request payloads.
- Filenames and watermark text are excluded from application analytics.
- Previously uncached codecs may require a connection before offline processing works.
How to verify the privacy claim
Open browser developer tools, clear the Network panel, choose a uniquely named test image and run a batch. Inspect request URLs, payloads and analytics events. The documented test plan treats any image byte, filename or watermark-text request as a serious defect.
How local browser processing works
The page receives browser File objects chosen by the user. A worker decodes and transforms one image at a time, then returns an encoded Blob. Object URLs display previews and local browser APIs save results. The workspace has no application request that contains image bytes, filenames, watermark text or processing results.
Selected images, filenames and watermark text are not sent to a BatchMint processing server. The browser still requests the site code, styles and codec assets used on demand.
Read the complete privacy modelHow to use it
- Open the workspace and choose local JPEG, PNG or WebP files.
- Set format, resize, compression and optional watermark controls.
- Process in local workers, review results and save them without a cloud job.
Sources and verification dates
Platform rules can change. Marketplace requirements below link to official pages, with the retrieval date and scope recorded for each source.
- BatchMint privacy model
Defines local data, required network resources and privacy boundaries.
- BatchMint testing methodology
Explains network-privacy and reproducibility checks.
Limitations
- Initial site and codec assets can require a network connection.
- Browser memory, extensions and device software remain outside BatchMint's privacy boundary.
- Opening an exported file in another service follows that service's privacy policy.
FAQ
Can the workspace work offline?
Previously loaded application and codec assets can be cached by the service worker, but uncached formats need an initial connection.
Evidence and privacy
Selected image bytes, filenames and watermark text are not sent to BatchMint servers.
Read the testing methodology