Financial Services Financial Promotions Tipping-Off & AML Client Confidentiality MNPI & Market Abuse Suitability Forward-Looking Antitrust
Market Abuse

Inside information leaks in a single line.

The deal is not public, and an email says act before it is. Under the market abuse rules, that line can be unlawful disclosure of inside information. VerbaPulse flags the non-public deal disclosure in Outlook and Gmail before the message sends.

The problem

The disclosure is the offence, not the trade

Inside information is precise, non-public information that would likely move a price if it were known. Under the Market Abuse Regulation in the EU and its UK equivalent, disclosing it outside the normal course of duties, or dealing on it, is market abuse. The leak is often a sentence, not a trade: a colleague sharing a deal that has not been announced, or hinting that someone should act before it is.

The risk concentrates with the people who legitimately know something the market does not, the deal teams, advisers, and relationship managers. They are not trying to break the rules. They are moving a process along, and the helpful line ("between us, this signs Friday") is the disclosure. Surveillance and trade monitoring look for the consequence. The cheaper place to stop it is the sentence.

What it catches

The line that shares what is not public yet

VerbaPulse reads the draft as it forms and flags the span that discloses non-public information, with a plain reason. Real output from the product:

VerbaPulse High
"Just between us, the acquisition signs Friday, you may want to act before it is public."
Confidential business information disclosure
Remove this disclosure before sendRemove
For a non-public disclosure the safe move is removal, not a reword. VerbaPulse marks the exact span while the message is still a draft.

The same check covers the related patterns:

How it works

In the inbox your team already uses

01
Install in minutes
The Outlook add-in deploys org-wide through the Microsoft 365 admin center, and the Chrome extension covers Gmail. No new tab, no change to how the team works.
02
Write as usual
As the message forms, a disclosure span is flagged with severity and a plain reason, so the writer sees the leak in the line they just wrote.
03
Catch it before it sends
The risky line is removed while the message is still a draft. Anonymized events feed an audit trail your compliance team can show.
Where this fits

A communication check, not trade surveillance

VerbaPulse does not watch trading, order flow, or your surveillance alerts, and it does not decide what is inside information. Those belong to your market abuse framework. VerbaPulse sits at the one point they do not cover: the outbound message, where a helpful line becomes an unlawful disclosure. It is one control inside email compliance for financial services, and it complements the surveillance and archiving systems you already run.

For the evidence behind this, our language risk benchmark runs real, anonymized cases through the product and reports what it flags.

FAQ

Common questions

What counts as unlawful disclosure of inside information?
Under the Market Abuse Regulation, inside information is precise, non-public information that would likely affect a price if it were public. Disclosing it outside the normal course of duties, or acting on it, is market abuse. In an email this usually looks like sharing a non-public deal or result, or nudging someone to act before an announcement. This page describes language risk and is not legal advice.
How does VerbaPulse help?
It flags the disclosure itself: a line that shares a non-public deal, a "this is not public yet" framing, or a nudge to act before an announcement. VerbaPulse catches that span before the message sends and marks it for removal, while the wording can still change.
Does VerbaPulse monitor trades or replace market abuse surveillance?
No. It does not watch trading, order flow, or your surveillance alerts, and it does not decide what is inside information. Those stay with your market abuse framework. VerbaPulse only checks the outbound message for language that would disclose non-public information.
Is email content stored anywhere?
No. Drafts are analyzed in memory and discarded immediately. They are never stored and never used to train AI models. The audit trail keeps anonymized risk events (type, severity, action taken), never message text and never named individuals.

See it on the messages your team actually sends

Book a demo →