Does BatchMint upload my selected images?
No. Selected image bytes and decoded pixels are processed in the page and local browser workers in the current product.
Last reviewed: July 23, 2026
Privacy model
Selected image bytes, decoded pixels, filenames, watermark text and processing results remain in the page and local browser workers. The site still downloads application and codec assets, and public content pages may use approved advertising; the workspace excludes AdSense.
The privacy boundary in one table
| Data | Processing location | Persistence |
|---|---|---|
| Selected image bytes and decoded pixels | Page memory and local Web Workers | Only for the current page and processing session unless the user exports a file |
| Original filenames and watermark text | Current page and worker messages | Not synchronized by BatchMint |
| Processed image results | Browser memory and user-selected download destination | Persist only where the user saves them |
| Presets and brand kits | Current browser profile | IndexedDB until the user deletes them or clears site data |
| Theme preference | Current browser profile | Local Storage until changed or cleared |
| Public-page advertising state | Browser, Google services and consent controls where applicable | Governed by the published Cookie and Privacy policies |
What the application does not send
BatchMint application requests do not contain selected image bytes, decoded pixels, original filenames, watermark text, local logo files or processing results. Heavy operations run in local workers and return browser Blobs to the page. This is the core privacy claim and it is narrower than saying that the entire website is offline or makes no network requests.
Expected network activity
- HTML, JavaScript and CSS for the static application.
- Font files, icons, service-worker files and same-origin assets.
- WASM and codec resources for JPEG, PNG, WebP or AVIF when they are not already cached.
- A same-origin Cloudflare country signal used to block AdSense for Chinese mainland traffic.
- Approved advertising and consent resources on public explanatory pages outside the workspace.
Why the workspace is treated differently
The image-processing workspace is marked noindex and excludes the AdSense site script and its advertising preconnects. This reduces unrelated third-party activity while a user is selecting and transforming local files. Public articles, tool explanations and policy pages have a different purpose and may use approved advertising or consent services according to the published site policies.
Local storage and deletion
Presets and brand kits use IndexedDB in the current browser profile; theme preference uses Local Storage. BatchMint does not provide account-based synchronization for those records. Clearing the site's browser data removes them. Downloaded images, ZIP archives and CSV reports are outside browser site storage and remain wherever the user chose to save them.
No remote image-retention schedule is required
Because the current application does not upload selected images to a BatchMint processing service, it does not need a server bucket or timed deletion job for those files. This does not delete the user's originals, downloads, browser cache or files later uploaded to another platform. Those copies remain under the device owner or destination service.
How the boundary is tested
- Run representative JPEG, PNG and WebP jobs while recording browser network requests.
- Check request bodies, URLs and analytics properties for image bytes, filenames and watermark text.
- Confirm that the workspace build contains no AdSense loader or advertising-origin preconnect.
- Repeat with an uncached codec so expected asset downloads are not mistaken for image uploads.
- Document exceptions and limitations rather than broadening the privacy claim beyond observed behavior.
What remains outside BatchMint control
- Browser extensions, operating-system software, malware and device administrators.
- Other people using the same browser profile or downloaded-files folder.
- A marketplace, cloud drive, email provider or social network that receives an exported image later.
- Screenshots, clipboard copies or manual file sharing performed by the user.
- Availability and behavior of the browser's own storage, download and permission systems.
Policy, explanation and correction links
- Why local processing reduces image exposure
A reader-focused explanation of data minimization and remaining device risks.
- Privacy policy
The published policy for website data, third-party services and user requests.
- Testing methodology
Evidence levels and network-privacy testing scope.
FAQ
Are filenames or watermark text sent to analytics?
No. BatchMint application analytics must not include filenames, image data, watermark text or processing results.
Does local processing mean the website never connects to the internet?
No. The browser still downloads the application and uncached codec assets. Public content pages may also load approved advertising and consent resources; the workspace excludes AdSense.