Is Your Cloud Storage Post-Quantum? Harvest Now, Decrypt Later, Explained

ShieldFive protects new uploads with post-quantum ML-KEM-1024 today; of five other providers checked, only Internxt makes a public post-quantum claim for files. Harvest now, decrypt later in one paragraph, and a sourced table.

Guides ·

On 15 November 2026 Engadget listed post-quantum cryptography among five emerging technologies that may soon become part of everyday life. Your browser and your messaging apps already moved: per that article, Chrome has used the post-quantum ML-KEM key exchange by default since late 2024, Apple has protected iMessage with PQ3 since iOS 17.4, and Signal extended its post-quantum layer to chats in late 2025. The question this page answers is narrower: what about the files you keep in the cloud?

Short answer: ShieldFive protects stored files with post-quantum encryption today; most big providers make no such public claim

New ShieldFive uploads from the web and Android are encrypted on your device with a hybrid of ML-KEM-1024 (NIST FIPS 203, security level 5) and a classical share. Our servers store only ciphertext, and we never hold your keys. The Lifetime plan is 5 TB, paid once.

Of the five other providers below, one (Internxt) publicly claims post-quantum protection for files. For the other four we found no public claim on their own pages.

Harvest now, decrypt later, in one paragraph

An attacker does not need a quantum computer today. They copy encrypted data now and keep it until a machine can break the key exchange that protected it. The dates are getting concrete: Google has set 2029 as its deadline to move its own services to post-quantum encryption, and NIST deprecates RSA and elliptic-curve algorithms after 2030 and disallows them for federal use after 2035. Engadget also reports that Google researchers estimated in March 2026 that elliptic-curve cryptography could be broken with fewer than 500,000 physical qubits. For stored files the protection is decided at upload. You cannot add it later to a copy someone already has.

What each provider says publicly about post-quantum protection for stored files

Checked on each provider's own pages on 16 November 2026. "No public claim found" means we did not find one on the pages listed; it does not mean the provider lacks the feature.

ProviderPost-quantum for stored files (their own words)Source
ShieldFiveYes. ML-KEM-1024 + classical hybrid on new web and Android uploads by default; files encrypted on your device; only ciphertext on our servers; 5 TB Lifetime paid onceWhite paper, llms.txt
InternxtYes, per Internxt: "Kyber 512 post-quantum and AES-256 encryption"; "All files are encrypted with post-quantum and zero-knowledge encryption"internxt.com/drive, help center
Proton DriveNo public claim found. Its security page names elliptic-curve cryptography (Curve25519) and OpenPGPproton.me/drive/security
pCloudNo public claim found. Its encryption page describes client-side encryption without naming an algorithmpcloud.com/encrypted-cloud-storage.html, pcloud.com/security.html
Google DriveNo public claim found for Drive files. Help page describes AES-256 at rest and optional Workspace client-side encryptionGoogle Drive Help
iCloudNo public claim found. Apple's iCloud security overview describes standard protection (Apple holds keys) and Advanced Data Protection (end-to-end)support.apple.com/102651

Where ShieldFive wins, and where Internxt is also post-quantum

Internxt does claim post-quantum file encryption, so the honest comparison is on the details, each from Internxt's own pages:

  • Strength level. Internxt names Kyber-512, the smallest parameter set (NIST level 1). ShieldFive uses ML-KEM-1024, the largest standardized set (NIST level 5), in a hybrid with a classical share.
  • Price for 5 TB, paid once. On 14 November 2026 Internxt's own pages showed its 5 TB lifetime plan at €507 on one page and €663 on another. ShieldFive's 5 TB Lifetime is €249 until 30 November 2026, then €299.

What our post-quantum layer covers, exactly

For files you upload to your own vault, the file key needs two shares: one from ML-KEM-1024 and one from a symmetric key chain that ends at a key derived from your password. For files a client sends you through a request link, the classical share comes from an X25519 exchange, so an attacker has to break both X25519 and ML-KEM-1024. Share links, Send transfers and one-time secrets do not use the ML-KEM layer, and if your account's key on the server does not match the one your device derives, the app writes AES-256-GCM instead and tells you. The crypto core is open source; an external audit is not yet completed. Details are in the white paper and our longer guide, post-quantum encrypted cloud storage.

Keep it simple

Most people do not need to think about quantum computers. If your files have to stay private for ten years or more (legal, medical, financial, family archives), it is worth choosing storage that already uses post-quantum encryption, so the copy anyone could take today is protected too.

ShieldFive Lifetime: 5 TB, paid once, €249 until 30 November 2026. Files are encrypted on your device, we store only ciphertext and we never hold your keys. 30-day full refund.

Frequently asked questions

What does "harvest now, decrypt later" mean for cloud storage?
Someone copies encrypted data today and keeps it until a quantum computer can break the key exchange that protected it. For stored files, the protection you get is the protection that was applied at upload. Files uploaded with classical-only key exchange stay that way in any copy an attacker already holds.
Does ShieldFive use post-quantum encryption on stored files?
Yes. New web uploads (since 17 May 2026) and Android uploads (build 38 and later) use a hybrid format: ML-KEM-1024 (NIST FIPS 203) plus a classical share, with XChaCha20-Poly1305 encrypting the file. Files are encrypted on your device; our servers store only ciphertext and we never hold your keys. If the account key on the server does not match the one your device derives, the app falls back to AES-256-GCM and says so on screen.
Which other providers claim post-quantum protection for stored files?
Of the providers in our table, Internxt says publicly that its files are protected with Kyber-512 post-quantum encryption. For pCloud, Proton Drive, Google Drive and iCloud we found no public claim of post-quantum protection for stored files on their own pages (checked 16 November 2026). That is not the same as saying they lack it; it means they do not say so publicly.
When do quantum computers become a real risk?
Nobody knows the date. What is public: Google has set 2029 as its own target to move its services to post-quantum cryptography, and NIST plans to deprecate RSA and elliptic-curve algorithms after 2030 and disallow them for US federal use after 2035. Engadget reported on 15 November 2026 that Google researchers estimated in March 2026 that elliptic-curve cryptography could be broken with fewer than 500,000 physical qubits.
Is ShieldFive post-quantum encryption audited?
The crypto core is open source (Apache-2.0) and published to npm as @shieldfive/crypto, so it can be read and tested. An external third-party audit has not been completed yet.

Try it free: 10 GB, encrypted on your device.

Create your free account

No card · EU-hosted · upgrade only when you fill it