Client Confidentiality

Confidential client data leaves in ordinary emails.

A name next to a balance, a deal value forwarded to an external broker, a client list attached to a pitch. No intent to breach, just someone moving things along. VerbaPulse flags confidential client disclosures in Outlook and Gmail before the message sends.

Book a demo → See pricing

The problem

The breach is usually an accident in an everyday message

Wealth managers, private bankers, and advisers handle highly sensitive client information all day, and most confidentiality slips have no bad intent behind them. The costly exposure is the everyday one: a client named alongside a balance, an unannounced transaction mentioned to a counterparty, a full client list attached so a colleague "has everything for the pitch". The duty is owed under client confidentiality and data protection law (UK GDPR and the Data Protection Act in the UK, GLBA in the US, banking secrecy regimes across the EU), and cross-border private client work raises the stakes further.

The usual control finds it after the fact. Archiving keeps a copy, supervision samples a slice, and a slip surfaces in review once the information has already reached the wrong inbox. The moment that actually matters is earlier, while the sentence is still a draft.

What it catches

Confidential client disclosures, at the moment of writing

VerbaPulse reads the draft as it forms and flags the span that exposes confidential client information, with a plain reason. Real output from the product:

VerbaPulse High

"Here is the client's name and the policy value for the case, forwarding to the external broker."

Confidential client information disclosure

Remove before send, or check the recipientRemove

For a 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 patterns a keyword filter misses, because it reads meaning, not just identifiers:

A client's name placed next to a balance, a deal value, or a position.
Unannounced transactions shared before they are public ("moving 4 million out of the fund next week").
Full client lists or holdings attached to an external pitch or forward.
Secrecy requests that signal something should not be in writing ("keep this between us").
Recipient awareness with NDA Guard: a warning when confidential content goes to someone who has not signed an NDA.
Your own rules: upload your confidentiality policy and VerbaPulse enforces it on every draft.

How it works

In the inbox your team already uses

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 writes.

Write as usual

As the draft forms, a confidential disclosure is flagged with severity and a plain reason, and NDA Guard adds a recipient check when one is configured.

Catch it before it sends

The exposed span is removed while the message is still a draft. Anonymized events feed an audit trail your compliance team can show.

Where this fits

The writing layer, alongside DLP and archiving

Traditional data loss prevention works at the network or file layer and catches known structured patterns. VerbaPulse works at the writing layer, on the meaning of the sentence, so it catches a client's name placed next to a balance even when no card or account number is present. It is one control inside email compliance for financial services, and it complements your DLP, archiving, and access controls rather than replacing them.

Email content is never stored: drafts are analyzed in memory and discarded immediately.
Nothing is used to train AI models.
The audit trail is anonymized by design: risk types, severities, and outcomes, never message text or named individuals.
With NDA Guard, confidentiality becomes recipient-aware, checked against the NDAs you have actually signed.

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 kind of confidentiality slips does VerbaPulse catch?

The everyday ones: a client's name alongside a balance or a deal value, a client list attached to an external pitch, an unannounced transaction shared to move things along, and secrecy requests like "keep this between us". VerbaPulse flags the span as a confidential client disclosure before the message sends and marks it for removal.

How is this different from DLP?

Traditional data loss prevention works at the network or file layer and tends to catch known patterns like card or account numbers. VerbaPulse works at the writing layer, on the meaning of the sentence, so it catches a client's name placed next to a balance even when no structured identifier is present. It is a complement to DLP, not a replacement.

Does it know who is allowed to receive the information?

With NDA Guard, yes. You can upload your signed NDAs, and VerbaPulse warns when confidential content is addressed to a recipient who has not signed one, so an external broker or a new counterparty triggers a check the internal team would not.

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.