Last updated 20 August 2026.
The short version
We do not receive your files. Every tool on this site processes images entirely within your browser using local APIs. No file data is uploaded, stored, logged, or transmitted to us or to anyone else.
You can verify this rather than trust it: open any tool, disconnect from the internet, and it will continue to work normally.
Separately from that: the site does send anonymous, cookieless usage counts to PostHog. They record which tool ran and how it went. They contain nothing about your files. Details below.
Files you open in our tools
When you drop a file into a tool, your browser reads it into memory on your own device. Processing happens locally. Results are held in temporary in-memory storage so your browser can offer them as a download. Closing or reloading the tab discards everything. Nothing persists on our side because nothing reaches our side.
Information we do collect
This site is served as static files. Our hosting provider records standard web server logs — IP address, user agent, requested page, timestamp — as an automatic part of delivering any website. These logs are used for security and aggregate traffic counts, and they contain no information about the files you process.
We set no cookie of any kind. There are no user accounts, so we hold no email addresses, names, or payment details.
Analytics
The site sends anonymous usage events to PostHog, a product analytics service, on their servers in the United States. It is how we know which tools are used and which checks fail.
The complete set of fields an event can carry:
- Which tool you were on, and which preset you picked.
- The settings you chose on that tool — the fit, the output format, the quality tier — recorded as the names shown in the dropdowns. Where a setting is a number you type, such as a quality slider or a target file size, it is rounded into a bucket first, so the exact figure you entered is not sent.
- Whether a check passed or failed, and which rules failed.
- How many files you dropped, and the image formats going in and out.
- The kind of error, if one happened, and the step it happened at.
-
File sizes, run times and compression ratios, rounded into buckets. A 2.3 MB file is recorded
as
1_4mb; a run of 640 ms is recorded as500_1000ms. - The page address, with anything after a
?removed. -
Which page of ours you came from, as a tool name and nothing else — so we can see whether
people move between the tools. If you arrived from anywhere other than this site, a search engine
or a link, that is recorded only as
external. The address you came from, and any search terms in it, are never sent and cannot be reconstructed from what is. - A coarse browser, operating system and device type.
Never collected, on any page, by any tool:
- Filenames.
- File contents or pixel data.
- EXIF, or any other metadata embedded in your images.
- Exact dimensions or exact byte counts, which could single out one specific file.
That second list is enforced in code, not by policy. The function that builds an event copies a fixed set of permitted fields and cannot read any other value off a file, so a filename cannot reach the network even by mistake.
It is cookieless. A random ID is created in memory when a page loads and discarded when you close the tab. Nothing is written to or read from your device — no cookie, no local storage, no session storage. That is why there is no consent banner. The cost is real: we cannot tell a returning visitor from a new one, and one person opening two tools counts as two people.
If your browser sends Do Not Track or Global Privacy Control, nothing is sent at all.
Third parties
PostHog is the only one. No third-party script, font, stylesheet or tracking pixel loads on any page. The analytics code is a file of ours, and it is the only thing on the site that makes a network request after the page has loaded.
Those requests go to a path on this domain, which our CDN forwards to PostHog. That is a routing choice, not a privacy one: it keeps the page locked to a single origin and stops ad blockers discarding the data. PostHog still receives the event, and your IP address and user agent reach them as on any request.
From that IP address PostHog derives an approximate location and stores it alongside each event: country, region, city, postal code, coordinates and timezone. The coordinates are accurate to about five kilometres — they describe a neighbourhood, not an address. Country is the part we actually look at; the rest is a by-product of how their service works rather than something this site asks for. Your IP address is held by PostHog, not by us, and nothing on this site joins it to anything else.
If advertising is introduced to fund the site, this page will be updated before that happens, naming the specific providers and the cookies they set.
Children
These tools are general-purpose utilities not directed at children, and we knowingly collect no personal information from anyone, including children under 13.
Your rights
Data protection law gives you rights to access, correct and delete personal data held about you. We hold none beyond the server logs and the anonymous events described above, and those events carry no identifier that outlives your visit, so there is nothing to look up. If you would like your IP address removed from the logs, contact us and we will do it.
Changes
Material changes to this policy will be reflected in the “last updated” date above. Because the no-upload architecture is the foundation of the whole site rather than a policy choice, any change to it would be announced prominently rather than quietly edited in.
Contact
Questions about this policy: see the contact page.