Privacy Policy
ID Photo App privacy policy — your photo is processed on your own device and never uploaded; the little data the site touches, explained layer by layer.
Last updated: November 1, 2026.
Privacy on this site is easiest to explain in three layers — the photo you work on, the pages you load, and the ads that fund it. The first layer is the one that matters, and the design answer is absolute: your photo never leaves your device.
Layer one: your photo
The maker has no upload code — not “uploads are optional”, but no endpoint exists for a photo to be sent to. When you drop an image into the tool, your own browser decodes it, draws it to a canvas, samples the border pixels for the background check and re-encodes the crop you download. Everything happens in the tab’s memory and disappears when you close it.
You can test this claim rather than take it on faith: load the page, pull your connection, and the tool works end to end — because nothing it does ever needed the network.
Layer two: serving the pages
Like every website, this one is delivered by a hosting provider — Cloudflare, in our case — which processes routine request metadata (IP address, user agent, timestamp, requested URL) to serve files and block abuse. There are no user accounts, no forms that store data, no first-party analytics tying a visit to an identity. Crop positions, check results and file names exist only inside your tab — they are never transmitted, so there is nothing to log about them.
Usage counts
So we know which pages help, each view sends one cookieless ping to our own server. It contains only the page address, the domain of the site that linked you, the page language and any campaign tag in the link; a second ping when you leave adds how long the page was open.
Our server records the time and adds the country and network provider reported by Cloudflare, a device type (phone, tablet, desktop or bot) from your browser’s user-agent, a source category and a bot-filter label. To count daily visitors it stores a code hashed from your IP address, browser, the date and a secret value — never the IP itself — and that code changes every day. Your photo, its file name and anything you type are never included, and no cookies are used.
The maker adds one more kind of ping, carrying nothing but an action’s name: upload when a photo opens, ready when the finished crop first appears, dl:photo or dl:sheet when you click a download, and — if you answer the small card that follows a download asking whether the photo worked — fb:yes, or fb:no:rejected, fb:no:size, fb:no:usage or fb:no:other, one fixed word per button with no text field. When a step fails, the name is a fixed error code instead — error:decode for a file your browser can’t read, error:too-big for one over 40 megapixels, and a few like it. That is how we see where the tool lets people down; the photo, its name, its size and the check results never ride along.
Layer three: advertising
Adsterra supplies display banners beside the content on wide desktop screens and one 320×50 banner below the tool or article on smaller screens. Loading an ad shares your IP address and browser details with Adsterra and its advertising partners; their own cookies or identifiers may be used where your browser permits them. See Adsterra’s privacy policy. Each banner runs in an isolated, sandboxed frame that cannot read this page’s inputs, uploaded images or browser storage. We do not pass tool inputs to the ad network. Advertising does not load on About, Privacy, Contact and Disclaimer pages. Blocking ads does not disable the tool. A separate 300×250 display ad sits between the upper and lower sections of longer content.
One structural point worth stating: the ad script loads in the page, but your photo is never in the page — it lives in the tab’s memory and is handed back to you as a local download. There is no path by which it could reach an ad network or anyone else.
Cookies summary
Children
This is a general-audience utility that knowingly collects nothing from anyone — a guarantee made easy by the fact that the photo, the only sensitive input, is never transmitted at all.
Changes and questions
Policy changes appear on this page with a new date. Questions: hello@passports.pics, or the contact page.