Last updated: October 2026.

The design goal here is that the sensitive thing — your photos — is impossible for us to collect, rather than merely promised-not-to-be. This page explains how that works and what little data the site itself touches.

The files you edit

When you drop a photo into the editor, your browser reads it straight from your disk. Every step after that — decoding, the per-pixel filter math, the before/after preview, the JPEG or PNG encode — runs in JavaScript inside that tab. There is no upload endpoint anywhere in the code; you can pull the network connection after the page loads and lose nothing but the ads.

That holds for the whole workflow: slider positions, undo history, filmstrip thumbnails and the exported file all live in the tab’s memory and vanish when it closes. File names, pixel dimensions, filter recipes and the images themselves are never transmitted — so they can’t be logged, leaked or sold from here, because they never arrive here.

The requests that happen anyway

• Page delivery. Pages are served by Cloudflare, which processes ordinary request metadata — IP address, user agent, timestamp, URL — to deliver content, resist abuse and produce aggregate traffic counts. With no accounts and no forms, there is nothing for those logs to attach to.
• Advertising. The site is free because it carries ads (Google AdSense). When an ad loads, the network may set or read cookies to count impressions and — where permitted — personalize what you’re shown. You can switch off personalization in Google’s Ads Settings or block third-party cookies; the editor is identical either way.

What we deliberately don’t run

No analytics product that profiles visitors, no sign-up flow, no contact form writing to a database, no tracking pixels in the tool. The aggregate counts from the host plus the small cookieless usage-count ping described on this page are the only usage figures that exist.

Your options

• Reading any page works with JavaScript off; only the editor itself needs it.
• Cookie and ad-personalization controls live in your browser settings.
• Privacy questions: hello@photopassport.online.

Updates to this policy

If the policy changes, the revised text replaces this page and the date above moves with it.

Usage counts

What travels for usage counts is one cookieless ping per page view — page address, the domain of the referring site, the page language and any campaign tag in the link — and a second one when you leave, with the time the page was open.

Our server adds the time, Cloudflare’s country and network-provider readings, a device type (phone, tablet, desktop or bot) inferred from the browser’s user-agent, a rough source category and a bot-filter label. Daily visitors are counted with a code hashed from your IP address, browser, the date and a secret value; it resets each day and the IP address is not stored. No cookies, and nothing about your images — no pixels, file names or sizes — is in it.