Cancelling Superhuman: What Happens to Your Email

What happens when you cancel Superhuman email is smaller than most people fear and larger than the billing page implies. Superhuman Mail is a client that sits on top of Gmail or Microsoft 365 — it authenticates over OAuth and reads a mailbox those providers already hold — so cancelling the subscription is a disconnect, not a deletion. Your messages, folders, address and archive stay in place.

What does stop working the day the seat lapses is everything Superhuman kept on its own side of that line: snippets, Split Inbox queries, Remind Me follow-ups, team comments, Send Later queues and your signature HTML. This post walks the audit to run before you click cancel, the actual steps, what breaks, how to roll back if you change your mind, and how to run it without downtime.

Disclosure: we build AI Emaily, one of the clients people land on after Superhuman, and the destination named in the placement section at the end. The audit and cancellation mechanics below apply whether you land with us, Shortwave, Mimestream, Apple Mail or plain Gmail — the sequence is the same, and copying it out first is what actually protects you.

What actually moves, and what does not#

The reassuring half first. Superhuman authenticates to Google or Microsoft over OAuth and reads a mailbox those providers already hold. Its help centre describes the inbox as stored on your machine rather than on Superhuman's servers, and cancelling the subscription severs the OAuth grant — it does not touch a message.

The risky half sits above the mailbox. Anything that was Superhuman's own product — the snippet library, split queries, the Remind Me schedule, team comments, read statuses, queued Send Later messages — never became part of the mail or of the underlying provider account. When the seat lapses, that layer is unreachable, and no export button walks you out with all of it packaged.

The pre-cancellation audit#

Do this in a single 30-minute sitting while Superhuman is still open and your subscription is still active. None of it is recoverable after access ends, and doing it under pressure on cancellation day is where people lose snippets they wrote years ago.

• Paste every snippet — private and any Team Snippets you own — into one document, including the shortcut name. Superhuman's help centre states snippets cannot be transferred between accounts, and it documents no bulk export as of August 2026.
• For each Split Inbox split, copy the underlying search query verbatim. A split is a saved query, so the string is the whole thing — it becomes a Gmail filter, an Outlook rule or a saved view in the new client.
• Open the Reminders view and list every pending Remind Me and auto follow-up, with its date and the recipient it chases. Decide which need to survive and which can quietly expire.
• Walk the Send Later queue message by message. Per message, decide: let it fire before cancellation, or move it into Gmail or Outlook's own scheduled-send. Anything still queued in Superhuman when the seat ends does not go out from any other client.
• For any thread where the real decision lives in a team comment rather than in the message body, copy that context out. Comments were never delivered to external recipients and never became part of the mail, so Gmail does not have them.
• Copy your signature block — the HTML, not just how it looks — since Superhuman stores it in its own settings, not in Gmail's signature field.
• Note your read-status habits honestly. If you time follow-ups off whether a recipient opened the mail, confirm the destination offers something equivalent before you commit.
• Screenshot your keyboard shortcut cheat sheet if you have customised bindings. You will want it as reference while you retrain in the new client.

The cancellation steps#

Once the audit is done, the actual cancellation is short. Neither Gmail nor Outlook needs to release anything — you are just ending a subscription and later revoking one OAuth grant on a mailbox that already exists.

1. 1

   Finish the audit above first

   Snippets, splits, reminders, scheduled sends, comments, signature. This is the one non-reversible part of the whole process, so it comes before every billing action.

2. 2

   Clear or reschedule the Send Later queue

   Either let queued messages fire before you cancel, or copy the message and its intended send time into Gmail or Outlook's own scheduled-send. A message left in Superhuman's queue when the seat ends will not send from another client.

3. 3

   Connect the replacement client alongside Superhuman

   Add the same Gmail, Google Workspace, Outlook.com or Microsoft 365 account in the new client using its normal OAuth or IMAP setup. Both clients hold the same mailbox at once — nothing duplicates, nothing moves, nothing is deleted.

4. 4

   Cancel the subscription in Superhuman

   For individual accounts, use the cancel option at the bottom of the Subscription page. For team seats, an admin removes members through the Admin Portal reached via Manage Team. Verify the current path on Superhuman's own help centre; billing surfaces changed hands during the Grammarly acquisition.

5. 5

   Revoke the OAuth grant, separately

   Ending billing and revoking a mailbox connection are two different actions. Open your Google Account security page or your Microsoft account's connected apps list and remove Superhuman from third-party access. Until you do this, the app can still hold a live token even after the seat ends.

6. 6

   Confirm the invoice and the refund window

   Check the final invoice date and, on annual plans, whether any mid-term proration applies. Superhuman documents its billing terms on its own help centre; a third-party guide, including this one, is not the authority on the number a card will be charged.

What breaks when the seat lapses#

Almost all of the breakage sits in the Superhuman-side layer, not in the mailbox. This table is the full list of items that either need to be rebuilt manually or stop the moment the seat ends — read it before you cancel, not after.

The rollback plan#

Rollback is the quiet advantage of any client that sits on your provider's mailbox — nothing about cancellation touched a message, so reverting means resubscribing and reconnecting. Provided the audit was done and the OAuth grant is revoked cleanly, the risk of leaving is contained.

Where rollback is genuinely hard is in the Superhuman-side layer you did not copy out. Snippets you never pasted into a document are gone. Splits whose queries you never wrote down are gone. Read statuses and team comments do not come back. Everything else — messages, drafts, sent mail, calendar, contacts — sits with Google or Microsoft, unchanged.

If you decide the new client is not working, the sequence is short: resubscribe to Superhuman, reconnect the OAuth grant, and rebuild any snippets or splits you had saved locally. You will not get read-status history or team-comment threads back, but you never lost the mail. On team seats, an admin has to re-add the member — the seat is not held open on the account after removal.

The Grammarly acquisition in July 2025 and the parent-company rename to Superhuman in October 2025 do not change this. Superhuman Mail still ships as the client you cancelled, and the same rollback path applies. Verify the current re-subscription and reconnection flow on Superhuman's own help centre — that surface changed hands, and third-party walkthroughs age fast.

Cancelling without downtime#

Because the mailbox never moves, downtime is a choice, not a constraint. The trick is running both clients on the same account for long enough to catch anything the audit missed, and to time the cancellation so the paid tail buys you the parallel-run week for free.

• Connect the replacement client on the same mailbox first. Both OAuth grants coexist — no mail duplicates, no folder gets confused, nothing changes on the provider side.
• Set the new client as the default handler for mailto links on your desktop and phone once you trust it — usually within two or three days of parallel use.
• Migrate one persona at a time if you run several mailboxes through Superhuman. Move your primary account first; add secondaries only after the first is stable.
• Rebuild only what you actually used last month. A snippet library grows like an attic; most of it is not load-bearing, and rebuilding all of it is what makes people give up on the switch.
• Warn any teammates before removing shared team access. Team Comments and Team Snippets end for everyone the moment an admin removes the seat, and quietly-disappearing snippets nobody copied out is a preventable outage.
• On an annual plan mid-term, treat the paid tail as free parallel-run time — cancel toward the end of the period, not the day you connect the new client, so a bad match can be undone without another subscription cycle.

Where AI Emaily fits, if you land with us#

We build AI Emaily, and this is the one paragraph that names it — the reader has already solved the cancellation. If the reason you are leaving is that you want the assistant to do more than draft, or you keep at least some mail on Outlook, IMAP or a custom domain Superhuman Mail does not open, we are an honest landing spot. Authority is set per account: Manual is a plain fast client, Copilot triages, files and drafts while nothing sends without approval, and Autopilot is gated with an undo window and a per-action audit log. Coverage spans Gmail, Google Workspace, Microsoft 365, Outlook.com and standard IMAP in one inbox, and drafting voice comes from a user-set Personal Context brain plus per-client profiles rather than being trained on your mail. Packaging is a 7-day free trial on Pro and Autopilot — card required, $0 if cancelled before day seven. On raw keyboard throughput and shortcut ergonomics, Superhuman is still ahead of us, and we will not pretend otherwise. See the

[homepage](/) and [pricing](/pricing) for the current shape.