What CME will and will not do to your mail

I built Connect My Email to clean inboxes without ever being the reason you lost something. This page says what the code does today, in plain terms. Every claim was checked against the source on the main branch on 2026-10-27, and the file is named next to each claim in this page's source. When the code changes, this page changes.

The short version

  • 11 kinds of mail are kept by default. A few age out: sign-in codes, sign-in links, sign-in and password change alerts, and routine service alerts after 30 days. Shipping notices stop being kept after a year.
  • Every delete is a move to Trash. CME does not expunge your mail.
  • Bulk tools preview first and run only on your go-ahead.
  • Limits are published per plan, in numbers, on the pricing page.
  • Credentials are encrypted with AES-256-GCM under a key derived per user.
  • No SOC 2 yet. Google OAuth verification pending. One operator. All stated below.

11 kinds of mail CME keeps by default

Every message gets one of three outcomes: kept, offered for cleanup, or asked. The 11 keep rules run first, in order. Only mail none of them claims can be offered. Most of it is bulk mail, plus sign-in codes, links, sign-in alerts and password change alerts once they are over 30 days old. Mail the rules can't place is usually asked.

KeptWhat it covers
1. Starred or flaggedAnything you starred or flagged. Gmail's "Important" marker does not count.
2. PeopleMail from people you have written to or replied to, threads you are part of, a lone email from a personal address, and a person's message carried by an app.
3. You and your keep listMail from your own address, and senders or domains on your keep list.
4. Account securityChanges to your account, such as a new email address, phone number or two-step setting, are kept at any age, as are team invitations and an account being set up for you. Sign-in codes, sign-in links, new sign-in alerts and password change or reset alerts are kept for 30 days, then offered.
5. MoneyBills, payments, refunds, deposits and other money events.
6. OrdersOrder confirmations and records, and donation receipts.
7. ShippingA parcel in motion or arriving. Kept for one year; after that the normal rules apply.
8. TravelTrips, bookings and tickets, and anything that happened to them.
9. Official recordsLegal, government, tax, health, school, housing and employer records.
10. Things you need to act onService notices that need you to act, at any age. Routine service alerts are kept for 30 days.
11. Calendar invitesMeeting invitations and event updates.

Kept is not a suggestion to the model. The rules run inside the cleanup engine, so a rule, a bulk tool or a cleanup your assistant runs cannot route around them. Tools where you name the exact messages, or a whole folder, do what you ask, and still move to Trash only. Receipts are kept on purpose even though some products treat them as clutter: a deleted invoice is the one mistake this product exists to prevent.

What can be offered for cleanup

Mail is offered for cleanup only when no keep rule claims it. Most offered mail is bulk mail: a mailing-list header, or a frequent sender with a second sign such as a marketing address. Sign-in codes, links, sign-in alerts and password change alerts are offered once they are over 30 days old.

Mail the rules can't place is usually asked: we show it to you and leave the call to you.

Below 0.70 confidence the policy layer downgrades any action to review unless you have approved that specific batch.

Offered never means deleted. You approve the cleanup, and everything it moves goes to Trash.

Trash only. Never expunge.

Every delete in CME is a move to your Trash folder. The single-message delete, the bulk delete and the empty-folder tool all take the same path. When an account has no Trash folder, all three refuse to act rather than remove anything permanently. You recover from Trash the way you always have.

The IMAP layer backs that up. Reads open mailboxes read-only. When a write path has to release a mailbox it re-opens it read-only first, because a plain CLOSE on a read-write mailbox would permanently remove anything your own mail client had marked deleted. If that re-open fails, the command that would have sent CLOSE is refused.

Free accounts cannot delete at all. Free cleanup is limited to archive and mark as read, which you can undo from any mail client.

One honest exception. When you edit a draft that CME saved, CME removes the older copy of that same draft after the new one is written, and only when the server has proven the old copy is the older message. Deleting a draft from the dashboard is the other. Those two draft-only paths are the only expunges in the codebase, and neither touches mail you received.

You approve every batch

Bulk tools preview first. The cleanup and bulk-delete tools run as a dry run unless dry_run is set to false. The execute-cleanup and empty-folder tools show you the plan and act only when called again with confirmed set to true. On the REST API, dry_run is required on every bulk call, so a script cannot forget it.

The policy layer enforces the same rule from the other side: a destructive action without explicit approval is refused and downgraded to review.

Before anything moves, check_before_cleanup answers allowed, blocked or review for any message or sender, with the class and the reason. It is read-only and free on every plan. Call it before cleaning up with any tool, including ones that are not ours.

Sending has its own guard. When you set a send allowlist on a connected inbox, the SMTP client checks every recipient against it before a byte goes out, on every path that sends from that inbox: tools, scheduled sends and the REST API alike. It is set from the API today.

Published limits, per plan

Every number below is read from the tier table the server enforces. They are the same numbers on the pricing page.

LimitFreeProPower
Price$0$9/mo or $86/yr$19/mo or $182/yr
Connected inboxes2510
Messages per scan25,000, report only250,000500,000
Cleanup actions per month 5,000 guarded and reversible: archive and mark read 50,000 150,000
Searches per day5005,00010,000
Sends per day10, to people you've emailed before100500

The $19 Sweep is a one-time clean, not a plan. It scans the newest 750,000 inbox emails and cleans all the mail it offers for cleanup, and runs in a separate service that carries the same 11 keep rules. A drift check in CI keeps the two copies of the classifier in step.

Your credentials

Mailbox credentials are encrypted with AES-256-GCM before they are stored. The key for each user is derived from a master key with HKDF, so one user's key does not unlock another's. The master key lives only in the server environment. Encrypted credentials sit in the platform database with a Redis cache. Sessions created before the per-user path shipped still use the original single-key AES-256-GCM path.

Gmail connects with OAuth, so CME never sees your password, and the refresh tokens are encrypted the same way. iCloud, Yahoo, Fastmail and other IMAP providers connect with an app-specific password that you can revoke at the provider at any time. Outlook / Microsoft 365 is coming soon.

What we do not claim

  • No SOC 2. CME has no SOC 2 report today. It is on the roadmap, not in hand.
  • Google OAuth verification is pending. Until Google finishes verifying the CME app, you may see Google's warning screen when you connect Gmail.
  • One operator. CME is built and run by one person. There is no 24/7 on-call rotation. Status, incidents and changes come from me.
  • No third-party penetration test yet. The guarantees above are enforced in code and covered by tests, and I am the one who wrote both.
  • Report a vulnerability: security@connectmyemail.com. Reports are acknowledged within 48 hours; we aim to remediate within 7 business days.
  • The model sees what it reads. Anything your assistant reads through CME is visible to the model and to the host you run it in, as with every connector. Connect the inboxes you are comfortable with.

FAQ

Can my assistant permanently delete mail through CME?
No. Every delete in CME is a move to your Trash folder. There is no tool argument that bypasses Trash, and the IMAP layer refuses to send the commands that would expunge. The only expunges in the codebase are draft-only: replacing an older copy of a draft CME itself saved, after proving it is the older message, and deleting a draft from the dashboard.
What does offered for cleanup mean in a CME scan or suggestion?
A candidate for you to approve. Only mail no keep rule claims is offered. Most of it is bulk mail, plus sign-in codes, links, sign-in alerts and password change alerts over 30 days old. Mail the rules can't place is usually asked instead. Offered never means deleted; cleanup moves mail to Trash.
Does the Free plan clean anything?
Yes. Free includes 5,000 guarded, reversible cleanup actions per month; Pro raises the cap. Free can archive and mark as read, both undoable from any mail client. Free cannot delete, move or flag, and can send only 10 a day to people you've emailed before.
I use another tool to clean up. Can CME still protect me?
Call check_before_cleanup first. It is read-only, free on every plan, and answers allowed, blocked or review for any message id or sender, with the class and the reason.