A tool that reads drafts has to clear IT and security before anyone uses it. VerbaPulse is built to pass that review: no mail-flow change, no email storage, nothing new to host, and clear answers to every question on your questionnaire.
Any product that touches message content lands on the security team's desk, and rightly so. The default answer is no until the data path, storage, and access model are understood. Most "AI writing" tools fail here because they are vague about where content goes.
VerbaPulse is built the other way around: the smallest possible data footprint, nothing in the delivery path, and an architecture that is easy to verify. This page is the short version; the Security page has the specifics.
VerbaPulse runs client-side: an Outlook add-in and a Chrome extension. There is no inbound connector, no journaling rule, and no server you have to stand up or patch.
For the full processing description, transport details, and sub-processor table, see the Security page, our privacy stance, and the DPA.