Security
An account just to crop an image? The data breach risk
You just want to crop an image, merge a PDF or solve a maths problem. The site asks you to create an account. You sign up with your email address and a password you already use everywhere else, then forget about the service. Years later, that very service suffers a data breach. What happens to your data depends on how the provider stored it and how you chose your password. Just one example: a breach at the maths service Mathway in January 2020 exposed around 25.7 million email addresses. This page uses cases like this to explain why creating an account for a small task is an unnecessary risk, and why local tools without an account or uploads are the safer choice.
An account just to crop an image
A simple task, such as editing a photo, checking a calculation or signing a PDF, should not need an account. Yet many web services and apps require you to sign up before they let you use their features. Your email address and a password you choose end up in the provider's database. They often stay there for years.
The problem is not signing up itself. The problem is what happens to that data later. Services are bought, merged or poorly maintained, and databases become public. If your email address appears in a leaked dataset, there is little you can do about it yourself, and your password is no longer any use as protection if you have also used it elsewhere. An account is therefore not a decision you make once and then forget. It is an ongoing risk that only the provider can influence from that point on.
The pattern: a small task, a big risk
Almost all the cases below follow the same sequence:
- A small task is tied to an account.
- Your email address and a password are stored in a database.
- The database is leaked.
- If you have reused the password, someone tries it on your other accounts too.
The "Sign in with Google or Facebook" feature (social login) is particularly sensitive. If you link an account this way, your linked profiles often appear in the leak too. That is exactly what happened in the Mathway and Pixlr datasets. Instead of handing over a single password, you are therefore giving up control over access through the entire linked profile.
There is another issue: a leaked password can still be cracked if the provider has used only weak encryption. That is precisely why the most important protection is to use each password only once and secure your central accounts with a second factor.
The cases: what was actually leaked
The following table presents a short, verified selection of real cases. These services offer typical small tasks such as calculations, image editing, PDF editing or design, which are also available here as local tools. The figures are the numbers of email addresses reported by Have I Been Pwned (HIBP), checked on 30 September 2026.
| Service | What people use it for | Incident | Affected (email addresses according to HIBP) | What the dataset contained | For this task without an account |
|---|---|---|---|---|---|
| Mathway | Solving maths problems (app/web) | January 2020 | 25.7 million | Email addresses, names, password hashes (salted), linked Google and Facebook profiles, device information | Simple calculations: Calculator, Percentage Calculator. No step-by-step solutions. |
| Pixlr | Editing images online | October 2020 | 1.9 million | Email addresses, names, locations, social media profiles, password hashes (SHA-512) | Crop and resize, Filters, Compress |
| Cutout.Pro | AI image editing, background removal | February 2024 | 20.0 million | Email addresses, IP addresses, names, password hashes (MD5, salted) | Cropping and resizing: Image Resizer, Compress. There is no local tool for background removal here yet, so we do not advertise one. |
| Nitro | Editing PDFs | September 2020 | 77.2 million | Email addresses, names, password hashes (bcrypt), also document titles according to HIBP | PDF Tools, Image to PDF |
| Lumin PDF | Editing PDFs | April 2019 | 15.5 million | Email addresses, names, usernames, gender, language, password hashes (bcrypt) or Google sign-in tokens | PDF Tools |
| Canva | Designing graphics | May 2019 | 137.3 million | Email addresses, usernames, names, places of residence, password hashes (bcrypt) | Simple tasks only: Crop an image, Favicon, Gradient, Colour Picker. Canva can do much more, and we do not dispute that. |
| Adobe | Adobe account for creative and PDF services | October 2013 | 152.4 million | Email addresses, usernames, weakly encrypted passwords, password hints in plain text | For the lesson on password reuse: Password Generator, Passphrase Generator. No claim to replace Adobe's features. |
Data: Have I Been Pwned, CC BY 4.0. Summary and translation: Studio Tools.
The table deliberately states exactly what was in each dataset, and no more: "password hashes" are not the same as "passwords". Only in the Adobe breach were even the password hints exposed in plain text, while the passwords themselves were only weakly encrypted. The stronger and more unique your password, the lower the chance that it will be used to access your other accounts after a breach. We link only to tools that demonstrably process their inputs locally. Where no suitable local tool exists, we say so.
What local tools change, and what they do not
The tools on this site process your inputs locally in your browser. You upload nothing, create no account, and none of your data for this particular task is stored on a third party's server. This removes exactly the risk illustrated by the cases above: no password to leak later, no email address to appear in a breach.
That does not mean local tools can replace everything. For a streaming account, Canva's full feature set or cloud storage, a provider with a server and an account remains the normal route. Nor can a local tool change data that has already been leaked: if your email address is in an old dataset, it stays there. The difference applies only to the tasks you do from now on. If all a task requires is cropping an image, merging a PDF or working out a calculation, a local tool can do it without an account or uploads. That is exactly why it is worth taking this route. And the more important an account is to you, the more it matters how you secure it: a strong, unique password and a second factor belong on every service you want to keep using.
How to protect yourself from today
Whether you want to delete an account or simply create fewer in future, these six steps help:
- One password per account. Use a password manager, or create unique passwords with the Password Generator. The Passphrase Generator builds passphrases from random words. Reused passwords are the most common entry point after a breach.
- Secure your email account first. Your email address is the recovery key for almost all your other accounts, for example because you can use it to reset passwords. Give it its own strong password and enable two-factor authentication.
- Delete unused accounts. Since June 2022, Apple has required apps that allow account creation to offer in-app deletion too; Google Play has required this since December 2023. If you cannot find a way to delete your account, request deletion in writing under Article 17 GDPR (right to erasure).
- Check the privacy information before installing small utility apps. In the App Store, "Data Linked to You" lists the data an app collects. Prefer tools without an account. A quick task such as cropping an image or merging a PDF does not need one.
- Do not give out your main email address. Use "Sign in with Apple" with the "Hide My Email" feature, or an email alias. This helps keep your real address out of other companies' databases.
- Check whether you have been affected. Look up your address for free at Have I Been Pwned, the HPI Identity Leak Checker and the University of Bonn Leak Checker. These services receive the email address you enter, so use them only if you are comfortable with that. We deliberately do not offer this check on our site.
This handbook provides general guidance and does not replace legal advice. It does not claim to list every data breach. Details of the cases come from the public entries on Have I Been Pwned and were checked on 30 September 2026. The tools on this site process inputs locally in your browser; they do not replace security measures such as a password manager or two-factor authentication.
Sources & status of these figures
The figures in this handbook come from the public entries on Have I Been Pwned and were last checked on 30 September 2026. The HIBP dataset is licensed under the Creative Commons CC BY 4.0 licence, which requires attribution. Summary and translation: Studio Tools.
- Have I Been Pwned (public data breach records), licensed under CC BY 4.0. https://haveibeenpwned.com
- HIBP: Mathway, breached January 2020, 25,692,862 email addresses. https://haveibeenpwned.com/PwnedWebsites
- HIBP: Pixlr, breached October 2020, 1,906,808 email addresses. https://haveibeenpwned.com/PwnedWebsites
- HIBP: Cutout.Pro, breached February 2024, 19,972,829 email addresses. https://haveibeenpwned.com/PwnedWebsites
- HIBP: Nitro, breached September 2020, 77,159,696 email addresses. https://haveibeenpwned.com/PwnedWebsites
- HIBP: Lumin PDF, breached April 2019, 15,453,048 email addresses. https://haveibeenpwned.com/PwnedWebsites
- HIBP: Canva, breached May 2019, 137,272,116 email addresses. https://haveibeenpwned.com/PwnedWebsites
- HIBP: Adobe, breached October 2013, 152,445,165 email addresses. https://haveibeenpwned.com/PwnedWebsites
- Apple: apps that allow account creation must offer in-app account deletion, since 30 June 2022. developer.apple.com
- Google Play: Account Deletion Requirement in the User Data Policy, data deletion information due by 7 December 2023. support.google.com/googleplay/android-developer/answer/13327111
- HPI Identity Leak Checker. https://sec.hpi.de/leak-checker
- University of Bonn Leak Checker. https://leakchecker.uni-bonn.de