An email cleaner almost always asks for access to your whole mailbox, with the right to change it. That’s normal. Deleting, archiving and unsubscribing in bulk all mean writing to your mail, and writing takes the broad permissions. The useful questions come after that. Does this app need that much for the job you want done? What does it keep once it’s in? And how do you take the access back afterward?
- Expect a broad request. Any cleaner that deletes or archives needs read-and-write access.
- One line is worth a pause. On Google’s screen, “permanently delete all your email” is the widest grant there is.
- “We only read headers” is a promise about behavior. The permission itself usually covers everything.
- The screen can’t show what the app keeps. That’s in the vendor’s privacy policy, and it varies a lot.
- Taking access back takes a minute. It stops new reading. What the app already copied stays with the vendor until you ask them to delete it.
Google’s, Microsoft’s and Yahoo’s pages below were checked on October 5, 2026, along with the two vendor pages named.
Why a cleaner needs so much
A cleaner’s job is to change your mailbox. Moving a year of newsletters to Trash is a write. So is archiving, labeling, and setting up a rule that runs every week.
A read-only app can show you who sends the most mail, and that’s where its job ends. That’s why almost every cleaner asks for read and write together, and why the request looks the same as the one from a full email client.
Here’s what each cleaning job needs, in plain terms.
| What you want done | What the app has to be allowed to do |
|---|---|
| See who sends you the most | Read the sender, date and subject of each message |
| Delete to Trash, archive, label | Read and change messages |
| Delete for good, skipping Trash | The widest mail permission there is |
| Set rules that run on new mail | Change your mail settings and filters |
| Unsubscribe for you | Often send an email from your address, or open the sender’s link |
| Work over IMAP, as many cleaners do | Full access to the mailbox, on Gmail and Microsoft alike |
The last row matters most, and the next section explains it.
What the Gmail screen asks for, line by line
When you connect a cleaner with Sign in with Google, Google’s screen lists what the app wants. Each line maps to a named permission, which Google calls a scope. These are the mail lines a cleaner is likely to show, in Google’s own wording from its list of Gmail scopes.
| What the screen says | Google’s class | What a cleaner can do with it |
|---|---|---|
| “Read, compose, send, and permanently delete all your email from Gmail.” | Restricted | Everything, including deletion that skips Trash |
| “Read, compose, and send emails from your Gmail account.” | Restricted | Delete to Trash, archive, label. Not deletion for good |
| “See, edit, create, or change your email settings and filters in Gmail.” | Restricted | Set up rules that act on new mail |
| “View your email message metadata such as labels and headers, but not the email body.” | Sensitive | Count and sort by sender, and nothing more |
| “See and edit your email labels.” | Non-sensitive | Create and rename labels only |
The second line is enough for most cleaning. Its full description adds that it “does not allow immediate, permanent deletion of threads and messages, bypassing the trash.” So mail it removes sits in Trash for 30 days, and a wrong sweep can still be undone. What an email cleaner deletes covers getting it back.
The first line is the one to stop on. It’s the only Gmail permission that can erase mail with no Trash in between. An app asking for it should be able to say why.
There’s one honest reason a cleaner might need it anyway. Google’s IMAP sign-in documentation puts it plainly:
The scope for IMAP, POP, and SMTP access is
https://mail.google.com/.
IMAP is the older protocol desktop mail apps use. IMAP has one size of grant on Gmail, and it’s the largest. So a cleaner that connects over IMAP with Google sign-in holds the widest permission, whatever it chooses to do with it. Knowing that, you can weigh the vendor’s promises with your eyes open.
A “headers only” cleaner can still hold the whole mailbox
Several cleaners say they never read the body of your mail. Clean Email’s security page, checked October 5, 2026, puts it this way:
We only access the envelope and header information associated with your emails. The actual bodies of your messages are never downloaded or accessed within our computer systems.
That’s a real commitment, and a useful one. It describes how the company uses its access. Deleting or moving a message needs the read-and-write scope, and that scope covers the body too. The metadata line is the only one on Google’s screen that stops at headers, and an app holding only that can sort but can’t clean.
Here the difference between the two costs something real. The permission screen shows what the app can reach, not what it says it will read. Take a “headers only” claim as a promise, and look for the same promise in the vendor’s privacy policy.
Outlook and Microsoft 365
Microsoft’s consent screen works the same way, with its own words. These come from the Microsoft Graph permissions reference.
| Permission | What Microsoft says it allows |
|---|---|
Mail.ReadWrite | “Allows the app to create, read, update, and delete email in user mailboxes. Does not include permission to send mail.” |
Mail.Send | Shown on screen as “Send mail as a user” |
MailboxSettings.ReadWrite | Creating, reading, updating and deleting your mailbox settings |
IMAP.AccessAsUser.All | “Allows the app to have the same access to mailboxes as the signed-in user via IMAP protocol.” |
A cleaner on Outlook needs Mail.ReadWrite at the least. Sending is a separate line. If the screen also asks to send as you, the app should have a reason, such as sending unsubscribe emails. The IMAP line is Microsoft’s version of Google’s widest grant. It gives the app everything you can do.
Two things differ at work.
- Your admin may decide for you. On a Microsoft 365 work account, your administrator can block outside apps or approve them for everyone. If a cleaner won’t connect, that’s usually why.
- A blue “verified” badge confirms who made the app. Microsoft’s publisher verification page says the badge “doesn’t imply or indicate quality criteria you might look for in an app.” It tells you the company is real. How it handles your mail is a separate question.
Yahoo, iCloud and app passwords
Yahoo and iCloud Mail handle outside apps differently. Many cleaners connect to them with an app password. That’s a separate password, made for one app, that lets it sign in to your mail over IMAP.
Clean Email’s security page describes this for iCloud users, who “can create an app-specific password just for Clean Email and, if needed, revoke it at any time without affecting the main account password.”
An app password opens your mail as fully as IMAP allows. Its strength is that it’s separate. Delete it, and that one app is locked out while your own password carries on working.
Whatever the provider, your main password stays with you. Google’s help on linked apps is direct about why:
If you share your Google Account password with a third-party app, they’ll have full access to your Google Account and this can compromise your account security.
A cleaner with a sign-in screen of its own, asking for your Gmail or Outlook password, is one to close.
What Google checks before you ever see the screen
Gmail apps that read or change mail hold restricted scopes, and Google puts conditions on those. Two are useful to you.
- A warning when the app hasn’t been checked. Google shows an extra screen for an app that “requests a sensitive or restricted OAuth scope, but hasn’t gone through the Google verification process,” per Google Cloud Help. A cleaner that’s been selling for years shouldn’t trigger it.
- A yearly security assessment. Google’s restricted scope rules say apps that reach restricted data “from or through a third-party server must undergo an annual security assessment by a Google-approved third party.”
Google also lists exceptions, including personal use. So a free cleaning script from a code site, run on your own account, may have skipped the assessment. That can be perfectly fine. Your own review is standing in for Google’s.
The assessment covers how a company protects what it holds. What it keeps, and for how long, is in its own policy. How to read the rest of a consent screen, and what each badge is worth, is in what to check before you connect your inbox.
What the screen can’t tell you
The consent screen shows what an app can reach. Three things it can’t show sit in the vendor’s own documents.
What it copies. Some cleaners work on your mail where it sits. Others copy headers, or more, to their own servers to sort them.
How long it keeps that. This varies more than you’d think. Clean Email’s page says it “automatically deletes all stored metadata after 45 days.” Mailstrom’s privacy policy says that after you delete your account, “we will keep your data for up to three months to facilitate easy restarting of your account,” unless you email privacy@mailstrom.com and ask otherwise. Both pages were checked on October 5, 2026.
Who else sees it. This is the one with history. On December 17, 2019, the FTC finalized a settlement with Unrollme, an unsubscribe service. The FTC alleged it “falsely told consumers that it would not ‘touch’ their personal emails in order to persuade consumers to provide access to their email accounts.” Meanwhile, the e-receipts in users’ inboxes went to its parent company, Slice Technologies.
So before connecting, look for three sentences in the privacy policy. What it stores, how long it keeps it, and whether anyone else receives it. A policy missing any of the three has told you something too.
Taking the access back when you’re done
A one-time clean-out is finished when the inbox is. Remove the app then. It takes a minute on each provider.
| Account | Where to remove an app |
|---|---|
| Google and Gmail | myaccount.google.com/linkedapps, then the app, See details, Remove access |
| Personal Microsoft, such as Outlook.com | account.live.com/consent/Manage, then the app, Remove these permissions |
| Microsoft 365 work or school | The My Apps portal, then Manage your application, then Revoke Permissions |
| Yahoo | Account security page, External connections, App passwords, then Delete app password |
| iCloud Mail | Delete the app-specific password the cleaner used |
The Google steps are from Google Account Help, which says that “If you remove access, the app can’t access your Google Account.” The Microsoft work steps are from Microsoft Support. It notes you can’t revoke what your administrator approved on your behalf. The Yahoo steps are from Yahoo Help.
Removing access stops new reading. What the app copied before then stays on its servers, as Google’s help on app links confirms. So deleting your account with the vendor is its own step. With Mailstrom, that means the email to its privacy address.
Changing your password leaves these grants in place, since each app connected through Google or Microsoft sign-in holds its own. Who still has access to your email walks through every kind of access an old mailbox collects.
What Point asks for, by the same measure
Point is an email client rather than a cleaner. It sits on top of your existing mailbox, whether that’s Gmail or Outlook. Measured against this page, it asks for the same broad kind of access. Here’s what that access is used for.
Point reads each thread as it lands, so the ones waiting on you are at the top when you sit down. Its sorting shows up in Gmail as ordinary labels. Filed threads go to Gmail’s archive with every word kept. A reply you send from Point leaves from your own address. Reading, changing and sending are the three things those need.
Bulk deletion isn’t on that list. Every action Point takes is written to a log you can read, and Point’s own actions can be undone from there. How much it does before checking with you is a setting for each kind of work. A new account starts every kind on review. Setting how much your inbox does on its own shows each position, and the benefits page lists the rest. If you ever want Point gone, the pages in the table above remove it like any other app.
Common questions
What access does an email cleaner need?
To delete, archive or label mail, a cleaner needs read-and-write access to your mailbox. On Gmail, that’s at least “Read, compose, and send emails from your Gmail account.” On Outlook, it’s Mail.ReadWrite. A cleaner that only reads headers can sort your mail by sender but can’t remove anything.
Is it safe to give an email cleaner access to Gmail?
It can be, with an established app. Gmail apps that read or change mail on their own servers must pass a yearly security assessment by a Google-approved third party. Check the vendor’s privacy policy for what it stores, how long, and who else gets it. Remove the app when you’ve finished a one-time clean.
Why does an email cleaner ask to “permanently delete all your email”?
That line is Google’s widest Gmail permission, and it’s also the only one Google allows for IMAP access. A cleaner built on IMAP has to ask for it. A cleaner built on Google’s own API can usually do the job with the narrower permission, which sends deleted mail to Trash first.
Can an email cleaner read my emails?
If it can delete or move them, the permission it holds covers the full message, body included. Some cleaners promise to read only headers. That promise lives in the vendor’s own policy, not in the permission.
Does removing a cleaner’s access delete my data?
No. It stops the app from reading anything new. Google’s help confirms that the copy an app already made stays where it is. Deleting your account with the vendor is a separate request.
Should I give an email cleaner my Gmail password?
No. Connect through Sign in with Google, or with an app password on Yahoo and iCloud. Google warns that giving an app your password gives it “full access to your Google Account.”