Privacy architecture

The website arrives. Your image does not leave.

Local processing means the application code is delivered to your browser, then the browser performs the image work on the device. This page separates that technical promise from vague claims like “secure” or “100% private.”

01Load the application

The browser requests the site interface and processing code from Cloudflare.

02Choose and process locally

File access, previewing, decoding, Canvas work, and supported worker tasks stay inside the tab.

03Save the result

The browser creates a temporary result URL and downloads the file only when you ask.

The boundary, item by item

What goes where

“Local” applies to selected files and processing. Ordinary website requests still reach the hosting network so the page can load.

InformationLocationPurpose
Website HTML, CSS, and JavaScriptDownloaded from the web hostRequired to open the application
Selected image contentsYour browser sessionDecoded and transformed locally
FilenameYour browser sessionUsed only to suggest a download name
Temporary preview and resultBrowser memoryRevoked when replaced, reset, or closed
Theme preferenceLocal browser storageRemembers light or dark mode
Current free MVP

What the current product deliberately omits

  • No server image-upload endpoint
  • No account, database, or cloud image library
  • No session replay or behavioural advertising scripts
  • No filename or image-content analytics
  • No remote AI image-processing API
  • No permanent processing history

Hosting can still see a page request

Cloudflare may process the IP address, requested URL, time, browser information, and security signals needed to deliver and protect the website. Those ordinary requests do not include the selected image, filename, preview, or result.

Browser limits still apply

Large images use device memory, supported codecs vary, and closing a tab during processing ends the job. Local processing reduces data exposure; it does not make every device equally capable.

Future network features need a new label

If an API, cloud sync, or server-based AI feature is added later, the interface and policy must identify the transmission before a file is sent. It cannot be silently covered by the local-tools promise.

Ready to verify the experience for yourself?