Skip to content

Sending securely when the other side has nothing set up

On this page

You can send a secure email to someone who has nothing set up. They don’t need an encrypted mail account, an app or a certificate. Three methods reach anyone with an inbox and a web browser: Outlook’s Encrypt button, Gmail’s confidential mode, and a password-protected file with the password sent another way. The choice comes down to the person, not the technology.

So start with them. Can they find a code in their inbox within 15 minutes? Do they share an inbox with family? Will they pick up the phone? Those answers pick the method. The rest of this page goes through what each method asks of someone with nothing, where it trips people up, and what to say before you send.

If you haven’t yet worked out which method your own account has, how to send a secure email, whatever you send it from sorts that out by plan.

What each method asks of someone with nothing set up

Every method below works with an ordinary Gmail, Yahoo, AOL, Comcast or work address. What changes is the work on their end, and the point where a careful person gets stuck. We read each row off Google’s and Microsoft’s help pages on October 4, 2026.

MethodWhat arrivesWhat they doWhere it trips people up
Outlook Encrypt (Microsoft 365)An email saying you’ve sent a protected messageClick to read, then sign in with Google or Yahoo, or ask for a one-time code by emailThe code lands in junk. The code expires after 15 minutes
Gmail confidential mode, no SMS passcodeA link in place of the messageGmail users open it. Everyone else gets a passcode by emailThe passcode goes to the same inbox as the link
Gmail confidential mode, SMS passcodeA link in place of the messageEnter a code texted to their phoneTheir number must be in a supported region. You need their mobile number
Password-protected PDF or Office fileAn ordinary email with an attachmentOpen the file and type the password you gave themThey lose the password, or it arrives in the same email
A call, with nothing sensitive in writingA short email saying you’ll callAnswer the phoneNothing sensitive is written down for either side

The Outlook flow comes from Microsoft’s own pages. Google and Yahoo users can “authenticate using your Google or Yahoo account or by using a temporary passcode,” and people on Comcast, AOL or anything else get the passcode by email. Microsoft says “each passcode expires after 15 minutes.” Its Message Encryption FAQ says a non-Microsoft recipient can “read and reply to encrypted messages on the web through your web browser,” with no download. That reply comes back to you encrypted too, which matters if they need to send something back.

Gmail’s flow is in Google’s confidential mode help. Without the SMS option, “if the recipient does not use Gmail, they get an email with the passcode.” Their copy holds a link in place of your message, and Google’s admin help says third-party mail apps show that link rather than the content. The step-by-step for turning each one on is in sending a secure email from Gmail and the Outlook guide.

What the code in their inbox does, and doesn’t, guard

Most of these methods email a code to the same address the message went to. That’s worth understanding, because it decides who the code keeps out.

The code proves that whoever opens the link can also read that inbox. So it guards against a forwarded link, a mistyped address that happens to exist, and a copy sitting somewhere along the way. It can’t tell two people apart who share one inbox. A couple who read the same AOL account both get the code.

When the inbox itself isn’t private, move the second step out of it:

  • In Gmail, choose the SMS passcode. Google sends it only to numbers in certain regions: “North America, South America, Europe, Australia, Asia: India, Korea, and Japan.”
  • From any account, use a password-protected file and say the password on a call. The file can travel by email, because the password never does.
  • For a single number, like an account or routing number, skip the email and read it out on the phone.

Outlook’s portal has no texted code for a recipient with nothing set up. Their choices are a Google or Yahoo sign-in, or the code by email. For a shared inbox, the file-and-phone route is the stronger choice from Outlook too.

Matching the method to the person

Here’s how that plays out with the people a small firm actually writes to.

  • An older client who reads mail on a phone. A password-protected PDF is usually the gentlest. Their phone opens it in the mail app, and the only new step is typing a password you just told them. A portal, a code and a 15-minute clock is three new things at once.
  • Someone on Comcast, AOL or a local internet provider. Outlook’s portal and Gmail’s link both work, with an emailed code. Tell them to check junk first. Microsoft’s own FAQ says the code email can be filtered as spam.
  • A couple or family on one shared address. Use Gmail’s SMS passcode to the right person’s phone, or the file with the password said aloud. An emailed code reaches everyone who reads that inbox.
  • A contact at another company. Their filters may hold a portal notice or strip a link. A protected Office or PDF file usually gets through, and their IT team is used to it.
  • Someone outside the SMS regions. Gmail’s texted code won’t reach them. The protected file with a password by phone or messaging app works anywhere.
  • Someone who never clicks links in email. That’s a good habit, and it’s worth respecting. Send the file, or call.

If they need to send something sensitive back, the Outlook portal handles that, because their reply stays encrypted. Their reply to a confidential mode message or a protected file goes back as ordinary email. Ask them to call you instead of typing it into a reply.

The heads-up before you send

A protected message from someone who’s never sent one before can look like a phishing email. A short note ahead of time fixes that, and it’s the single step most likely to get the message read.

Send it by text, or say it on a call, so it arrives by a different route from the message. Cover three things:

  1. That it’s coming, and from which address. “I’m sending your return from jane@yourfirm.com in the next five minutes.”
  2. What they’ll be asked to do. “It’ll ask for a code. The code comes in a second email, and it might be in junk.”
  3. What you won’t ask. “I won’t ask for your bank login or your Social Security number in that email.”

The third line protects them later as well. A client who knows how you send things is harder to fool with a fake one.

For a password-protected file, the heads-up is also how the password travels. Never put it in the same email as the file, or in a follow-up email to the same inbox. A file, not an attachment covers making the file and choosing a password they can type on a phone.

When it won’t open

Most failures are small, and each one has a fix that keeps the message protected.

  • No code arrived. It’s usually in junk or spam. If it isn’t there, they can start over from the original email and ask again.
  • The code stopped working. Microsoft’s codes last 15 minutes. They start again and use the newest code.
  • The link says the message has expired. Your confidential mode expiry passed. Send a fresh one with a longer date.
  • The file is too big. Microsoft caps encrypted messages at 25 MB, attachments included. Split the file, or share it as a link.
  • They can’t open the PDF. A preview pane may show a blank page instead of asking for the password. Ask them to save the file and open it in their phone’s files app or Adobe Acrobat Reader.
  • They’re stuck and frustrated. Call them. Five minutes on the phone is better than a second attempt by email.

The one move to avoid is resending it unprotected because the protected copy was a hassle. If they really want plain email, the next section covers when that’s allowed and how to write it down.

When they ask you to just email it

Some people will say they don’t want the code or the password. They want it in a normal email. Whether you can do that depends on the rules that govern your work.

Health practices. HHS addressed this directly in the 2013 HIPAA Omnibus Rule. Its answer is in the Federal Register preamble at 78 FR 5634:

We clarify that covered entities are permitted to send individuals unencrypted emails if they have advised the individual of the risk, and the individual still prefers the unencrypted email.

So a patient who’s been told of the risk can choose plain email for their own records. HHS adds that it “merely” expects you to say there’s “some level of risk that the information in the email could be read by a third party.” That fits with the right of access in 45 CFR 164.524(c)(2)(ii), which requires the electronic format the patient asks for when it’s readily producible. Write down the warning and their answer in the chart.

Tax and accounting firms. The Safeguards Rule from the FTC, 16 CFR 314.4(c)(3), requires encryption of customer information in transit. It has one way out:

To the extent you determine that encryption of customer information, either in transit over external networks or at rest, is infeasible, you may instead secure such customer information using effective alternative compensating controls reviewed and approved by your Qualified Individual

That’s a firm-level decision by the person who runs your security program. A client’s preference on its own isn’t the same thing. For a tax firm, the safer answer to “just email it” is the phone, or a protected file with the password said aloud.

Everyone else. The broader rules for lawyers and others are in when the law expects more. Whatever applies, the habit is the same. If you send plainly at someone’s request, note who asked, when, and that you told them the risk.

Sending less

The safest sensitive detail is the one that never goes in an email at all. A lot of what feels urgent to send can travel in a smaller form.

  • Account numbers. Use the last four digits in writing, and give the full number on a call.
  • Social Security numbers. Use the last four when you only need to say which return or which person you mean.
  • Whole documents. Send only the pages they need, and keep the full packet for a meeting.

Less in the message also helps if something goes wrong later. No method here pulls a message back once it’s on someone else’s server. Expiring a message covers what expiry and revoking access can still reach. Sent it to the wrong person already? Then the hour after a wrong recipient email walks through what to do.

How Point fits the message that needs care

Point connects to your Gmail or Outlook mailbox. When a client asks for something sensitive, Point drafts the answer in your voice. By default, that draft waits for you. Point doesn’t encrypt mail. The protected copy goes out from your own Gmail or Outlook, with the method that suits this client.

What Point can take off your plate is the plain part. You can tell Point once how you handle sensitive details, such as “keep account numbers out of drafts, and offer to call.” Your drafts then follow that preference. When a client hasn’t answered the protected message, the thread stays on your list of replies you’re waiting on. That’s your cue to pick up the phone. What Point does covers the rest of the day.

Common questions

Can I send an encrypted email to someone who doesn’t have encryption?

Yes. Use a method that works through a web browser or an ordinary file. Outlook’s Encrypt button sends them to a web portal with a one-time code. Gmail’s confidential mode sends a link and a passcode. A password-protected PDF works from any account, as long as you give the password by phone or text.

Does the recipient need special software to open an encrypted email?

No, for the methods most small firms use. Microsoft says people outside Microsoft 365 can read and reply in a web browser with no download. Gmail’s confidential mode opens as a link. A password-protected PDF opens in the reader already on their phone or computer.

Why didn’t the recipient get the passcode?

It’s usually in their junk or spam folder. Microsoft’s own FAQ says these code emails can be filtered as spam. Microsoft’s codes also expire after 15 minutes, so they may need to request a fresh one and use it right away.

Is it safe to email the password for a protected file?

No. If the password goes to the same inbox as the file, anyone who can read that inbox can open the file. Say the password on a call or send it by text, so the file and the password travel separately.

Can I send unencrypted email if the client asks me to?

It depends on your field. HHS says health practices may send patients unencrypted email after warning them of the risk, if the patient still prefers it. The FTC Safeguards Rule for tax preparers requires encryption in transit unless your Qualified Individual approves alternative controls. Either way, write the request down.

What if the person shares an email account with someone else?

An emailed code reaches everyone who reads that inbox, so it won’t keep a spouse or family member out. Use Gmail’s SMS passcode to the right person’s phone, or a password-protected file with the password said on a call.

Ready for a calmer inbox?

Join the private beta

We're onboarding a few teams at a time. Leave your email, confirm it once, and we'll send an invitation the moment a place opens.

By joining you agree to our privacy policy.

Private beta

What you're joining

It runs on the mail you have

Point sits on top of Gmail or Outlook. Your address, your history and your contacts stay exactly as they are, so there is nothing to migrate.

You set how much Point does

Out of the box everything waits for your review, replies included. You hand over only what you trust, one kind of work at a time.

Join the private beta

We're onboarding a few teams at a time. Leave your email, confirm it once, and we'll send an invitation the moment a place opens.

By joining you agree to our privacy policy.