KBSnap

Privacy

No upload. No storage. No training data.

Files are processed on your device

When you drop an image, the browser reads it into memory, decodes it, re-encodes it and hands you a download. There is no upload request in that path. You can confirm it yourself: open DevTools → Network, drop a file, and watch — no request carries the image. Cutting your network after the page loads also leaves every tool fully working.

What we do store

  • Your settings — target size, format, quality — in localStorage on your own device, so the form remembers you. Clear site data and they are gone.
  • Anonymous page analytics, if enabled: page path, referrer, country and Core Web Vitals. No file names, no image content, no fingerprinting.
  • Server logs for the static HTML itself, retained 7 days by the CDN.

What we never store

  • Your images — they never reach a server in this build.
  • Your images as training data, in any form.
  • Accounts, e-mail addresses or file history.

If a server-side fallback is added later

Some browsers cannot decode HEIC, and very large batches can exhaust mobile memory. If a server fallback is ever introduced for those cases, it will be opt-in and stated on the tool page, files will be deleted immediately after processing (at most one hour), and this page will be updated before it ships. Today there is no such endpoint.

Cookies

No advertising or tracking cookies are set by the core tools. If ads are enabled in the EU, a consent banner gates them and the ad slots are labelled.

Contact

Privacy questions: privacy@kbsnap.fun. We answer within a few days and will not ask you to send the image you are worried about.

Frequently asked questions

Can you see the images I process?
No. They are never transmitted. There is nothing on our side to see.
Do I need to trust you?
Not really — that is the point of local processing. Verify it with DevTools or by going offline.