ResizeWizard company

Privacy policy

ResizeWizard's privacy policy explains local browser-based image processing, basic analytics, contact emails, and important user responsibilities.

Overview

How ResizeWizard handles images

Basic deployment analytics may record aggregate page and performance information, while contact emails are processed only to respond to the message.

How it works

  1. Your browser reads the selected local image.
  2. Canvas APIs create the requested output locally.
  3. The browser creates a temporary download URL.
  4. Temporary local data disappears when the page or browser releases it.

Image handling

What local processing means

For supported editing flows, the selected image is read by your browser and processed with browser APIs. ResizeWizard does not require you to create an account or upload the file to a cloud library.

  • The browser reads the local file you select.
  • Canvas-based processing creates an edited output.
  • Downloads are created from temporary browser data.

Chrome extension

Extension permissions and local settings

ResizeWizard for Chrome processes selected files locally. It uses active-tab access only after a requested page capture, context menus for shortcuts, downloads for finished files, and Chrome storage for preferences and named presets. It does not request access to every website.

  • Selected image pixels are not sent to ResizeWizard.
  • Editor preferences remain in the Chrome profile.
  • Optional website links may include campaign parameters for aggregate referral measurement.

Limits

What this policy does not control

Your browser, device, network, email provider, and linked third-party sites have their own privacy and security behavior. Avoid sending sensitive images by email.