Privacy Policy

Inbox Triage is made by Inbox Manager Pro, LLC ("we", "us"). You can contact us at admin@inboxmanagerpro.com.

• Your email data (messages, headers, sender lists and subject lines) is processed locally on your computer. We do not collect it, and it is not sent to us.
• The app communicates directly from your computer with your email provider (Google, Microsoft, or your IMAP server) to read and organize your mail. It also contacts a sender's unsubscribe address when you choose to unsubscribe from that sender, and it checks this website for updates. These are the only external connections the app makes.
• No email content is sent to any AI or machine-learning service. Senders are flagged by a rule-based classifier that runs on your computer.
• Deleting moves messages to Trash or Deleted Items. The app does not permanently delete mail.
• The app scans your Inbox only. It does not access your Sent mail.

For Google and Microsoft accounts, you sign in with your provider directly. Your provider gives the app access tokens, which are held on your computer and are not sent to us.

For IMAP accounts, the sign-in details you enter are stored in your operating system's secure credential store: the macOS Keychain, or Windows Credential Manager on Windows.

You can revoke the app's access at any time:

• Google: open the permissions page of your Google Account and remove Inbox Triage.
• Microsoft: open the apps and services page of your Microsoft account and remove Inbox Triage.
• IMAP: remove the account in the app, or change your password or app-specific password with your provider.

Inbox Triage's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

The app requests exactly two Gmail permissions (scopes):

• gmail.modify (a restricted scope). This is the working scope for everything the app does inside the mailbox. It reads message headers and sizes to build the per-sender inventory, fetches a full message only when you open it in the viewer, and lists and creates labels so an archive run can tag what it moved. Its write side is three label operations performed in bulk: adding Trash to move messages to the Trash, removing Inbox to archive them, and removing Unread to mark them read. Both actions are recoverable from inside Gmail, and the app never permanently deletes anything. A read-only scope cannot move or label anything, and the narrower label-only scope cannot read the headers the inventory needs, so this is the least permission that covers both halves of the product. The grant stays in a token file on your own computer. No server of ours ever receives it or sees any mail.
• gmail.settings.basic (a sensitive scope). This scope exists for one feature: blocking a sender. When you block an address, the app creates a Gmail filter for that address whose action is the same move to Trash you just performed, so the block keeps working while the app is closed. Unblocking deletes exactly that filter. The app touches only the filters settings and never reads or changes forwarding, vacation, delegation or any other setting. This scope is requested at sign-in but is not required to use the rest of the app; an older grant keeps working for everything except Block, which then asks you to reconnect that one account.

• Google user data is processed on your computer. It is not transferred to us or to any third party.
• Google user data is not used for advertising.
• Google user data is not used to train AI or machine-learning models.
• No person at Inbox Manager Pro, LLC reads your Google user data.

The app requests exactly two Microsoft Graph permissions, both delegated (they act only as you, on your own mailbox). Sign-in also includes the standard openid, profile and offline_access permissions that Microsoft's sign-in library adds on its own. The app does not request User.Read or any permission to send mail.

• Mail.ReadWrite. This one permission covers everything the app does inside an Outlook mailbox. It reads message headers and sizes to build the per-sender inventory, tracks changes since the last scan so repeat scans stay quick, and fetches a full message only when you open it in the viewer. Its write side is moving messages between folders: a trash run moves messages to Deleted Items, and an archive run moves them to Archive. Both are recoverable inside Outlook, and the app never deletes a message. A read-only permission cannot move anything, and the more limited read permissions cannot reach the sender and subject fields the inventory needs, so this is the narrowest permission that covers both halves of the product. Tokens stay in a file on your own computer. No server of ours ever receives them or sees any mail.
• MailboxSettings.ReadWrite. This permission exists for one feature: blocking a sender. When you block an address, the app creates an Inbox rule that moves mail from that address to Deleted Items, so the block keeps working while the app is closed. Unblocking deletes exactly that rule. The app's only delete actions in Outlook remove a rule it created, never a message. This permission is requested at sign-in but is not required for scanning, trashing or archiving; an older grant keeps working for everything except Block, which then asks you to reconnect that account.
• The email address shown in the app comes from the sign-in response, not from a profile lookup, which is why User.Read is not needed.
• In work and school accounts, these permissions are not on Microsoft's default user-consent list, so your organization's administrator may need to approve Inbox Triage before you can connect.

• Data from your Microsoft account is processed on your computer. It is not transferred to us or to any third party.
• It is not used for advertising and not used to train AI or machine-learning models.
• No person at Inbox Manager Pro, LLC reads it.

We may collect payment details when you purchase the app.

Payments are processed by Stripe. Stripe handles your payment information under its own privacy policy.

You do not need a separate Inbox Triage account to use the app. You sign in directly with your email provider.

If you email us, we receive your email address and whatever you include in your message, and we use it to reply to you.

This website uses no analytics, no tracking pixels and no third-party cookies. Fonts are hosted on this site, so loading a page does not send your visit to anyone else.

We do not sell or share your personal information. Payments are processed by Stripe, which receives the information needed to process your payment and handles it under its own privacy policy.

Data processed on your computer stays on your computer. Everything the app stores locally lives in one per-user folder — ~/Library/Application Support/InboxTriage on macOS, or %LOCALAPPDATA%\InboxTriage on Windows — plus credentials in the operating system's secure credential store and the app's embedded web view's own storage. Removing that folder removes the app's local data.

Support emails are kept for 12 months.

Our main safeguard is that your mail stays on your computer: it is processed locally, and we hold no mail data on our systems.

No method of storing or transmitting data is perfectly safe, and we cannot guarantee absolute security. Keeping your computer and your email account secure also matters.

Inbox Triage is not directed to children under 13, and we do not knowingly collect personal information from them.

This policy describes rights under United States privacy law. You may have the right to ask what personal information we hold about you, to have it corrected or deleted, and to object to certain uses.

Because we do not hold your mail data, most requests are answered by explaining that we have none. For anything we do hold, such as support emails, contact us and we will help.

If we change this policy, we will update the "Last updated" date at the top of this page and post the new version on this site and in the app.

Questions about this policy? Email admin@inboxmanagerpro.com.