Connect a mailbox and Point reads all of it. The whole history, whoever it came from. Every thread in there, including the one from four years ago about the joinery client’s overdraft. And every message that lands after.
That’s the answer to the first of the six questions, and it belongs in the opening line. It’s the part a supplier is most tempted to soften. It’s also the part you’d work out for yourself by the second week.
It also has to work this way, which is worth seeing before it reads like a concession dragged out of somebody. Deciding what matters is the looking. A product that offered to read only your important messages would have to know which ones those were before it opened anything. Knowing that is the whole job. The reading and the ranking are one thing. The reading is the ranking, seen from underneath.
So the question people carry to the connect screen gets answered on the first morning, and it turns out to be the wrong shape to carry. Three better ones sit underneath it: how far the reading reaches, what it leaves behind, and what it’s kept away from. Those have edges, and a supplier can be held to all three.
What the connect button actually was
Your mailbox stayed where it is. Point runs on top of the one you already keep with Google or Microsoft, and the address and the plan stay exactly as they are. The whole shape of it is changing client without changing account. No migration, no export, no new address to tell four hundred clients about.
What you did instead was grant a permission. Your mail provider holds it, recorded against your account there. It sits on the same page as every other application you’ve ever let near your mail. Google’s own account help is plain about both halves. It says that you can allow apps access to some of your Google Account data, and if you remove access, the app can’t access your Google Account (Google Account Help, checked August 19, 2026).
Read that twice. It’s doing more work than it looks like. You revoke the grant yourself, at your provider, and the vendor finds out afterwards. It takes one person’s decision, and that person is you. It’s the one fact in this whole subject you can check for yourself, whatever you make of the rest. The record sits with the firm you were already trusting with eleven years of client correspondence. Everything else in this series is a supplier’s word, tested against documents. This one you can see.
Point’s own privacy policy names what Point takes at that moment. Provider account identifiers, addresses, tokens or token references, scopes, authorization status, sync state, and folder or label metadata (privacy policy section 3.3, version 1.0, effective July 7, 2026, checked August 19, 2026). Scopes is the word to notice. A scope is the shape of the key, written down by the provider in advance. It’s why this question has a factual answer at all.
Here’s the one distinction worth keeping, because it gets blurred in both directions. Your account staying put is a different fact from nothing being copied. The mail is read, and to be read at speed it’s held. What the supplier holds, and for how long, is a real question. That’s the work of keeping client data out of model training, retention clause by retention clause. What belongs here is the first half of it. The mailbox is still yours, still where it was, still reachable by every route it always was.
Reading is not one thing
Ask what a piece of software can see and you get a list of nouns back. The useful answer separates three things that one word is doing.
First is contact, a model passing over the text of a message. It’s constant, and it happens to everything. It’s the entire reason the product does anything at all. Every product in this category works that way.
Second is reach, how far sideways the connection goes. Here most people’s picture is too small. It goes past email. Point’s privacy policy sets the reach out as a list, and the first three items are the ones to sit with:
- emails, messages, threads, recipients, senders, headers, metadata, attachments, files, and folders;
- calendar events, invitations, availability, RSVPs, reminders, participants, meeting links, and scheduling pages;
- contacts, identities, relationships, circles, labels, and organization membership;
(Privacy policy section 3.4, checked August 19, 2026.)
The calendar is the item worth stopping on. People brace themselves for the mail and forget what’s attached to it. A calendar tells you more than most correspondence: who you met, how often, for how long, and which week it stopped. It has to be there. Finding a slot for four busy people takes the calendar, and the mail alone gets you the five-message thread instead. It’s a second consent sitting inside the first, and a supplier that lists it in a numbered clause is telling you before you ask.
Third is residue, the part people leave out of the picture. Reading makes things. The same clause in the same policy runs on past what arrived into what was built from it: search indexes, embeddings, summaries, the tasks lifted out of a thread. A reader’s picture tends to stop at item one, and half of what exists is further down the list.
You can read what it concluded
Here’s the first thing in this subject that runs in your favor, and it’s easy to miss. It arrives as a settings screen rather than a promise.
Point forms views about your working life. That this sender outranks that one. That mail from a particular address belongs to the practice rather than the other venture. That when you write to a client on a Friday you sign off differently. Those views are how Point gets better at the work, and they build up whether or not you go looking for them.
They’re also written down where you can read them. The habits Point has picked up are held as separate, named items. You can open one, correct it, or delete it. The ranking Point applied to a thread sits on the surface of the thread. What that gives you is unusual, and the comparison is with a person rather than other software. A bookkeeper who’s been with you four years has formed a hundred views about your clients, and every one of them stays in their head. You infer them from behavior, slowly. You find out about the wrong one when it produces the wrong outcome.
Which speaks to the difficulty the last chapter left open. A summary that missed the only sentence that mattered reads exactly like one that caught everything. So reading the output tells you little. Reading what Point believes tells you a lot. A belief written in plain words can be plainly wrong, and a smooth paragraph hides that. If Point has decided a particular client is low priority, you see the decision now instead of the consequence later.
What Point did, in sequence, with a way back from each step, is a separate record and a later chapter. This chapter is about what Point thinks.
What it cannot see
Four blind spots, and only one is the sort you’d set up yourself.
The first is deliberate, and it surprises people. A message from a sender Point has no history with waits at the door. It sits in a quarantine you release it from, and Point leaves it outside the reading until you do. The message is there for you to look at, and the reading starts when you say so. The reason is worth following, because it shows what reading means for software of this kind. To a machine that reads instructions, a message is instructions. A stranger who gets prose in front of Point can try to tell Point things. The sentence in the eleventh paragraph of a plausible invoice can be addressed to the assistant rather than to you. So Point stays blind to unvouched senders. Here, reading and obeying sit closer together than they do for you.
The second is a lane you open on purpose. A message locked end to end stays between you and the recipient, and Point can’t read it. The cost is on the label, and it’s the whole point of the mechanism. A sealed message stays out of the ranking, out of the summaries, and out of your task list. Point works from the text, and that text stays sealed. That makes it a channel for the few things a year that need it, rather than a way to run a practice.
The third is the wall between businesses. If you run the firm and something else besides, each side stays behind its own wall. The line runs between the businesses you operate, rather than between the clients inside any one of them. That distinction does more work than it looks like, and it gets a chapter of its own further on.
The fourth is the largest, and it has no setting attached. Point sees the correspondence. The practice itself stays outside. The call where the client actually told you what was wrong. The ten minutes in the corridor after the meeting. The thing you’ve known about that family since 2014 and would never put in writing. All of that lives outside the mailbox, so all of it lives outside the picture. Every judgment Point makes rests on the written record of a relationship, and that record is partial and sometimes misleading. The lines inside a practice that most need respecting are often the ones nobody ever typed. That gap is what whether client financial data is safe here works through for a firm.
A blind spot is not neutral
The instinct on reading that list is to want more of it, and to go looking for the setting that draws the boundary tighter. Before you do, price it. A blind spot costs you something, and you find out late.
Whatever Point can’t see stays out of the ranking. It sits below the items at the top of your morning. The request in its third paragraph stays a request, rather than a dated task. Ten days on, with the reply still outstanding, it sits there quietly. The message looks ordinary, and the silence reads the same as everything being handled.
Which is the failure you already have, reinstalled by hand. A thing that goes wrong by being absent stays silent, and that’s the exact shape of the near miss that made you look at this category in the first place. So the argument for a boundary has to be worth that risk across the part of the mailbox it covers. For a few messages it usually is. For a whole category it rarely is.
So draw the boundaries deliberately, and keep them few. The reflex runs the other way, toward sealing whatever feels heaviest. Heaviest is exactly where a silent miss costs the most.
Why this one goes first
Everything in this chapter has a door that opens both ways.
You withdraw the permission at your provider, and the reading stops. You disconnect the account. What was made from the mail, you can ask about, itemize against the terms, and delete. Every decision here is one you can reverse, and that’s a real property to have. It’s the honest reason this question leads, rather than any claim that it’s the least exposure. It leads because it’s the one you can take back.
The next question has a different shape, and that difference is the largest single fact in this series. A withdrawal reaches as far as your own building and stops there. Once something has been written and delivered, it sits on hardware belonging to somebody who owes you nothing. Point’s undo covers what Point did, and a recipient’s mail server holds what it holds. Point puts a dial on how much gets to that stage, and the full inventory sets out what sits behind it. A message that has already arrived stays arrived.
So reading was the calm half of this. What goes out is the other one.