Cookie Policy

This site sets no cookies. Not for image processing, not for preferences, not for measurement, not for advertising. There are no first-party cookies and no third-party cookies, because there is no third-party code on the site to set them.

A cookie is a small piece of text a website asks your browser to store and send back on later requests. Cookies are how sites keep you signed in, remember a shopping basket, or recognise a returning visitor across days and — in the advertising case — across other sites entirely.

They are a mechanism for carrying state between your browser and a server. PixelEditor has no server-side state to carry, so it has no use for the mechanism.

Every tool here runs inside the page while it is open. Your image is held in the tab’s memory, processed there, and released when you reload or close the page. None of that involves a cookie: a cookie could not hold an image, and there is no server session for it to identify.

There are no accounts, so nothing to sign in to. There is no basket, no saved history, no cross-visit recognition of any kind. Your tool settings are not remembered between visits — that is the trade-off for storing nothing about you, and it is deliberate.

Cookies are not the only way a site can keep data on your device, so for completeness: PixelEditor does not write to local storage, session storage or IndexedDB either, and it does not install a service worker. Your images are never written to any of them.

The only data that exists while you use a tool is held in the page’s memory, and the browser reclaims it when the page goes away.

There is no analytics on this site. No Google Analytics, no privacy-friendly analytics alternative, no tracking pixel, no heatmap or session-recording tool, no A/B testing script, no advertising or remarketing tag, no error-reporting service that phones home.

This means we genuinely do not know how many people use the site or which tools are popular, beyond whatever the hosting provider’s own request logs show. The Privacy Policy explains what those logs contain, since a web host that serves pages inevitably records requests.

Third-party cookies are usually set by embedded content: advertising networks, social buttons, embedded videos, chat widgets, hosted fonts and CAPTCHAs. This site embeds none of those.

Fonts are self-hosted, so no font provider is contacted when you open a page. The image-metadata and ZIP libraries the tools use are bundled into the site and loaded from this site’s own address when a tool first needs them — not fetched from anyone else’s content delivery network. Loading any page here produces no request to a third-party domain, which is the reason there are no third-party cookies to describe.

Your browser does its own housekeeping for every website you visit, including this one, and we neither control nor rely on it:

• Caching site files. Pages, stylesheets, fonts and scripts may be stored in the browser’s cache so the site loads faster next time. This is the browser’s standard behaviour for static files; it is not a cookie, it identifies nobody, and it contains none of your images.
• History. The pages you visit appear in your browsing history, as with any site.

Both are cleared with your browser’s normal “clear browsing data” controls, or avoided entirely by using a private window.

When you download a processed image or a ZIP archive, your browser saves it where it saves downloads. That file is then an ordinary file on your device, under your control and outside the scope of this site. If you were processing something sensitive, remember that the downloaded copy stays in your downloads folder until you move or delete it.

Consent banners exist because sites place cookies that are not strictly necessary, and the law requires consent for those. A site that sets no cookies at all has nothing to ask consent for, so a banner here would be theatre — and a pointless obstacle between you and the tool you came to use.

It would also break a rule this project holds to: nothing may overlay or interfere with selecting, editing, previewing or downloading an image. The legal documents live on their own pages, linked in the footer, and stay out of the way of the work.

Nothing needs to be blocked for this site, but every major browser lets you view and delete cookies and block them by default, in its privacy or content settings. Blocking cookies entirely will not affect any tool here, since none are used. You can also verify this claim: open your browser’s developer tools, look at the storage or application panel while using any tool on this site, and check the cookie list for yourself.

If a cookie or an analytics tool were ever introduced, this page would be updated to say exactly what it is and why, with the date at the top changed, and anything requiring consent would ask for it properly rather than assuming it. We would rather revise this document than keep a claim here that had stopped being true.

Questions can go to support@mrmanager.me. See also the Privacy Policy and the Terms of Service.