Skip to content

What an app can and can't pull out of your inbox

On this page

What an app can pull out of your inbox comes down to two gates. The first is what you let it open when you connected it. The second is what it can recognize once it’s reading. An app with full read access can find most of the asks written into your mail, with a date and a name attached. What it can’t pull out is anything that was never written down, anything locked behind a link, and a few kinds of ask that trip up careful people too. Below is the detail behind each part, so you can judge any app, ours included.

  • The permission sets the ceiling. Some apps can see who wrote and when, but never a word of the message. An app like that can’t find a single ask.
  • A store’s privacy label is the developer’s own account. The consent screen from Google or Microsoft is the record to read.
  • Full read access finds the plain asks well. Sender, date, the request and a named deadline come out cleanly.
  • Some asks come out shaky. Relative dates, conditions, group asks, old asks in quoted text, and asks inside images or files.
  • Some asks were never in the mailbox. A call, a text, a client portal, and what you already did about it.

Two questions inside “what can it read”

When you ask what an app can read, you’re usually asking two things at once. Is it allowed to see my mail? And if it sees it, does it understand what the mail wants from me?

The first is a fact you can look up. Google and Microsoft write down each permission an app can ask for, and they show it to you before you agree. The second is about judgment. It changes from one app to the next, and it’s never perfect.

Keep the two apart and most of the confusion goes away. A tool can be fully permitted and still miss the ask in paragraph three. A tool can be brilliant at reading and still see nothing, because you gave it headers only.

What you let it open when you connected it

When you sign in to an app with Google or Microsoft, the screen lists what the app is asking for. Each line maps to a named permission. Here’s what the common mail permissions allow, in each company’s own words.

PermissionWhat the provider says it allowsCan it find an ask?
Gmail gmail.metadata“View your email message metadata such as labels and headers, but not the email body.”No. It sees who and when, never what was asked
Gmail gmail.readonly“View your email messages and settings.”Yes
Gmail gmail.modify“Read, compose, and send emails from your Gmail account.”Yes, and it can act on the mail too
Gmail gmail.send“Send email on your behalf.”No. It covers sending only
Microsoft Mail.ReadBasicRead mail “except body, previewBody, attachments and any extended properties.”No. The body is exactly what’s left out
Microsoft Mail.Read“Allows the app to read the signed-in user’s mailbox.”Yes

The Gmail wording is from Google’s scope list for the Gmail API. The Microsoft wording is from the Microsoft Graph permissions reference. Both were checked October 5, 2026.

Notice the Microsoft line in the middle. Mail.ReadBasic sounds like reading. It covers the subject, the sender and the date, and leaves out the body and the attachments. Ask an app holding only that permission for your action items, and it has nothing to look at. Headers-only access is a real privacy choice, and a good one for some tools. It’s the wrong tool for finding asks.

Any app that reads the body of Gmail messages holds a scope Google calls restricted. Google puts conditions on those apps. Its API Services User Data Policy sets the use limit:

Limit your use of data to providing or improving user-facing features that are prominent in the requesting application’s user interface

In plain terms, mail read for a feature you can see can’t quietly feed something you can’t. The same policy says that, depending on the API and the number of users, apps “must pass an annual security assessment” from a Google-designated third party. That’s a floor under the whole category, set by Google rather than by the vendor.

What happens on the Google side when you connect is covered step by step in connecting Gmail to another app. The Microsoft side is connecting Outlook and Microsoft 365.

What the store’s privacy label tells you

If you searched this question, you probably met an app store page first. Those pages carry a privacy section. On Google Play it’s called Data safety. On the App Store it’s the privacy details.

Both are written by the developer. Google says so directly. Its Data safety help page notes that even an independent security review “does not verify the accuracy and completeness of the developer’s Data safety section disclosure.” Apple’s guidance to developers puts the job on them too: “You’re responsible for keeping your responses accurate and up to date.”

So a label is useful as the developer’s own statement. The consent screen is the stronger record. Google or Microsoft grants the permission listed there, and you can see it in your account and take it away.

What a reading app pulls out cleanly

Say the app has full read access. Here’s what it can lift out of a thread, roughly in order of how reliably it comes out.

What’s in the threadHow well software pulls it outWhy
Who sent it, to whom, and whenExactlyIt’s in the headers, in fixed fields
A plain request: “Can you send the signed lease?”WellThe ask is stated and the verb is clear
A request with a named date: “by October 14”WellThe date is written in full
An ask phrased as a statement: “The form needs your signature”UsuallyModern tools read meaning, not just question marks
A second ask after the first: “Also, check the invoice address”UsuallyA tool reading the whole message doesn’t stop at the first ask
A promise in your own sent mail: “I’ll get that to you Monday”Usually, if the tool reads sent mailIt’s your commitment, written in your words
An ask in the body of a text PDFSometimesIt depends on whether the app opens attachments at all

The last row is the one to check with any tool. Reading attachments is a separate choice for the app maker. Plenty of tools stop at the message body. Where action items hide inside a message, and why people miss them too, is the subject of finding the action items buried in your email.

What comes out shaky

These are the asks where software and careful readers both stumble. Knowing them tells you where to look twice.

The askWhat goes wrong
“Can you get this to me by Friday?”Which Friday? The app works it out from the date the message was sent. A message read late, or forwarded on, can land on the wrong week
“End of next week” or “before the board meets”There’s no date to read. The app guesses, or leaves the date blank
“If you want the Tuesday slot, confirm by Friday”A condition. It may be optional, and only you know whether you want the slot
“Could one of you book the caterer?” on a reply-allSoftware can see the ask. It can’t see who in the group is meant to take it
An ask three replies down in the quoted textIt may still be live, or long since handled. The quoted text looks the same either way
An ask in a screenshot, a scan or a photo of a pageIt’s a picture of words. Only a tool that reads text out of images will see it
“Sorry, ignore that, I sorted it” in a later replyA good tool links the two. A weaker one keeps the first ask on your list

The fix in every case is the same. Each item on the list should carry a link back to the exact words that produced it. Then a wrong date or a stale ask takes seconds to correct, because the sender’s sentence is one tap away.

What was never in the mailbox

The largest gap has nothing to do with the app. Some of the work your clients ask of you never arrives as readable mail.

  • The call. A client asks for something on the phone and nobody writes it down. No app can find it.
  • The text or the chat. It lives on your phone or in another app, unless that channel is connected too.
  • The portal notice. “You have a new secure message” from a bank, a court system or a document-signing service. The real ask sits behind a login.
  • The locked message. Gmail’s confidential mode sends people on other mail apps a “View the email” link and a passcode step, per Google’s help page. What reaches the mailbox is the link.
  • What you already did. You finished the task on a call or dropped the file in a shared folder. Unless something about it shows up in the mail, the app can’t tell it’s done.

These sit at the edge of the mailbox, past the reach of any setting. A good tool helps by being right about everything inside it, so the outside is the only thing left to carry in your head.

A ten-minute test for any app

You can check what any tool finds for yourself. Send yourself a few test messages from a second address, wait for them to land, and see what comes out. This works for any tool that claims to find asks, ours included.

  1. The buried ask. Two paragraphs of news, then “I’ll need your numbers by Thursday.”
  2. The relative date. “Can you send this over by Friday?” Check which Friday it picked.
  3. The ask in a file. Attach a short PDF that says “Please sign page 2 and return by the 20th.” Write nothing in the body but “See attached.”
  4. The ask in a picture. Paste a screenshot of a sentence asking for something.
  5. The group ask. Copy a second address of yours and write “Can one of you confirm the venue?”
  6. The condition. “If you’d like the early slot, let me know by Wednesday.”
  7. The canceled ask. Send an ask, then reply to it with “Never mind, all sorted.”

Then look at what the tool produced. Count what it caught and what it missed. Look at the dates it chose. Above all, check whether each item takes you back to the words that created it. A tool that misses two of seven but shows its working is easier to live with than one that catches six and hides how.

If you’d rather compare tools side by side, the best email task tools for a small firm lays out the kinds.

Where Point sits on both gates

Point is an email client. It runs on top of your existing Gmail or Microsoft mailbox, with full read access, so it reads whole threads as they land, including your sent mail. Where a thread wants something from you, Point drafts a task with the date the thread names. Each task links back to the words that asked. Point can also answer questions about an attached PDF, with a link to the line the answer came from.

What happens to each task depends on how you’ve set the dial for tasks.

  • Suggest-only. You see the ask Point spotted, and turning it into a task is your call.
  • Review. The task is drafted and held until you say yes. Review is the starting position for every kind of action on a new account.
  • Handled outright. Point adds the task to your list without stopping to ask.

Tasks have their own setting, apart from replies and scheduling. Setting how much your inbox does on its own shows each position.

Point has gaps of its own, and they’re the ones on this page. It can’t hear the call or log in to the client portal. A conditional ask is a judgment call for Point too. A vague date may come through blank or wrong, and the link back is how you catch it. Mail that Point treats as hostile waits in quarantine, outside the reading, until you release it. An ask in that message isn’t on your list until then.

How the date is chosen, and how Point notices you’ve already finished something, has its own page: email task management, without writing it down. The full list of what Point handles sits on the benefits page.

Common questions

Can an app read my email without my permission?

Through Google’s or Microsoft’s sign-in, an app gets only the permissions you approved on the consent screen. You can see the app listed in your Google or Microsoft account, and you can remove it there. An admin on a work account may also control which apps can connect at all.

What’s the difference between an app reading metadata and reading my email?

Metadata is the envelope: sender, recipients, date, subject and labels. Reading the email means the body and often the attachments. Google’s gmail.metadata scope and Microsoft’s Mail.ReadBasic permission both leave the body out. An app limited to those can sort mail by who sent it, but it can’t find what a message asks you to do.

Is the Data safety section on Google Play reliable?

It’s the developer’s own statement. Google says an independent security review doesn’t verify that disclosure for accuracy and completeness. Read it as a starting point. The permissions on the Google or Microsoft consent screen are the stronger record of what an app can open.

Can AI find action items in attachments?

It depends on the tool. Reading attachments is a separate choice for each app, and many stop at the message body. A text PDF is the easiest case. A scan or a photo needs a tool that reads text out of images. Test it by sending yourself a PDF with an ask inside and nothing in the body.

Why did an app put the wrong date on a task from my email?

Usually because the email used a relative date like “Friday” or “end of next week.” The app works out the real date from when the message was sent, and that can land on the wrong week. Phrases with no date at all, like “before the board meets,” leave it guessing. A link back to the original words is what lets you fix it in seconds.

Will an app know when I’ve already done the task?

Only if the evidence is in the mail. A reply with the file attached, or a “thanks, got it” from the client, can show the task is finished. Work done on a call or in another system leaves no trace in the mailbox. Once an ask is on your list, carrying it through to done is covered in what turns an ask into a loop you can close.

Ready for a calmer inbox?

Join the private beta

We're onboarding a few teams at a time. Leave your email, confirm it once, and we'll send an invitation the moment a place opens.

By joining you agree to our privacy policy.

Private beta

What you're joining

It runs on the mail you have

Point sits on top of Gmail or Outlook. Your address, your history and your contacts stay exactly as they are, so there is nothing to migrate.

You set how much Point does

Out of the box everything waits for your review, replies included. You hand over only what you trust, one kind of work at a time.

Join the private beta

We're onboarding a few teams at a time. Leave your email, confirm it once, and we'll send an invitation the moment a place opens.

By joining you agree to our privacy policy.