A screenshot can easily contain something sensitive — an API key visible in a terminal, a customer's name in a support ticket, an internal URL. Here's exactly what happens to an image you paste into this tool, in plain terms.
Nothing is uploaded, ever
The entire conversion — reading the clipboard image, rendering the preview, converting format, adjusting quality — happens using your browser's own Canvas API, locally on your device. The image data never leaves your machine as part of using this tool. There's no server-side processing step to upload to in the first place.
Nothing is stored
The pasted image exists only in your browser's memory for as long as the tab is open. Close the tab or navigate away, and it's gone — there's no history, no saved gallery, nothing persisted to a database or local storage that would survive the session.
Permission is requested only when you actively paste
Browsers require an explicit clipboard-read permission prompt, and this tool only triggers that request the moment you paste — not on page load, not in the background. You can see exactly when it happens because it's the same browser-native prompt every clipboard-reading site uses.
No tracking of what you paste
We don't log, analyze, or collect any information about the images you paste or download — only standard, aggregate website analytics (page views, not image content) like most sites use.
Offline capability, as a side effect of local processing
Because nothing about the core conversion depends on a server round-trip, the tool also works offline once the page has loaded once — a Service Worker caches what's needed so a lost connection mid-session doesn't interrupt anything.
What this doesn't protect against
This only covers what happens inside this tool. Once you download and share a screenshot elsewhere — Slack, email, a bug tracker — normal precautions apply: crop or redact sensitive details before you capture, not after.