Privacy Policy

HEIC2JPG privacy policy — photos are decoded and re-encoded inside your browser; network activity is page delivery, one decoder download, ads and a small cookieless usage ping.

Last updated: September 2026.

The three facts that cover it

  1. Photos never upload. HEIC decode plus JPG/PNG/WebP encode runs in a WebAssembly worker inside your tab; no upload endpoint and no processing server exist.
  2. One download happens. The first HEIC file triggers a fetch of the decoder itself (/libheif-*.js and /libheif-*.wasm, ~1.5 MB) from this site’s own domain — not a third-party CDN. Afterwards the tool runs fully offline: cut the connection and keep converting.
  3. Ordinary web plumbing still runs. Hosting logs and ad requests exist, detailed below.

Hosting logs

Cloudflare’s edge delivers the pages and the decoder, recording the routine request fields — client IP, browser agent, timestamp, requested path — to serve traffic and deter abuse. With no accounts and no forms, nothing ties those records to you or your files.

Ads

Funding comes from Google AdSense ads. Google may set or read cookies to measure impressions and, where permitted, personalise them — Google’s own policies apply. The opt-out lives in Google’s Ads Settings, or block third-party cookies; converting works identically with ads blocked.

Measuring usage

Aggregate, privacy-respecting traffic figures are the only analytics — no cross-site tracking, no profiles. One anonymous cookieless beacon marks a page view (URL, referrer, CDN-reported country, duration); file names, photo contents and conversion results are never part of it — they never reach the network.

Controls and contact

The articles read fine with JavaScript off; the converter needs it. Cookie and ad-personalisation controls are browser-side. Policy questions: hello@photopassport.online. Revisions land on this page under a new date.