Privacy policy
Last updated
CropShrink processes your images entirely inside your own browser. We never receive them, never store them, and could not produce them if we were asked to.
The short version
- Your images are never uploaded. Editing happens on your device.
- CropShrink sets no cookies and stores nothing in your browser.
- The site uses one cookieless analytics script that counts page views and saved images in aggregate.
- There is no account, so there is no account data.
| Data | Reaches us? |
|---|---|
| Your images, before or after editing | Never. They are read, edited and encoded in your browser tab. |
| File names, dimensions and file sizes | Never. Not even the analytics save event carries them. |
| Photo metadata: camera, date taken, GPS location | Never — and saving removes it from the file you download. The EXIF remover shows you what was there. |
| Cookies and local storage | None. Nothing is stored in your browser. |
| Name, email address, account details | None. There are no accounts. Only what you choose to put in an email to us. |
| Pages viewed, referring site, country | Yes, as aggregate counts, through cookieless analytics. |
| That an image was saved, its output format, and whether it was cropped, resized or given a target size | Yes, as an aggregate count. Nothing else about the image. |
| Your IP address, browser and the page requested | Yes, in the web server’s access logs, deleted after about 11 days. |
Your images
When you open a file, the browser reads it from your disk into the page you already have open. Cropping, resizing and encoding all run on your own processor, and the finished file is handed back to you from your browser’s memory. No request carries the image anywhere — not to us, not to a third party.
You can verify this rather than trust it — the next section shows how.
Because nothing is transmitted, nothing is retained. Closing or refreshing the tab discards the image and every edit. There is no copy to delete, no retention period, and no backup.
How to check it yourself
A privacy claim you cannot test is only a promise. This one takes a minute to test in any desktop browser:
- Open the editor, then your browser’s developer tools —
F12, or⌥⌘Ion a Mac — and select the Network tab. Reload the page so the list starts from the beginning. - Everything the page needs loads from
cropshrink.com, except the analytics script and its page-view count, which come fromanalytics.ahrefs.com. Note what is there. - Open an image and edit it: crop it, resize it, change the format and the quality.
- Look at what was added. You will see entries whose names begin with
blob:ordata:. Those are not network requests: they are the page handing the image from one part of your browser’s memory to another. Most browsers can hide them — in Chrome, tick Hide data URLs and type-scheme:blobin the filter box. What remains is empty — unless you chose AVIF, in which case two files arrived fromcropshrink.com:avif_enc.jsandavif_enc.wasm. That is the AVIF encoder being downloaded to your browser, because browsers cannot encode AVIF themselves. Open them and you will see they are responses carrying code to you, with nothing of yours in the request. - Click Download image. The file is written from memory. One small request to
analytics.ahrefs.commay appear — that is the save count described under Analytics — and you can open it to see that it carries no image and no file details.
For a stricter test, block analytics.ahrefs.com in your browser or an extension, or load the page and then disconnect from the internet. The editor keeps working exactly the same, because it never needed the network in the first place. The one exception is AVIF: choose it once before you disconnect, so the encoder is already loaded.
What the web server records
Serving the page itself is an ordinary web request, and like almost every website, the hosting layer keeps standard access logs of those requests. These can include your IP address, the URL requested, the time, your browser’s user-agent string, and the referring page. They are used to operate and secure the site — diagnosing errors, detecting abuse and understanding load — and they contain no image data, because no image data is ever sent.
These logs are kept on a server we administer ourselves, with no CDN or hosting service in between, and they are not shared with anyone or sent anywhere else. They are rotated daily and deleted after about 11 days. While they exist, we read them only to diagnose problems, and the one automated reader is a filter that temporarily blocks addresses sending malformed or abusive requests. CropShrink’s own application writes no access log at all — only error messages, which name the page that failed but not who requested it.
Cookies and local storage
CropShrink sets no cookies. It writes nothing to localStorage, sessionStorage or IndexedDB. There is no consent banner because there is nothing to consent to.
Analytics
We use Ahrefs Web Analytics to see how many people visit and which pages they read. It is a cookieless analytics service: it does not set cookies, does not collect personal data, and does not track individuals across devices, sites or days. What we see is aggregate traffic — page views, referrers, countries — never an individual’s browsing history. When you save an image, the script also records that a save happened, with the output format and whether you cropped, resized or set a target size. It never receives the image, its file name, its dimensions or its file size.
Loading it means your browser makes one request to analytics.ahrefs.com. That is the only third-party request the site makes; everything else, including the fonts, is served from cropshrink.com. If you block analytics scripts, the editor works exactly the same.
Your rights
If you are in the UK, EU or another region with comparable data protection law, you have rights to access, correct, delete and port the personal data an organisation holds about you, and to object to its processing.
In CropShrink’s case there is very little to exercise those rights against: we hold no account, no profile, no uploaded content and no analytics record tied to you. Server access logs are the only personal data involved. If you would like to ask about them, or exercise any of these rights, write to hello@cropshrink.com and we will respond within 30 days.
Children
CropShrink is a general-purpose utility and is not directed at children. We do not knowingly collect personal data from anyone, of any age.
Changes to this policy
If this policy changes in a way that affects what happens to your data, we will update the date at the top of this page. The core commitment — that images are processed on your device and never uploaded — is the reason the tool exists, and is not something we intend to change.
Contact
Questions about this policy go to hello@cropshrink.com. See the contact page for everything else, and the about page for who makes CropShrink and why it works the way it does.