What a zero-knowledge proof does
Usually, proving something means showing the evidence: entering a password or handing over an ID card. That can reveal more than the other person needs to know.
A zero-knowledge proof is a cryptographic method that changes this. One person, the prover, demonstrates a precise claim to another, the verifier, without revealing the secret used to make that claim true. The verifier learns the answer they need — for example, that you meet an age requirement — but not your birthday, address, or document number.
It is not a vague promise of privacy. A proof must be designed for one exact claim, and good designs make cheating overwhelmingly unlikely.
The cave example
Imagine a cave with two paths that meet behind a locked door. The door opens only with a secret word. You say you know it, but you do not want to say it aloud.
You enter by either path while your friend waits outside. Your friend then calls out the path they want you to return by. If you know the word, you can open the door inside the cave and return by either path. If you are guessing, you have only a fifty-fifty chance of being on the requested side.
Repeat the test many times with a fresh, unpredictable choice. Ten successful rounds leave a bluffer with about a one-in-1,000 chance of getting lucky. Your friend gains strong evidence that you know the word, but never hears it.
From cave story to real software
Real proofs use mathematics rather than a cave, but the privacy goal is the same. They can show that a transaction follows the rules without exposing all of its details. They can also let one small proof stand in for a large batch of checks, which can make some systems faster to verify.
Digital credentials are another practical use. Instead of uploading an entire ID to every service, a well-designed credential could answer only the question being asked: “Is this person over 18?” or “Do they hold this qualification?”
The details matter. A proof protects only the information it was built to hide. The surrounding app can still collect data, identify you, or make a poor security choice elsewhere.
Zero-knowledge proof vs zero-knowledge encryption
The phrase 'zero-knowledge' is also used in cloud storage. That is a different idea. Zero-knowledge encryption means the storage provider cannot read your files because it does not have the decryption keys.
A zero-knowledge proof answers a question without exposing the secret behind the answer. Zero-knowledge encryption keeps stored files unreadable to a provider. Both can improve privacy, but they are not interchangeable.
A practical privacy lesson
Zero-knowledge proofs are a useful reminder to share the minimum information needed for a task. They do not make you anonymous or secure every part of an app. A service may still know that you connected, when you did it, and other data outside the proof.
Sealby does not need zero-knowledge proofs because it has no account or server asking you to prove something. Files are encrypted on your iPhone. For everyday privacy, the practical question is simple: what does this service actually need to know — and can it work with less?