Why People Are Leaving Google Drive for Zero-Knowledge Storage

A senior AI policy advisor named Kevin Bankston opened Google Drive in 2024 and found that Gemini had already summarized a private tax return sitting in his files. He never asked it to. He also had trouble finding the setting to turn the feature off. His experience became one of the more widely cited examples of a discomfort a lot of people have been quietly sitting with: the files in your "personal" cloud storage are not entirely personal, and the company hosting them decides what happens to them next.

What "Google can read your files" actually means

Google Drive encrypts your files, but it is not zero-knowledge encryption. The distinction matters more than it sounds like it should: with zero-knowledge encryption, only you hold the key that unlocks your data, and the storage provider physically cannot read it even if ordered to. With Google Drive, Google holds the keys. That is what lets Drive index your files for search, scan attachments for malware, and, since Google folded Gemini into Workspace, let its AI read and summarize document contents by default.

This is not a hypothetical risk. In October 2025, Google enabled Gemini's "Smart Features" by default across Gmail, Chat, and Meet for roughly 1.8 billion users without an opt-in prompt, a change that became the basis of a class action, Thele v. Google. A federal judge later dismissed the case for failing to show concrete harm, while giving the plaintiffs room to file an amended complaint, so the legal question of whether this counted as unauthorized access is still unsettled. What is not in dispute is what Google did: it changed the default for over a billion accounts without asking first.

At the account level, cybersecurity firm Metomic scanned 6.5 million Google Drive files in a 2023 audit and found 40.2% contained sensitive data, with 34.2% of files shared outside the owner's organization and roughly 350,000 files, about 0.5% of the total, openly accessible to anyone with the link. Read Metomic's full findings here. None of that requires a hack. It is what happens when a storage system built for convenience gets used, correctly, by millions of people who never audited their own sharing settings.

The single point of failure: when Google gets it wrong

The scariest version of this story is not a data leak. It is Google's own detection systems making the wrong call, because your entire digital life sits behind one login.

In February 2021, two fathers, one in San Francisco and one in Houston, photographed their young sons' genital infections at a doctor's request so a physician could review them remotely. Google's automated scanning flagged the photos as child sexual abuse material, reported both men to the National Center for Missing and Exploited Children, and permanently suspended their Google accounts, wiping years of email, photos, videos, and in one case, phone service tied to the account. Both police departments investigated and cleared the fathers within days. Google did not restore either account. The Electronic Frontier Foundation has the full account here.

The technical failure was narrow: an AI classifier misread medical photos. The damage was not narrow at all, because Google Drive, Gmail, Google Photos, and often a Google Fi phone number all sit behind the same account. One false positive took out all of it at once, with no functioning appeal. That is the actual argument for splitting your digital life across more than one company: not that Google is uniquely malicious, but that a single provider being both your storage and your identity means their mistake becomes your outage.

What zero-knowledge encryption actually changes

Zero-knowledge encryption means your files are encrypted on your device before they ever leave it, using a key derived from your password that the provider never receives. NordLocker describes its own implementation here: it combines AES-256, xChaCha20-Poly1305, and Ed25519 encryption, and unlike an optional setting, it is the default for every file, not an upgrade you have to configure correctly. Practically, that means nobody at NordLocker, and nobody who successfully compels NordLocker to comply with a request, can hand over readable copies of your files. There is nothing readable to hand over.

This is not a claim that Google Drive is malicious or that NordLocker is invulnerable. It is a different threat model. Google Drive optimizes for integration: search, AI features, seamless sharing across a billion-user ecosystem. NordLocker optimizes for one property, that the provider itself cannot read your data, which is exactly the property that matters for medical records, financial documents, family photos, or anything you would rather not have summarized by an AI feature you did not turn on. If that's the file category you're trying to protect, moving it into NordLocker closes the gap Google Drive is structurally unable to close.

The other half: the password that unlocks everything

Encrypted storage solves half the problem. The other half is that most people's Google account, the one holding all of this, is protected by a password they have reused somewhere else. NordPass data puts the average person at around 120 personal passwords plus another 67 for work, and a 2025 survey by 360 Research Reports found 78% of people who adopted a password manager did it simply because they were drowning in passwords they could no longer track safely. Bitwarden's 2025 World Password Day survey found Gen Z reusing the same password across accounts at a 72% rate, the highest of any generation.

A reused password is the fastest route to exactly the single-point-of-failure problem described above: one breached site leaks a password, that password unlocks your Google account, and now the same account that holds your files also holds your email, your recovery options, and every service tied to that login. A dedicated password manager like NordPass uses the same zero-knowledge principle as NordLocker: your vault is encrypted with a master password only you know, so a breach at the vendor does not hand anyone your logins. Pairing zero-knowledge storage for your files with a zero-knowledge vault for your passwords means no single compromised account can cascade into everything you own online.

A practical way to actually do this

You don't need to delete your Google account or migrate every file you own. That is how these projects stall out. A more realistic approach:

1. Sort files by what would actually hurt if exposed or auto-summarized. Tax returns, medical records, ID scans, financial statements, family photos. Shared meeting notes and non-sensitive documents can stay wherever they already live.
2. Move the sensitive category first, not everything at once. A focused move of the handful of folders that actually matter takes an afternoon. A full migration of a decade of Drive clutter takes a project you'll abandon in week one.
3. Separate your password vault from your Google login. If your passwords currently live in Chrome's built-in manager tied to your Google account, that's the same single-point-of-failure problem in a different shape. Move them to a standalone vault.
4. Keep two-factor authentication on, but don't make Google your only recovery path. Use an authenticator app or a hardware key rather than SMS to a number that could itself be tied to the same account.

Frequently asked questions

Does this mean Google Drive is unsafe to use?

Not unsafe in the sense of being likely to get hacked. Google's infrastructure security is generally strong. The concern here is different: Google, not you, holds the keys, which means Google's own systems (AI features, automated scanning, account enforcement) can read, act on, or lock down your files even when nothing was ever breached.

What does "zero-knowledge" guarantee that regular encryption does not?

Regular encryption at rest protects your files from outside attackers who don't have the provider's keys. It does nothing against the provider itself, or anyone who legally compels the provider. Zero-knowledge encryption removes that exception: the provider never has a readable copy to begin with.

Can I still share files if I move them to zero-knowledge storage?

Yes. Zero-knowledge providers support sharing through separate encrypted links or invites, the same way Drive does. The difference is what happens to a file before it is deliberately shared, not whether sharing is possible.

What happens if I forget my zero-knowledge master password?

The same protection that keeps the provider out also means there is no "forgot password" reset that decrypts your data for you. Most services offer a recovery key you generate and store separately at setup. If you lose both the password and the recovery key, the files are unrecoverable, which is the direct tradeoff of nobody else being able to unlock them either.

Is this only relevant if you have something to hide?

The two documented incidents above involved a routine tax return and a father photographing a medical condition at his doctor's request, neither remotely illicit. "Nothing to hide" assumes the system correctly identifies what it's looking at. The CSAM false-positive cases are the clearest evidence that assumption doesn't always hold.

Conclusion

The people moving files off Google Drive are not, for the most part, reacting to a breach. They're reacting to the accumulating evidence that "free" and "convenient" come with a specific tradeoff: Google can read what you store, its AI now does so by default in several products, and when its automated systems get it wrong, there is no reliable way back in. Zero-knowledge storage and a separate password vault don't eliminate risk. They remove one very specific failure mode: a single company, and a single mistake, taking down everything you have stored with it at once.

Related reading: AI security mistakes you are probably making right now and the complete ransomware defense guide for 2026.