5 Things I Never Store in the Cloud
I am not anti-cloud. For a lot of everyday files, cloud storage is useful, practical, and sometimes the right answer. Shared documents, ordinary photos, and routine backups all make sense there.
But there is another category of file where convenience is not the main question. Control is. For certain kinds of personal information, I would rather keep the files encrypted locally than let them live in yet another synced account.
This is not about paranoia. It is about reducing unnecessary exposure. The more sensitive the file, the less I want it copied across multiple services, devices, recovery workflows, and background sync systems.
1) Scans of IDs and personal records
Driver’s licenses, passports, Social Security cards, birth certificates, and insurance cards are exactly the kinds of files that create a headache if they leak.
Even when a cloud provider is reputable, storing these in the cloud means trusting more than one thing. You are trusting your account security, your email security, password resets, synced devices, and whatever other services end up touching the file later.
For documents like these, I prefer local encrypted storage and deliberate access, not casual availability.
2) Recovery codes and account backup files
Two-factor recovery codes, backup authentication files, password reset notes, and emergency access records can be even more sensitive than the password itself.
If someone gets access to those files, they may not need to guess anything. They can simply go around your protections.
That is why I do not like leaving this kind of information inside a general-purpose cloud folder. It deserves a tighter box.
3) Financial and tax documents
Tax returns, W-2s, 1099s, loan papers, bank statements, and account documents contain far more personal context than most people realize. A single file may include your address, employer, income history, and account details all in one place.
That makes these documents useful not just for identity theft, but also for social engineering and impersonation.
For that reason, I would much rather keep them encrypted locally and only expose them when I actually need them.
4) Client files and business records
Small businesses and independent technicians often end up handling surprisingly sensitive material, invoices, network notes, customer records, internal screenshots, scanned forms, and troubleshooting documents that were never meant to leave a controlled environment.
That does not mean every business must avoid cloud services entirely. It does mean that some files should be treated differently from routine collaboration files.
If a document would be embarrassing, risky, or professionally harmful if exposed, that is usually a sign it deserves stronger local handling.
5) Private notes that were never meant to sync everywhere
Some files are simply personal. Journal notes, sensitive ideas, draft letters, legal notes, medical reminders, or other private writing may not be world-ending if exposed, but they were never intended to be copied across a whole ecosystem either.
There is a real difference between having a file on your device and having that file mirrored to remote systems, cached on other devices, and tied into account recovery flows you may not think about until something goes wrong.
That is why I still think local-first security matters.
Cloud storage is convenient, not neutral
The cloud is often sold as the default answer because it is easy. Easy does not always mean best.
Every extra sync path, remote copy, account dependency, or shared link creates another place where sensitive information can escape your control. Sometimes that tradeoff is worth it. Sometimes it is not.
If your goal is simply to keep important files encrypted on the device itself, then an offline approach can be the cleaner solution.
Where an offline encrypted vault fits in
That is part of the idea behind Vaelri Vault’s offline encrypted vault for Android. It is built for people who want to encrypt files locally, keep them on the device, and avoid turning simple file protection into another cloud subscription problem.
That will not replace every storage workflow, and it is not supposed to. It is simply a better fit for files that deserve a different standard.
Final thought
I am not arguing that nothing should ever go into the cloud. I am arguing that some files deserve more caution than others.
My rule is pretty simple: if a file could meaningfully hurt me, my family, or my business if it leaked, I would rather keep it encrypted locally unless there is a very good reason not to.
If you want a broader privacy angle on how personal information circulates once it leaves your control, this article is a good next read:
What Is a Data Broker? (And Why They Already Have Your Information)