ImageTextRemoverA PictureEditor.com tool

What this site can see

There is no upload endpoint here: your picture is decoded on your own machine, the fill runs there, and closing the tab throws it away — the only thing crossing the network is a model file coming to you.

Your picture

When you open a file here, the browser decodes it into memory in this tab. The boxes you draw are numbers held in the same tab, the fill rewrites pixels in the same tab, and the file you save is written by your own browser from those pixels. There is no upload endpoint on this domain, no server behind it and no account to attach anything to. Closing the tab is the whole of the clearing up.

This is checked rather than asserted. A build-time audit fails the release if any code path under the picture engine or the interface can reach the network or write to storage, which is why the one file on this site that does make a request touches no pixels at all.

The two things that do cross the network

The fill model, only if you ask for it

The structure-aware fill needs a trained network, and that file comes from cdn.pictureeditor.com. It is migan-512.onnx: 26,639,447 bytes, MIT-licensed, fetched once and then kept in this site’s own cache bucket on your device. Nothing is fetched until you press a control that names that byte count, the request carries a fixed address and nothing else, and the panel that starts it also holds the button that deletes the file again.

The runtime that executes the network is served from this domain rather than from anywhere else: 13,961,845 bytes of WebAssembly and 24,218 bytes of loader. That is a deliberate choice about who gets to see a request, and it keeps the number of other hosts this site ever contacts at exactly one.

The model comes to your picture. Your picture never goes to the model.

A decoder for iPhone photographs

A HEIC file needs a decoder no browser ships, so about a megabyte and a half of WebAssembly is fetched the first time you actually open one, and never otherwise. Like the model, it is code arriving on your machine rather than a picture leaving it.

Measurement

There is no measurement script on these pages today. The analytics property for this domain has not been set up, the token in the source is a placeholder, and because it is a placeholder the beacon is not rendered at all — shipping one that collects nothing would still make a third-party request on every visit, which on a site making this particular promise is worse than having no figures.

If that changes, it will be a cookie-free counter on this domain’s own property, never a shared account with another site, and this paragraph changes in the same release as the switch. A build gate now fails if the prose here and the configuration disagree in either direction, which is the only reason that promise is worth anything.

Advertising

This site is meant to be paid for by Google advertising, and the placements are built: one below the written section on each tool route, three inside a guide. No advertisement is served yet, because the domain has not been through review — the units render nothing at all until that is done.

When they do run, what an advertising network sees is what it sees anywhere: the address of the page, your general location from your network address, and whatever your browser tells it. It never sees your picture, because your picture is not in the page in any form a script could read, and it is never sent anywhere for an advertisement to be chosen. Personalised advertising is a matter for your own Google settings rather than something this site can turn on for you.

What is stored on your device

One thing, and only if you ask for it: the fill model, in a cache bucket named for this site. The panel that downloads it holds the control that deletes it, and clearing site data in your browser removes it just as well. No cookies are set by this site, nothing about your pictures is written down, and no history of what you have opened exists anywhere — including here.

Getting in touch

There is no account and no database, so there is nothing to request a copy of and nothing to ask us to delete. If something on this page turns out to be wrong, the correction goes here rather than into a support queue nobody reads.