Cryptography in Everyday Applications
Decide what HTTPS, end-to-end encryption and online payment protections do and do not protect in an everyday situation.
The padlock you see a hundred times a day
On Sunday evening Mrs. Lata Gokhale orders her monthly medicines on the Tulsi Health app over her building's shared Wi-Fi. She types her password, confirms her address in Erandwane and pays ₹1,840 by UPI. Between her phone and Tulsi Health's server, the computer in the cloud that runs the app, her order passes through the building's Wi-Fi router, her internet provider and several other networks run by people she will never meet. Cryptography is what stops any of them from reading or changing it. You use it dozens of times a day without noticing: in the padlock beside a web address, in "messages are end-to-end encrypted" notices, and in every UPI payment.
HTTPS: a sealed courier envelope instead of a postcard
A website is a set of pages kept on a server, and a browser is the app on your phone or laptop that fetches and shows them. They talk using a set of rules called HTTP. Plain HTTP sends everything as readable text, like a postcard: every person who handles it on the way can read it, and could even rewrite it before passing it on.
HTTPS is HTTP sent inside a protective layer called TLS (Transport Layer Security). It turns the postcard into a sealed courier envelope. The people carrying it can see the address on the front, which site you are talking to, but not what is inside, and if anyone tears the envelope open and reseals it, the receiver notices. You can tell a site uses HTTPS by the https:// at the start of its address and the padlock or similar icon beside it.
HTTP is a postcard anyone on the route can read. HTTPS is a sealed envelope: the route still sees the address, but not the contents.
HTTPS gives three protections at once. Confidentiality: nobody on the route can read the content. Integrity: nobody can change it on the way without being detected. Authentication of the server: your browser checks the site's certificate, an electronic ID card for a website, vouched for by a trusted organisation called a certificate authority, so you know you reached the real holder of that name.
How TLS sets up the private line
The clever part is that Lata's phone and the server have never met and share no secret, yet they must agree on one without anyone listening in learning it. TLS solves this with a short opening conversation called the handshake, using two kinds of encryption together. Public-key encryption uses a pair of keys, one public and one private, and lets two strangers agree a secret over an open line. Symmetric encryption uses one shared key on both sides and is very fast, so it carries the actual data once the shared key exists.
Public-key maths sets up a shared secret in the first few messages; fast symmetric encryption then carries everything else. The whole handshake takes a fraction of a second.
What the padlock does not promise
The padlock is widely misunderstood. It means the line is private; it does not mean the shop is honest. Certificates for a domain, the name part of a web address such as tulsihealth.in, are easy and often free to get, and the authority only checks that the requester controls that name. So a criminal who registers tulsihealth-secure.in can get a perfectly valid certificate, and their fake refund page shows the same padlock as the real site.
A private line to a crook is still a crook. Read the name in the address bar, not just the padlock beside it.
HTTPS also protects data only while it travels. Once Lata's order reaches Tulsi Health's servers it is decrypted, so a breach of Tulsi Health's database exposes it no matter how the order was sent. HTTPS cannot help if malware on her own phone records what she types. And the envelope still shows the address on the front, so her building's Wi-Fi owner can see that she visited tulsihealth.in, and when, though not what she ordered. Sort the items below by whether HTTPS actually protects them.
Encrypted messaging and end-to-end encryption
Chat apps add a further step. With ordinary transport encryption, which is what HTTPS gives you, your message is encrypted from your phone to the chat company's server, decrypted there, then encrypted again on the way to your friend. The company's server can read it, and so could anyone who breaks into that server. With end-to-end encryption, often shortened to E2EE, the message is encrypted on your phone with keys that only your phone and your friend's phone hold. The company's server carries a sealed envelope it has no way to open.
The difference is who holds the keys. With end-to-end encryption, only the two ends do.
E2EE is strong, but it protects the journey, not the ends. Anyone holding your unlocked phone can read your chats, a screenshot or a forwarded message leaves the protection behind, and chat backups may be stored without the same protection unless you turn that option on. The service also still knows metadata, data about the message rather than its content: who talked to whom, when and how often. Most importantly, E2EE says nothing about who is typing. A message from a hijacked account is delivered just as privately as a genuine one.
Paying online safely
Secure online payments stack several protections. The UPI app talks to the bank over an encrypted connection, and your UPI account is tied to your registered phone and SIM, so a stranger cannot simply log in from another device. Your UPI PIN is entered on a protected screen and sent encrypted, and it is a second secret on top of the phone itself. Card payments add a one-time password, the OTP, as a second step, and under RBI rules shopping sites in India no longer store your full card number but a substitute value called a token. Tulsi Health's app passes card entry straight to its payment gateway, so Tulsi Health's own database never holds card numbers at all.
None of this cryptography can stop you from approving a payment yourself, which is why payment scams target the person rather than the maths. Make the calls below as if you were helping the Tulsi Health family; each wrong first choice counts as an incident.