Skip to content

Secure cloud email, and where your mail actually sits

On this page

Secure cloud email is a mailbox that a provider hosts for you, with your stored mail encrypted on its servers. That much is true of Gmail and Outlook already. What separates one secure cloud mailbox from another is who holds the key that turns the stored mail back into readable text. If the provider holds it, the provider can read your mail when it needs to. If only you hold it, the provider stores mail it can’t open.

  • Gmail and Microsoft 365 encrypt stored mail with keys they manage. That protects against stolen disks and outsiders, not against the provider.
  • Business plans can add keys you control. Some of those the provider still uses to run search and spam filtering. A few it can’t use at all.
  • Zero-access providers like Proton and Tuta encrypt stored mail with a key only you hold.
  • A secure email gateway is something else. It filters mail on the way in and holds no mailbox of its own.
  • Self-hosting puts every key with you, along with every job the provider used to do.

This page walks through each arrangement, what the provider can and can’t reach in it, and what that means for a small firm.

What is secure cloud email?

The phrase gets used for two different products, and search results mix them freely.

The first is a cloud-hosted secure mailbox. Your mail lives on the provider’s servers, encrypted, and you read it in a browser or an app. Proton Mail, Tuta and an encrypted Microsoft 365 or Google Workspace setup all sit here.

The second is cloud email security. That’s a filtering service that sits in front of a mailbox you already have and screens what comes in. Most of the vendor pages ranking for this term sell the second kind. It’s a real and useful product. It just answers a different question: what reaches your inbox, rather than who can read what’s stored there.

This page is about where the mail sits. So it starts with the mailbox, and comes to gateways once the key question is clear.

Five places your mail can sit

Every arrangement comes down to two things. Where the stored copy lives, and who holds the key to it.

ArrangementWhere your mail is storedWho holds the keyCan the provider read stored mail?Examples
Standard cloud mailboxProvider’s data centersThe providerYes, when its systems or approved staff need toGmail, Outlook, Microsoft 365, Google Workspace
Cloud mailbox, your key, provider still uses itProvider’s data centersYou, with the provider authorized to use itYes, for the services you authorizeMicrosoft Purview Customer Key
Cloud mailbox, your key, provider can’t use itProvider’s data centersYou, through a key service the provider can’t reachNo, for messages encrypted this wayGoogle Workspace client-side encryption, Microsoft Double Key Encryption
Zero-access cloud mailboxProvider’s data centersYou, through a key unlocked by your passwordNo, for message bodiesProton Mail, Tuta
Self-hosted serverA server you or your IT firm runYouThere’s no provider to read it, only whoever runs the serverYour own mail server, on your premises or rented

A gateway doesn’t appear in the table because it isn’t a place mail is kept. It’s a checkpoint mail passes through. It gets its own section below.

One thing holds across all five rows. Mail you send to a client on Gmail sits in their Gmail too, under Google’s keys. Your arrangement governs your copy. Theirs governs theirs.

When the provider holds the key

This is where most business mail lives. It’s encrypted at rest, and the provider manages the keys.

Microsoft states the baseline in its Customer Key overview (checked October 4, 2026):

Your Microsoft 365 data is always encrypted at rest using BitLocker and Distributed Key Manager (DKM).

A few lines later it adds, “By default, Exchange mailboxes are encrypted using Microsoft-managed keys.” Google’s position on Workspace is the same shape. Its client-side encryption page describes that feature as a layer “in addition to the default encryption that Google Workspace provides.”

What this protects is real. A stolen drive from a data center is unreadable. So is mail intercepted between data centers. What it doesn’t do is keep the provider out, because the provider’s own systems need to read mail to run the service. Spam filtering, search and malware scanning all work on readable text.

People access is a separate matter, and Microsoft documents it in detail. Its Customer Lockbox page says “no Microsoft personnel have permission to access customer content on an ongoing basis.” Engineers request temporary access through an internal approval system, and approved access lasts four hours at most. Customer Lockbox adds one more step: your own admin has to approve the request too.

Customer Lockbox ensures that Microsoft can’t access your content to do service operations without your explicit approval.

That puts you in the approval chain for support access. Customer Lockbox comes with Microsoft 365 E5, or as an add-on to other plans. Microsoft’s own FAQ is clear on its limit. Asked whether it protects against law enforcement or other third-party requests, the answer is no.

When you hold a key the provider still uses

Microsoft 365 offers a middle step called Customer Key. You supply the root keys that encrypt your mailboxes, and Microsoft wraps your data in them. It sounds like the provider is locked out. The documentation describes something narrower:

You explicitly authorize Microsoft 365 to use your encryption keys to deliver value-added services like eDiscovery, anti-malware, anti-spam, and search indexing.

So Microsoft still reads your mail to run the service. What you gain is the off switch. Microsoft says “revoking access to your keys triggers deletion of the availability key, resulting in cryptographic deletion of your data.” That’s useful for compliance and for leaving cleanly. It isn’t the same as the provider being unable to read your mail.

Customer Key also stops at the cloud. Microsoft notes it “doesn’t protect on-premises mailboxes or files.”

When you hold a key the provider can’t use

Both big providers sell a version where the key lives somewhere the provider can’t reach.

  • Google Workspace client-side encryption. Google says CSE uses “end-to-end encryption that Google servers and third parties can’t decrypt.” The keys sit with an external key service your organization chooses. Google lists it on Frontline Plus, Enterprise Plus, Education Standard and Education Plus.
  • Microsoft Double Key Encryption. Protected content needs two keys to open: one in Microsoft Azure and one you hold. It comes with Microsoft 365 E5. The plan details for both are in what secure email means.

The trade is that anything Google’s servers did with readable text stops working for those messages. Google’s user experience overview says “some Gmail features aren’t available with client-side encrypted email.” It names two that a small firm would notice: “Email delegation (shared inboxes) isn’t available with Gmail CSE,” and CSE “isn’t available with email aliases.”

Both options also apply to messages someone chooses to encrypt. The rest of the mailbox stays under the provider’s keys.

When the mailbox is zero-access

Zero-access providers encrypt everything you store with a key derived from your password. The provider keeps the encrypted copy and never holds the key to open it.

Mail from Gmail can’t arrive pre-encrypted, so there’s a brief moment where the provider sees it. Proton describes what happens next on its zero-access encryption page:

we encrypt it immediately using your Proton Mail public encryption key. Afterward, only you can decrypt the encrypted email.

Tuta describes the same step. Its encryption page says mail from outside senders isn’t end-to-end encrypted and is “only encrypted once they reach our servers.”

The two differ on what’s left readable. Tuta encrypts subject lines and attachments along with the body:

The only unencrypted data are mail addresses of users as well as senders and recipients of emails.

Proton encrypts subject lines in storage, but not end-to-end. That difference, and what Proton can hand over under a Swiss court order, is set out in what secure email means. Both keep sender and recipient addresses where the provider can read them. Mail can’t be delivered otherwise.

The cost is the same one Google’s CSE carries. A provider that can’t read your mail can’t search it on its servers or filter it the way Gmail does. The full list of trade-offs for Proton is in what secure email means, and the providers are compared in the secure email companies.

Where a gateway fits

A secure email gateway is a filtering service your mail passes through on its way to the mailbox. The mailbox itself stays where it was, usually Microsoft 365 or Google Workspace.

There are two common ways to connect one. Microsoft’s own documentation describes both.

  • In front of the mailbox. Your domain’s MX record, the DNS entry that tells the world where to deliver your mail, points at the gateway instead of the mailbox. Microsoft’s mail flow guide puts it plainly: “Your domain’s MX record must point to your third-party service provider.” Every message reaches the gateway first.
  • Inside the mailbox, by API. The service connects to the mailbox and scans mail after it arrives. Microsoft’s integration guide adds a warning worth reading twice:

This integration typically requires granting the non-Microsoft service full access to mailboxes. Be sure to understand the security and support practices of the non-Microsoft service before granting this permission.

So a gateway adds a company to the list of who can read your mail. It needs readable text to judge a message. Most also hold copies of what they quarantine. That’s a fair trade for better filtering, as long as you count the vendor among the parties who see your mail.

A gateway also leaves stored mail as readable to your mailbox provider as it was before. Microsoft’s guide carries a line that applies to every layer on this page: “No matter how many layers of email protection exist, total protection never reaches 100 percent.” The gateway vendors themselves are grouped in the secure email companies.

When the server is yours

Self-hosting means running your own mail server, in your office or on a rented machine. No provider holds a key, because there’s no provider. The server holds your mail, and you hold the server.

That shifts the risk rather than removing it. Whoever can get into the server can read what’s on it, unless you’ve added encryption on top. Every patch, backup and spam filter becomes your job, or your IT firm’s.

Sending is the part that surprises people. Gmail sets rules for anyone delivering mail to its users. Its sender guidelines say all senders must:

  • Set up SPF or DKIM for the sending domain
  • Use a TLS connection to deliver mail
  • Have valid forward and reverse DNS records, called PTR records, for the sending IP
  • Keep spam rates in Google’s Postmaster Tools below 0.3%

A server that misses any of these risks having its mail land in spam or be refused. The big providers handle this for you. On your own server, it’s yours to keep in order. What the domain records do is covered in a secure address on your own domain.

What a court order reaches

For a US provider, where the data center sits doesn’t decide what it must hand over. The CLOUD Act amended the Stored Communications Act, and 18 U.S.C. § 2713 says a provider shall disclose what’s in its “possession, custody, or control”:

regardless of whether such communication, record, or other information is located within or outside of the United States.

Choosing a European data center for a US provider’s mailbox doesn’t change this. What changes it is the key. A provider can only hand over what it can read. Under provider-held keys, that’s everything. Under client-side or zero-access encryption, it’s the encrypted bodies plus the metadata it needs to deliver mail: addresses, times and, for some providers, subject lines.

Providers based outside the US answer to their own courts instead. Proton’s position under Swiss law is covered in what secure email means.

What the provider can reach, arrangement by arrangement

What the provider can reachStandard cloud mailboxYour key, provider uses itYour key, provider can’t use itZero-access mailbox
Message bodies, for search and spam filteringYesYes, as you authorizeNo, for encrypted messagesNo
Subject linesYesYesVaries by productTuta: no. Proton: encrypted, not end-to-end
Sender, recipient and timeYesYesYesYes
Mail as it first arrives from Gmail or OutlookYesYesYes, unless the sender also encrypted itYes, briefly, before encryption on arrival
Staff access for supportThrough internal approval, plus your admin’s with Customer LockboxSameEncrypted messages stay unreadableEncrypted content stays unreadable
Content under a court orderReadable contentReadable contentEncrypted content plus metadataEncrypted content plus metadata

What every column shares is that someone signed in as you sees everything you see. Encryption protects mail from people without your key. A phished password hands them the key. How often that happens, and which providers it happens to, is in what secure email means.

Which arrangement fits a small firm

Most small firms are best served by a standard cloud mailbox with strong sign-in. That means two-step verification for everyone, enforced by an admin, plus encryption for the specific messages that carry sensitive data. Microsoft and Google both handle the patching, filtering and deliverability that self-hosting would hand to you.

A few situations point elsewhere:

  • Your clients or regulator expect the provider to be unable to read stored mail. A zero-access mailbox does that by default. Client-side encryption does it on enterprise plans.
  • Your compliance team wants to control and revoke keys, but keep every feature working. Customer Key fits that brief.
  • Phishing is getting through your current filtering. A gateway helps, and it means another vendor reads your mail.
  • You need full physical custody. Self-hosting gives it, at the cost of running a mail service.

If you’re weighing a move to a new provider, what a more secure provider would actually buy you helps with that decision. If you’d rather keep your mailbox and add encryption, encryption a small firm can run covers that. How each kind of encryption works under the hood is in the kinds of encryption, side by side.

Point and the mailbox you already have

Point isn’t an email provider. It doesn’t host mail or hold encryption keys, and it doesn’t add encryption. It reads from the Gmail or Outlook mailbox you already use, and it never asks for your email password. Your mail stays where it sits today, under the same keys.

There’s one real trade-off. A message your provider can’t read is a message no assistant can read either, Point included. More on that in encrypted email, and what an AI assistant cannot read. What Point does with the mail it can read is on what Point does for you.

Common questions

Is Gmail secure cloud email?

Gmail is cloud email with encryption in transit and at rest, and Google holds the keys. That’s secure against outsiders on the network and in the data center. It isn’t private from Google. Google Workspace client-side encryption, on enterprise plans, adds keys Google can’t use.

Can my email provider read my email?

On Gmail, Outlook and most business mail, the provider’s systems read your mail to filter spam and run search. Staff access goes through an approval process. On a zero-access service like Proton or Tuta, the provider stores your message bodies encrypted and can’t open them.

Is cloud email more secure than an on-premises server?

For most small firms, yes, in practice. The big providers patch, monitor and filter at a scale a small office can’t match. An on-premises server gives you custody of the keys, but it’s only as secure as the person maintaining it.

What’s the difference between cloud email security and secure cloud email?

Cloud email security usually means a filtering service that screens incoming mail for phishing and malware. Secure cloud email usually means a hosted mailbox that keeps stored mail encrypted. Many firms use both: a mailbox from one company and filtering from another.

Does a secure email gateway encrypt my stored mail?

No. A gateway filters mail on its way to your mailbox. Stored mail stays under your mailbox provider’s encryption. Some gateway vendors also sell outbound encryption for individual messages as a separate feature.

The location doesn’t decide it. Under 18 U.S.C. § 2713, a US provider must disclose data in its possession, custody or control wherever it’s stored. What limits a disclosure is whether the provider holds a key that can read the mail.

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.