Email and SMTPSensitive data stops at the mail path.
RedactWall sits in the mail path you already run. It checks the whole message and refuses the ones that should not leave, before anything is accepted for delivery.
What that looks like
An account number sits in a quoted reply below the signature
Found, because the whole message is checked, not just the part you can see.
A loan officer forwards a member list to a personal webmail address
Refused before the message is accepted.
Someone asks who tried to send what, last quarter
Every refusal is already on the record, with the reason.
What it takes to switch on
Nothing is held. Because a message is refused rather than accepted and parked, there is no quarantine for your team to administer and no mailbox of ours holding your mail.
How far this is proven
Proven against a real clusterRedactWall inspects a whole message and refuses the ones that should not leave, proven against a real cluster. This broader product integration is outside the proposed first pilot. Verification against production mail servers remains separate. See where it stands today.
Every limit, in one place: Disclosures.
Review the proposed first pilot
The proposed first pilot covers ChatGPT text in managed Chrome and a separately verified Anthropic gateway path. Other integrations are part of the broader product.
- Coverage is published for this integration
- Proof status is shown explicitly
- Pilot scope is agreed before onboarding