The padlock on an email means the message was encrypted on its way between mail servers. In Gmail it’s a gray lock, and nearly every message has one. It protects the trip. Once the message lands, it’s stored readable on the recipient’s server, and on every server it reaches after that.
Maya Okafor learned where that line falls on a Friday afternoon. She runs a six-person bookkeeping and tax firm in Columbus. Her account was broken into two weeks ago, and her firm spent this week locking it back down. Then a client asked whether it was safe to email his tax return to his bank.
This part of Point’s series is her answer. It covers what each padlock means, where a sent message actually sits, and the four ways she could get the return there. If you’ve ever looked at that little lock and felt reassured, you read it correctly. It just covers less ground than it seems to.
What the padlock on an email means
Dale Huang’s question came in at 4:40. Maya opened a new message to his loan officer and looked at the lock before typing anything. It was gray.
Google explains that gray lock on its Gmail Help page about encryption:
All Gmail messages use TLS automatically. Think of TLS as a secure mail carrier for your messages.
TLS stands for Transport Layer Security. It’s the same kind of protection a bank’s website uses. A second Google page adds the condition: “For TLS to work, the email providers for both the sender and recipient must use TLS.” Almost every large provider does. When one doesn’t, Gmail shows a red open lock, and Google’s advice is short. Don’t send sensitive information.
Gmail has two more icons, and most small firms rarely see them.
| Icon in Gmail | What Google calls it | What’s encrypted | Who holds a key |
|---|---|---|---|
| Gray lock | Standard encryption (TLS) | The trip between mail servers | Each server along the way |
| Green lock | Enhanced encryption (hosted S/MIME) | The message itself | You, your recipient, and Google |
| Blue shield | Additional encryption (client-side) | The message itself | Your organization only |
| Red open lock | No encryption | Nothing | Anyone on the path |
Outlook uses the lock differently. Microsoft’s support page says “a lock icon on the incoming mail will suggest email is encrypted.” That’s the message itself, sealed with S/MIME or Microsoft’s own encryption.
Six places one tax return would sit
This is the part people most often get wrong. The gray lock isn’t a sealed envelope. It’s a locked truck between two buildings, and the letter comes out of the truck at each one.
The standard behind it says so directly. RFC 3207 defines how mail servers turn TLS on:
It should be noted that SMTP is not an end-to-end mechanism. Thus, if an SMTP client/server pair decide to add TLS privacy, they are not securing the transport from the originating mail user agent to the recipient.
So Maya traced where Dale’s return would go if she attached it and pressed send.
| Where the return sits | Who can read it there | How long it stays |
|---|---|---|
| Maya’s Sent folder, on Google’s servers | Anyone signed in as Maya | Until she deletes it |
| In transit to the bank’s mail provider | Nobody, under the gray lock | Seconds |
| The bank’s mail server | The bank’s provider and its admins | Under the bank’s retention policy |
| The loan officer’s inbox | Kim, and anyone signed in as Kim | Under the bank’s retention policy |
| Wherever Kim forwards it | An underwriter, a processor, a shared folder | Unknown |
| Any phone or laptop that downloads it | Whoever holds that device | Unknown |
The second row is the only one the padlock covers. Rows one and four are mailboxes, and Maya had spent two weeks learning what a mailbox is worth to someone with its password. Rows five and six were out of her sight entirely.
A tax return carries a Social Security number, income, and usually a bank account for the refund. Dale’s would sit readable in at least four places. The padlock would be gray the whole time.
What the rules ask of a tax practice
Maya’s firm prepares returns, so two sets of rules already speak to this.
The FTC Safeguards Rule covers tax preparation firms. Its encryption section, 16 CFR 314.4(c)(3), is one sentence long:
Protect by encryption all customer information held or transmitted by you both in transit over external networks and at rest.
The rule goes on to allow other safeguards where encryption is “infeasible.” Those have to be “reviewed and approved by your Qualified Individual,” the person who runs the firm’s security program. At a six-person firm, that was Maya.
The IRS is more specific about email. Publication 4557, its guide for tax professionals, puts it this way:
Send only password-protected and encrypted documents if you must share files with clients via email or use Secure File Transfer Protocol (SFTP) to transmit files instead of email.
Read together, they settle the question. The gray lock covers the trip. The return still needs its own lock, or a route that skips the inboxes.
Four ways to get a return to a bank
Maya called Dale at 4:55. She asked him to leave the return with her. She’d sort it out with the bank. Then she called Kim, the loan officer, at the number on the bank’s website.
Between the two calls, she had four options.
| Option | What protects the return | Where copies end up | What it asks of Dale and the bank |
|---|---|---|---|
| Plain email attachment | The gray lock, for the trip only | Readable in both mailboxes and anywhere it’s forwarded | Nothing |
| A password-locked PDF, password by phone | The file’s own encryption | Locked in every mailbox it passes through | One phone call |
| The bank’s own upload portal | The bank’s website connection, then the bank’s systems | In the bank’s loan file | An address Maya trusts |
| An IRS transcript through IVES | It stays out of email | With the IRS and the lender | Dale’s signature on Form 4506-C |
The last row was Kim’s suggestion. Many lenders can get income records straight from the IRS. The IRS Income Verification Express Service lets a taxpayer authorize “banks, credit unions, and others” to receive a transcript, using Form 4506-C. A transcript is a summary of the return. Kim’s underwriter wanted the full return with its schedules, so that settled it for this loan. It’s worth asking about next time.
Encrypted email was the option Maya checked first. Gmail’s green lock needs hosted S/MIME, which Google offers on its Enterprise Plus, Frontline Plus and Education editions. Both sides also need to “exchange keys” first. In October 2025, Google added a way for client-side encryption users to email anyone. That needs Enterprise Plus with an add-on. The firm is on a Business plan, so both were out of reach. Gmail’s confidential mode seals less than it sounds. As the EFF pointed out, those messages “are not end-to-end encrypted.” Encrypted email, and what an AI assistant cannot read covers what each kind of encryption protects, if you want the full picture.
The password went by phone
Kim’s bank had a portal. Maya asked for the address on the call rather than in an email. After this week, any upload link arriving by email looked like a risk. She typed it in herself on Monday morning and uploaded the return at 9:05.
She made the backup option the firm’s default too. Any file with a Social Security number goes out locked. The password never travels in the same channel as the file. If the file goes by email, the password goes by phone or text, said once and kept out of the thread.
That choice had a cost Maya had already thought about. In part two she’d turned down a provider that would have sent every client a link and a password. Her reasoning then was that it made phishing look normal. A locked PDF is different in one way that matters. Nothing in the email asks the client to click or sign in. They open a file they were expecting, with a password Maya gave them out loud.
Jess, who runs the front desk, asked the obvious follow-up. What about everything else? Engagement letters, meeting times, a question about a receipt? Those stay as ordinary email. The gray lock is enough for a message that would be harmless in a stranger’s hands. The rule covers the rest.
What a sent email can’t take back
Ben asked the last question of the afternoon. What if someone sends a return to the wrong Dale?
The honest answer is short. Once a message reaches another provider’s server, it’s out of your hands. Gmail’s Undo Send works only because it waits before sending, for “5, 10, 20, or 30 seconds.” After that, the message is gone.
Outlook’s recall feature sounds like more than it is. Microsoft’s support page limits it to recipients “in the same organization,” and only if they haven’t opened the message yet. A bank or a client is outside its reach.
So the firm set Undo Send to 30 seconds for everyone. A mistyped name is a more likely leak than anything on the wire, and 30 seconds is enough to catch most of them. The locked PDF covers the rest. A return sent to the wrong person arrives as a file that stays locked.
Monday at 9:05
The upload page showed a green check. Kim confirmed by phone at 9:20. Dale’s return was in the loan file, and nowhere in anyone’s inbox.
Maya wrote the week down on one page for the firm’s records:
- Who can sign in: everyone, with passkeys.
- Who else holds a key: six apps, no delegates, no forwarding.
- What leaves the firm: anything with a Social Security number goes out locked or through a portal. Passwords go by phone.
- What can’t come back: a sent email. Undo Send is set to 30 seconds.
Each line was something she could check. For the first time since the Saturday it started, every question on the page had an answer.
At 11:40, Jess got an email from the bank. It said Dale’s upload had failed and asked her to send the file again using the link below. It had the bank’s logo and Kim’s name. It had a gray padlock, like every other message that morning. The standard behind that padlock says plainly it’s “not suitable for authenticating the author of an email message.” Before she thought about any of that, Jess had the link from the one that got through open in a new tab.