The morning you decide to stop is shorter than the morning you started. Your mail never moved, so nothing has to come back from anywhere. You walk out with everything that was written into your own mailbox, in your own provider’s vocabulary. You leave behind the layer that was doing the thinking. That line is the whole cost of the decision, and knowing which of your things sit on which side of it is worth more than any assurance about it.
- Leaving is a revocation. You withdraw the app’s access, and your address, your mail and your history stay where they already were. There’s no copy to make and no deadline to make it by.
- What an app wrote into the mailbox stays, permanently and unconditionally. The labels or categories, the filing, the mail you sent, the meetings on your calendar: they’re ordinary items in your account, and nobody can reach in and take them back.
- What goes is the layer. The ranking, the summaries, the tasks, the wake times, the record of why. Gmail and Outlook have nowhere to put any of it.
- The part that costs people something is standing work. Things being watched for, follow-ups being chased, replies waiting on your approval. Those stop the moment access does, and nothing announces it.
- Ending access and asking a company to delete its copy are two separate requests. What a company may keep, and for how long, is settled by what it wrote down. For a supplier this size, the law usually stays out of it.
There is nothing to bring back
Three different acts get called leaving, and each has a different effect. Sorting them out is the first useful thing on this page. People routinely do the first one and believe they’ve done the second.
You stop opening the app. The authorization is still live. The connection still reads the mailbox and writes into it, and whatever you’d set to be handled without asking goes on being handled without asking. This is the one distinction worth holding onto: a tab you’ve stopped opening isn’t a relationship you’ve ended. The gap between the two is where the surprises live.
You end the authorization. This is the one people mean. You do it on your provider’s own page, in a list your provider keeps. The vendor’s cooperation isn’t part of it, and neither is their knowledge. Where that list sits on the Google side, and the sentence Google adds about what a company may already hold, is the Gmail part of this series. The Microsoft equivalent is the Outlook part, including the case where an administrator consented on the organization’s behalf and only an administrator can undo it. From the moment you’ve done it, the app can’t read your mail, can’t write to it and can’t act on it.
You ask the company to delete what it holds. A separate request, to a different party, with the least machinery behind it of the three. It’s the one that reaches a copy sitting somewhere other than your own account, and it gets its own section further down.
The middle act is cheap for the reason the first afternoon was cheap. It’s the sentence this series has circled from the beginning: one mailbox, in one place, taking delivery at the same address the whole time. Why there is no migration when you switch email apps itemizes what a real migration pays for. Every line of that bill exists because a second mailbox has to end up matching the first. Ending an authorization closes a window onto a room that was always yours.
One property of a revocation is worth knowing in advance, because it runs against the instinct. A revocation is abrupt. There’s no wind-down, no notice period, no export window that opens on the way out. The app simply stops being able to see anything, in the middle of whatever it was doing. That sounds alarming and it’s the opposite. A service that needed a managed departure would be one holding something you needed back, and this series has argued from the start that there’s nothing of that kind here. It does mean the small amount of preparation worth doing happens before you click. That’s what the twenty minutes below are for.
What was yours the whole time
Five things stay, and one reason covers all five. Each is an ordinary object in an account you never left.
Your address, your mail and your history. Untouched throughout. An email client is a window onto a mailbox, and the mailbox stays with your provider. If the address itself is the thing you’re unsure about, the answer turns entirely on who owns the domain it sits on, which the first part of this series works through.
The labels or the categories. Every triaged message keeps whatever word was put on it. In Gmail they’re ordinary labels, in Outlook ordinary categories. They look like every other label and category you have, and they go on working after the app is gone. You can leave them, use them, or clear them out in one action, and that choice stays open indefinitely.
The filing. Every thread that was put away stays put away. In Gmail that means it’s out of the inbox and in All Mail, like everything else you’ve ever archived. In Outlook it means it’s sitting in the Archive folder, where you can open it, count it and drag things out of it. What an email app writes back into your mailbox is where those two operations are pulled apart, and both of them hold once an authorization ends.
The mail you sent. In your Sent folder, threaded under the messages it answered. It went out through your account, from your address, like any other reply you’ve written.
The meetings. Ordinary events on the calendar itself. Open the calendar with nothing installed and nothing connected, and they’re there.
That list has a consequence almost nobody expects, and it’s the honest good news of the whole subject. Your mailbox on the day you leave is in whatever condition months of triage left it in. That’s a better condition than the one you connected it in, and it stays that way. Every one of those decisions is recorded in it. The archive is deep, the inbox is short, the sent record is complete. The judgment stops. Everything the judgment produced is still sitting there, filed, on your provider’s servers, in a format your provider has understood since before any of this existed.
One caveat belongs in the same breath. A label holds a name. Once the software is gone, Now and Later are two words on some old mail, meaning whatever you remember them meaning. That’s a deliberate trade, and the part on writing back sets it out. The alternative is encoding the reasoning into label names, which fills a mailbox with a private language nothing else can read.
What the layer takes with it
Here’s the other pile, stated plainly.
The feed, and the ranking that ordered it. The summary sitting on each thread. The tasks lifted out of your mail, with their dates. The wake time on anything you set aside. The record of what was done and why. Whatever the app had worked out about how you like client mail signed off. The version of your contact list where a client with three addresses is one person. The morning briefing. The standing requests to be told when something arrives.
All of that goes because Gmail and Outlook have no field it could live in. That’s the argument the part on writing back makes at length. An app that forced it in would be writing a vocabulary into your mailbox that means nothing to Gmail, nothing to Outlook, nothing to your phone and nothing to whatever you’re using in 2030.
So this is the bill the part before this one promised, and it’s worth reading exactly. The thing you pay for is precisely the thing that goes. Read what that amounts to. Everything of yours stays in your hands, so there’s no hostage, no ransom, no data to negotiate for. There’s still a cost. Two years of a product learning your habits is two years of accumulated fit, and accumulated fit doesn’t transfer to the next product any more than it transfers back to Gmail. Every tool of this kind works that way, and any page telling you otherwise is describing a filing system.
That reframes the export question, which people usually ask at the wrong end. Your mail is already yours, so the question is about the layer. Does the layer have an export at all? Which parts of it survive outside the product, and in what format? Some of it travels perfectly well. A task with a date and a link to the thread it came from is a portable object, and so is a list of the people you marked as mattering. Some of it means nothing anywhere else, a ranking most of all. Ask a supplier for that list before you sign rather than at cancellation, and add it to the retention and subprocessor questions in what to ask an AI tool about your data.
The work that stops without telling you
Now the part that actually costs people something. It’s a set of commitments quietly ceasing, with nothing to announce that they have.
The standing watches. A request to be told when the signed engagement letter comes back is a piece of software watching your incoming mail on your behalf. End the authorization and the watching stops. The letter arrives, nothing happens, and a missing alert feels exactly like a missing letter.
The follow-ups that were being chased. Open loops you handed over stop being counted. The person who hasn’t replied goes on not replying, and the arrangement where somebody was going to notice is gone.
Anything waiting for your approval. Work sitting in a review state is work that hasn’t happened. A reply prepared but not sent looks, from the other end, precisely like being ignored. A queue of those is the most avoidable loss in this whole subject, because clearing it takes a few minutes.
Mail you set aside until a date that hasn’t arrived. This is the one to be careful about. Deferring a message lifts it out of the list you’re looking at, and something brings it back at an hour you named. That’s what snoozing actually does, and it’s why snoozing is the only inbox gesture that records a when. The when lives in the product. So if the message left your inbox to wait, and you switch off the thing that was going to return it, it stays where it is. It’s sitting quietly in your archive, whole, with nobody expecting it.
The four have one shape, and naming it gives you a rule that outlives any particular product. Anything that was going to happen later, on your behalf, without you, is a promise held by software you’re about to turn off. Your data is safe, because your data lives in your account. Promises live in the product. That’s the whole of the risk, and it’s also, conveniently, a complete description of what’s worth doing before you go.
Twenty minutes before you revoke anything
Everything you own is already safe. These twenty minutes are for the promises. Four of them take a couple of minutes each, and the fifth is the revocation itself, which goes last for a reason.
- Empty the approval queue. Go through whatever is waiting on your yes. Send it or discard it, deliberately. Both are fine. The one to avoid is leaving it in a state that resolves to neither once access ends.
- Wake everything you set aside. Bring the deferred mail back into the inbox now, while something still knows the dates. It’ll look like a bad morning for a minute. It’s the cheapest insurance on this list.
- Write down the open loops. Your task list is the only place some of them exist as a dated commitment. Ten minutes with a notepad is enough. You’re copying names and dates, and the mail every one of those tasks came from is still in your mailbox, where it always was.
- Turn the watches off yourself. Leaving them on breaks nothing. Switching each one off is how you find out which promises you’re quietly taking back. A standing request you’d forgotten you made is exactly the one worth rediscovering here.
- Then revoke, and open your mailbox once. The labels or categories are still on the old mail, the archive is still full, the sent record complete. Thirty seconds, and you’ve seen for yourself the claim this whole series rests on.
Look at what that list is made of. A handful of commitments and a couple of lists, and that’s all of it. Your mail, your address, your history, your contacts and your calendar sit in an account that hasn’t moved, and nothing you’re about to do touches them.
Two situations sit outside it. If you’re leaving your email provider as well as the app, that’s a genuine migration. It has a real deadline and a copy to make while you still have access, and the first part of this series sets out the order. And if you’ve been meaning to tidy the address book, do that at Google or Microsoft on its own terms, on a day of its own, because it has an undo you would not want to meet in a hurry.
Ending access and deleting data are two requests
Revoking stops what happens next. A copy the company already holds is a separate matter, and Google says so in its own words on its own page about removing linked apps, quoted in the Gmail part. Deletion is a second ask, made to the supplier, and it’s worth knowing how little stands behind it before you rely on it.
Start with the law, because most people assume more of it than is there. California’s is the one usually meant. The California Consumer Privacy Act gives a right to delete, in the Attorney General’s own words: “You may request that businesses delete personal information they collected from you and to tell their service providers to do the same” (California Attorney General, checked September 6, 2026). Then read who it reaches. The same page says the act “applies to for-profit businesses that do business in California” and that meet at least one of three tests (same page, checked September 6, 2026):
- “Have a gross annual revenue of over $25 million”
- “Buy, sell, or share the personal information of 100,000 or more California residents or households”
- “Derive 50% or more of their annual revenue from selling California residents’ personal information”
Hold those numbers against the kind of company you’re considering buying from. A supplier selling to small professional firms, in a private beta, is very often below every one of those tests, and a right that attaches to businesses of a certain size attaches only to businesses of that size. Those figures are California’s, and they govern California residents. A number of other states have passed their own privacy laws, with their own thresholds and their own lists of rights. Whether any of this reaches you depends on where you live as much as on who you bought from, so check rather than assume.
What does hold everywhere is smaller and more useful. It’s the promise the company made you in writing. The Federal Trade Commission’s position on that is plain. “When companies tell consumers they will safeguard their personal information, the FTC can and does take law enforcement action”, and in the cases where it has, “the FTC has charged the defendants with violating Section 5 of the FTC Act, which bars unfair and deceptive acts and practices in or affecting commerce” (Federal Trade Commission, checked September 6, 2026).
That turns the whole question into a drafting question, and that’s good news. A specific promise is a strong one, because a company that fails a specific written commitment has made a false statement. A vague promise is weak, because it promises little. So get the specifics before you sign rather than after you cancel. How long content is kept after an account closes. Whether deletion reaches backups, and on what schedule. What happens to anything derived from your mail rather than copied from it. A deletion clause silent on backups is half a clause, and the missing half is the half with the copies in it. Reading terms of that kind clause by clause is the job keeping client data out of model training takes on, and the questions belong in one message to every supplier on the shortlist.
What Point leaves you holding
Point authorizes against the Google or Microsoft 365 account that already holds your mail, and the record of that authorization lives in that account rather than with Point. You end it where your provider keeps its list, yourself, without asking us. The two parts of this series about connecting are where each of those lists is.
What stays is the whole of what Point wrote into your mailbox, and that’s four things. The Now, Later and Other labels in Gmail, or the same three as Outlook categories, on every message that was triaged. Every thread that was filed, sitting in All Mail or the Archive folder according to which provider you have, filed rather than deleted. Every reply, in your Sent folder, threaded under the original, because it went out through your own account from your own address. And every meeting, as an event on the calendar you already keep. What an email app writes back into your mailbox is that inventory in full. Four ordinary objects, in a format your provider already speaks, and this morning is exactly what that’s for.
Your address book is a special case worth stating on its own, because it’s the one place where a merge would have been hard to undo. Point doesn’t write to it. The resolved view, where a client with three addresses is one person, is built inside Point, and Google Contacts or the Outlook People list stays exactly as it was, which the previous part explains at length. On the way out that means there’s nothing to un-merge, nothing to roll back and no thirty-day clock anywhere near your contacts. You keep a list identical to the one you had, duplicates and all.
What goes is the layer, and it’s the same list as everybody else’s. The feed and its ordering. The summaries. The tasks and their dates. The wake times on set-aside mail. The log of what was done and why. What Point had learned about how you like things. The resolved view of who is who. The briefings and the watches. The ones that need a few minutes of your attention before you revoke are the standing work rather than the stored work, which is what the twenty minutes above are for.
How much standing work there is to unwind varies, and this is where a setting you made months earlier turns out to matter. Point holds a separate level for each kind of work. The level runs from staying out of it, through preparing something for your approval, to handling that kind of work itself, and all three start in the cautious middle one when you first connect. If you never moved any of them, almost everything Point did was waiting for you anyway, and there’s very little running unattended to stop. If you raised several, there’s more. The autonomy dial sets out what each of the three positions permits, the activity log is the written record of what got done under them, and everything Point does is the list of work that was available to hand over at all.
Two limits are worth naming plainly. Retention and deletion at Point are a matter of the written terms, the same as at any other supplier, and the right way to establish them is the way this page recommends for everybody: in writing, before you sign, with the backup question asked explicitly. And leaving Point does nothing about an address you don’t own, a mailbox your internet provider can reclaim, or an archive sitting on an old laptop. Those sat upstream of every product on the market before you arrived, and they sit upstream of all of them after you go.
The question that belongs at the front
The odd thing about this page is where it sits. It’s the last part of the series and it’s the part worth reading first, because everything the other six argue is only worth believing if this one is true.
Read the arc backward and it collapses into a single claim tested from seven angles. Your address survives because it never belonged to the app. Your history survives because it stayed where it was. Your labels and folders survive because they live at Google and at Microsoft. Your contacts survive because nothing wrote to them. And on the morning you leave, all of it is still there, in the same account, under the same bill, unchanged by the departure of the thing that had been reading it. A product that took nothing on the way in has nothing to hold on the way out, and a product with nothing to hold can’t make leaving expensive however much it might like to.
So the switching fear that started this series turns out to have been a question about ownership dressed as a question about software. Once ownership is settled, the decision shrinks to something much more ordinary. Getting out is easy. What’s left to decide is whether the layer is good enough to be worth having, on a Tuesday, in your own inbox, with your own clients writing to you.
That one no page can answer, including this one. It gets answered in the first hour of the first afternoon, which is what day one is written for, and by about the second Friday you’ll know.