Cryptography Basics: How Encryption Protects You
You rely on encryption dozens of times a day without noticing. Here's a practical, non-mathematical explanation of how it works and why it matters for secure design.
Encryption↗ quietly protects nearly everything you do online, the padlock icon in your browser, your messaging app, your banking app. Understanding the basic concepts (without needing the underlying mathematics) helps you make better decisions about which tools and practices actually keep data safe.
Two core concepts
Encryption in transit vs. at rest
Encryption in transit protects data while it moves between two points, for example, between your browser and a website (this is what "https" and the padlock icon indicate). Encryption at rest protects data while it's stored, on a hard drive, in a database, or in cloud storage. A system can have one without the other, so it's worth knowing which protection actually applies to your situation.
Symmetric vs. asymmetric encryption
Symmetric encryption↗ uses the same key to lock and unlock data, fast, but both parties need to already share that key securely. Asymmetric (public-key) encryption uses a matched pair of keys: a public key anyone can use to encrypt a message, and a private key only the recipient holds to decrypt it. This solves the problem of sharing a secret key over an insecure channel, and underpins technologies like passkeys and end-to-end encrypted messaging.

End-to-end encryption↗, explained simply
"End-to-end encryption" means only the sender and intended recipient can read a message, not even the service provider carrying it can access the content. This is the strongest practical privacy guarantee available for everyday communication, and it's why some messaging apps advertise it as a headline feature.
Why this matters for secure design
Good security architecture doesn't try to invent new cryptography, it uses well-established, publicly reviewed encryption standards correctly. Common mistakes in secure design include: storing passwords in plain text instead of hashing↗ them, using outdated encryption algorithms that have known weaknesses, or encrypting data but storing the encryption key↗ alongside it (which defeats the purpose entirely).
Practical takeaways
- Always check for "https" (not just "http") before entering sensitive information on a website.
- Prefer messaging apps that offer end-to-end encryption by default for sensitive conversations.
- Understand that encrypted data is only as safe as the key protecting it, a strong lock is meaningless if the key is left under the doormat.
You don't need to understand the mathematics of cryptography to benefit from it, you just need to recognize when it's being used correctly, and when it isn't.