What each surface actually does.
This page states what every surface covers, one row at a time: what decides before data moves, what finds and reports it afterwards, and what runs on the device itself. How far each one is proven today is in Disclosures.
Coverage by surface
The product implements several surfaces. This reference describes their behavior; inclusion in the proposed first pilot is stated above.
| Surface | Level | What it does |
|---|---|---|
| AI tools and assistants | Decides before data leaves | Checks what configured applications explicitly route through RedactWall and what comes back, before either direction is forwarded. Every gateway decision is recorded, and a request that cannot be recorded is refused rather than allowed through. |
| Outbound email | Decides before data leaves | Checks the whole message, including attachments, and decides before it is accepted for delivery. There is nothing to recall afterwards. |
| Microsoft 365 and Google Drive | Finds and reports | Fetches and transiently inspects document bytes already sitting in configured drives, then reports findings without retaining source content in evidence or durable content storage. |
| AI agents and their tools | On the device | Approves or refuses tool calls routed through the RedactWall MCP guard before the upstream server runs, and checks results before the model receives them. Calls made through another route are outside the guard. |
| Laptops and browsers | On the device | Governs measured submission paths on supported origins in enrolled Chrome profiles, observes text clipboard generations on enrolled Windows devices, and watches activity in configured sync roots. Clipboard replacement or clearing is bound to the exact current generation; the observer does not know which application, destination or paste action may consume it, and cannot prove another application did not read the original first. Every decision a device reports is rechecked centrally, and any that does not match your policy is rejected. |
What it looks for, and how carefully
106 kinds of sensitive data, each built from the issuer’s own published format.
Numbers are checked for validity, not just shape. A value that looks like an account number but fails the issuer’s own arithmetic is not reported.
Exact-data matching against your own records, using a transformed copy, so the original values stay in your systems. If that copy fails to load, the system stops rather than quietly matching nothing.
Built to catch data that has been disguised, not only data in its plain form. Disclosures states how far this is measured today.
Start a supervised pilot
Work with RedactWall to confirm fit, agree the scope and verify one managed device before expanding.
- Coverage is stated surface by surface
- Proof status is published separately
- Pilots start with one governed path