Your files are encrypted before they leave your device.
We store ciphertext and never hold your keys. ShieldFive is self-funded, paid for only by its customers, hosted in the EU, and the cryptography that protects your files is open source.
- No investors
- Paid for by customers only
- EU-hosted
- Operated from Spain
- Open source
- Crypto library, CLI, MCP
- 30-day refund
- On every paid plan

Why I built ShieldFive
Cloud storage kept adding AI features that need a readable copy of your files. The model I wanted, store an encrypted blob, keep the key with its owner and leave it alone, barely existed outside a niche, and the products that came closest each had specific gaps.
If a readable copy of your files exists on a server, someone can ask for it. So ShieldFive is built so that copy doesn't exist, and the Security page says exactly where that guarantee ends.
I kept the cryptography in its own public library on purpose, so anyone can read exactly what runs in the browser before a file is uploaded. I answer support email myself.
Customers pay for it. Nobody else does.
Who funds a company decides what it is pushed to do. ShieldFive has no investors, no ads and no data deals, so the only way it earns money is a subscription or a Founding Lifetime.
No ads, no tracking pixels
Nothing in the app reports what you store or open.
No AI training
The servers hold ciphertext, so there is nothing to train on.
No lock-in
Any file downloads decrypted, whenever you like, and the file format and decryption code are open source.
What our servers hold, and what stays with you
Stays on your device
- The keys that open your files
- Your password: sign-in sends a key derived from it in the browser, not the password
- Readable file contents and file names
Held on our servers
- Your files and their names, as ciphertext
- Your account email and plan
- File sizes and timestamps, to sync reliably
One limit every browser-based encrypted service shares: we serve the code that does the encrypting. The Security page explains it in full.
Everything you need to check us is public
There is no external audit yet; it is on the roadmap. Until then, the code and the review are open for anyone to read.
Shaped by the people who use it
“I chose ShieldFive because it doesn't just promise privacy—it implements the post-quantum cryptography (PQC) necessary to protect data against future threats. It's a breath of fresh air to find a developer who is actually moving the needle on quantum-resistant storage.”
Security researchers credited
Mudit Raj, 0xEr3n, Aravind S, andzis11, koalarajin, NH Limon and 0xanarki reported issues that are now fixed. Every report is listed on the Security page.
Found a bug? Report it and we'll credit you.
Where to find us
- [email protected]