Privacy
PhotosUpscaler fetches a model file and a WASM runtime when you press the control that names their size, and then executes them here — your folder is read from disk, worked through in a Worker on this device and written back as an archive, and no image byte is sent to any server, ours or anybody else's.
The short version
There is no server behind photosupscaler.com. The pages are flat files, there is no API route, no form posts anywhere, and no code path by which a pixel buffer could be sent somewhere even by mistake — a build step fails if one appears in the engine or in any component.
What leaves this device
One request, and only when you ask for it
A model file is fetched from cdn.pictureeditor.com — 240,078 bytes for ESPCN, or 4,866,396 bytes for Real-ESRGAN if you opt into it — and it is fetched only after you press a control that prints those numbers. That request tells the host that some visitor asked for that file. It carries no image, no filename, no dimension and no identifier this site set. Nothing is fetched at all if you run the arithmetic path.
The WebAssembly runtime that executes the graph is served from this domain rather than from anybody’s content network, which keeps the number of other hosts this site talks to at exactly one.
Your pictures
They are read from disk by the browser, decoded in this tab, worked through in a background thread on this device and written back into an archive your browser saves. They are not uploaded, not copied to any service, and not seen by anyone operating this site.
What is written to disk, and where
Model files
Downloaded weights are kept in a Cache Storage bucket named photosupscaler-models-v1, so a return visit does not fetch them again. The estimate reference page reports how many bytes are held and deletes them on request, and deleting site data in your browser removes them too.
The run record
While a queue is running, an IndexedDB record holds the factor, the format, the naming pattern, the list of filenames with their sizes and dimensions, each file’s state and the pass cursor of the one in flight. It exists so a closed tab does not lose a forty-minute job.
It holds no source bytes and no decoded pixels. That is why picking a run back up asks you to grant the folder again rather than resuming silently: this site would rather ask for a permission twice than quietly copy five hundred photographs into browser storage. A record can be discarded at any time, and one that has not been touched for seven days is deleted the next time the page loads.
Measurement
No analytics property is configured on this domain today. No measurement script is served, no beacon is sent, and not one page view is recorded — the token that would enable it is a placeholder, and a build gate fails if any page on this site claims otherwise. If that changes, it will be a cookie-free counter on this domain’s own property, never a shared container across a group of sites, and this paragraph changes in the same release.
Advertising
This site is intended to carry Google advertising, and the placements are built: one unit on each queue route below the prose, two on each reference page and three in each guide, every one of them with its height reserved in advance so nothing moves when a unit loads or fails to.
None of them is serving yet, because the domain has not been through AdSense review. When they do serve, Google will be able to see the usual things an ad request carries — an IP address, a user agent, the page the unit is on, and whatever its own cookies and identifiers already know about the browser. It will not be able to see a picture, a filename, a dimension or anything else about the contents of a queue, because none of that leaves this tab for any unit to read.
What there is not
No account, no sign-in, no email address, no contact form, no session cookie, no fingerprinting script, no social embed, no third-party font and no tag manager. The one first-party thing stored in this browser is described above and is removable from this site’s own controls.