Privacy policy

When you use a tool, your file is read from your disk into the memory of the browser tab, processed there by a model running on your own hardware, and written back out as a download. No request carrying your image is ever made to our servers, or to anyone else’s.

You can confirm this yourself. Open your browser’s developer tools, watch the Network tab while you edit, or simply disconnect from the internet after a tool has loaded and keep working. How on-device processing works explains the pipeline in more detail.

Because we never receive your images, we also cannot recover one for you, inspect one to debug a problem, or produce one in response to a legal request. That is a real limitation and we would rather state it than pretend otherwise.

Our hosting provider records standard web server logs when your browser requests a page or a file from us. These typically contain your IP address, the URL requested, the time of the request, your user agent string and the referring page. Every website on the internet generates these; they are how a server answers a request at all.

We use them only to:

• Keep the site online and diagnose errors
• Detect and block abuse, scraping and denial of service attempts
• Understand aggregate load, so we can size what we pay for

We do not build profiles from them, do not sell them and do not combine them with anything else. They are retained by our host for a short operational period and then rotated out.

At the time this page was last updated we run no analytics: no Google Analytics, no session recording, no heatmaps, no advertising pixels and no third party tracking scripts of any kind.

We may add privacy-respecting, aggregate analytics later, because running a site with no idea which pages are useful is its own kind of problem. If we do, we will update this section before it goes live, say exactly which tool we use and what it collects, and note it in the changelog. We will not add anything that receives your images, because there is nothing for it to receive.

The tools store things locally so they do not have to download them again. Everything listed here stays on your device and is not readable by us:

• Model files, kept in Cache Storage after the first run. This is what lets a tool work offline and start instantly the second time.
• Tool preferences, such as the last export format or quality you chose, kept in local storage.

You can clear all of it at any time by clearing site data for this domain in your browser settings. The tools will simply download the model again the next time you need one. See the cookie page for the full list.

If you write to [email protected], we hold your message and your email address in our mail provider’s system so that we can reply and so we can find the thread again if you write back. We do not add you to a mailing list from a support email, and we do not pass your address to anyone else.

Ask us to delete the correspondence and we will, other than anything we are required to keep for accounting or legal reasons.

Today the list is short:

• Our hosting and CDN provider, which serves this site and generates the logs described above.
• Our email provider, which carries messages to and from the support address.
• Google Fonts, self-hosted at build time rather than requested from Google by your browser, so no font request leaves our domain.

When paid plans launch we will add a payment processor, which will handle card details directly so that we never hold them. This section will be updated before that happens.

Depending on where you live, you may have the right to ask what personal data we hold about you, to correct it, to have it deleted, or to object to how it is used. Under the GDPR, the CCPA and similar laws, those rights apply to us.

In practice the honest answer to most such requests is that we hold almost nothing: some server log lines tied to an IP address, and any email you sent us. Write to [email protected] and we will tell you exactly what exists and remove what we are able to remove.

Photomop is not directed at children under 13, and we do not knowingly collect personal information from them. Since the tools currently require no account and transmit no images, there is very little for a child to disclose to us in the first place.

If this policy changes in any way that matters, we will update the date at the top of the page and record the change in the changelog. We will not quietly start collecting something and mention it later. Material changes, such as adding analytics or a payment processor, get written here before they ship, not after.

Questions about any of this go to [email protected], or through the contact page. A person reads it.