Accumen Outreach Tracker — Privacy Policy

For the Chrome extension. Last updated 22 August 2026. Published by Accumen Intelligence Ltd, Shelton Street, London WC2H 9JQ, United Kingdom.

The short version. The extension reads the mail thread you have open in order to work out what happened to outreach you sent. Your messages are read inside your browser and are not transmitted, with one exception that only you can trigger: if you click Write with Accumen in a Gmail compose window, the recent messages of that thread and what you have typed are sent to Accumen to write a draft. What we otherwise receive is the outcome: which prospect, what happened, and which email in your sequence it relates to.

Why the extension needs access to your mailbox

Accumen helps you research prospects and prepare outreach, but it does not send your email — you do, from your own mail client. That means it cannot otherwise tell whether a message was delivered, bounced, or answered. The extension exists to close that gap.

What it reads

On mail.google.com and Outlook Web, it reads the currently open thread: sender, recipients, subject, and message text. It does this only to decide whether the thread concerns a prospect on your Accumen board and, if so, what became of it.

What leaves your browser

For a matched message, the extension sends Accumen:

Message bodies, subjects, sender names and recipient lists are not transmitted, except when you click Write with Accumen, which is described below.

The one exception, stated plainly

When a message is a delivery failure notice, the text of that notice is sent to Accumen so its cause can be determined — specifically, whether the address did not exist or whether a valid mailbox refused the message. Those are opposite findings and telling them apart requires the wording of the notice.

Such a notice is generated by a mail server, not written by a person, and is about a message you sent. Ordinary correspondence is never transmitted.

When you ask for a draft

In Gmail, the extension adds a Write with Accumen button above each compose window. Nothing is read or sent for this until you click it, and the first time it asks you to confirm. When you click, it sends Accumen:

Accumen uses this only to write the draft you asked for. The text is processed by Google's Gemini API to produce it, under Google's API terms. Accumen does not store the text, does not use it to train models and does not share it with anyone else; it counts how much the writing service was used for your workspace. The draft is shown to you. The extension never sends the email, and you decide whether to apply it.

What is stored, and where

Outcomes are stored against your own Accumen workspace, in Google Cloud Firestore, and are visible only to members of that workspace. The extension keeps a connection token and a short list of recently handled message identifiers in local browser storage, so the same message is not recorded twice.

What we never do

Access, and how to end it

The extension records nothing until you connect it from Accumen under Settings → Connections. Disconnecting there revokes its access immediately. Removing the extension from Chrome also deletes everything it stored locally.

Outcomes already recorded belong to your workspace and can be deleted with the rest of your workspace data from Settings.

Contact

Questions, or a request to access or delete your data: redialmedia@gmail.com.