Put a policy between sensitive data and AI.
Built for midmarket security teams. Start with a guided pilot for your managed ChatGPT workflow, and check the decision, the destination and the evidence before expanding to more staff.
Free guided pilot. Up to 30 days, up to 50 managed devices.
After staff-confirmed conversion: $12 USD, per managed device, per month.
A RedactWall employee confirms seats and terms before billing.
Pricing and conversionOne message, from the composer to the record
The first pilot is the RedactWall Chrome extension on an enrolled Windows 11 device, watching the ChatGPT composer. This is what happens to one message that carries sensitive values.
Managed installation and ChatGPT composer interception have not yet been run on a managed Windows 11 endpoint. Dated proof is published before enrollment.
The first pilot, end to end
The RedactWall Chrome extension on an enrolled Windows 11 device, watching the ChatGPT composer.
What the employee types
chatgpt.com, in the managed Chrome profile
Set up the direct deposit. Routing number: 555000005, checking account number 000123456789. Draft the confirmation letter.
What leaves the browser
Submission is held in the extension until the substitution is made
Set up the direct deposit. Routing number: [REDACTWALL:ROUTING_NUMBER:1], checking account number [REDACTWALL:BANK_ACCOUNT:1]. Draft the confirmation letter.
What the employee is shown
Two mandatory hard stops were removed before this was sent: a routing number and a bank account number. The rest of your message went through. Your organization’s policy owner set this. The extension encrypted and queued the coaching copy for delivery. RedactWall can retain it for authorized, audited review under your organization’s employee activity retention setting.
What lands on the record
One row in your own evidence, readable by the people you name
| Observed | Surface | Decision | Findings |
|---|---|---|---|
| 10:42:07 UTC | Browser · Text submission | Mandatory protection | Routing number, Bank account |
The record stores the kinds of finding and the action taken, not the values. The clock reading above is a depiction; this walkthrough publishes no counts, rates or durations, because it has measured none.
106 kinds of sensitive data, each built from the issuer’s own published format.
Audit metadata, separate activity
The audit record stores decision metadata, including the kinds of finding and the action taken, rather than prompt bodies. Employee activity can retain encrypted content under separate access and retention controls.
Refused, not waved through
A request that cannot be checked is refused rather than waved through.
A separate application gateway path.
An application explicitly routed through the Anthropic gateway is a separate path with its own verification.
The published Anthropic live-service proof is dated August 14, 2026. It does not establish current release readiness or browser coverage.
Typed into an AI assistant
Set up the direct deposit. Routing number: 555000005, checking account number 000123456789. Draft the confirmation letter.
- Read complete
- Decide complete
- Record complete
What the AI provider receives
Set up the direct deposit. Routing number: [REDACTWALL:ROUTING_NUMBER:1], checking account number [REDACTWALL:BANK_ACCOUNT:1]. Draft the confirmation letter.
Two hard stops in one message. The rest of the prompt went through.
The answer comes back the same way and is checked before staff see it.
Recorded on your evidence stream
A sample prompt with made-up values.
Every RedactWall surface, and what it governs
The broader product has five governed paths plus a shared evidence plane, each with its own coverage and proof boundary. The proposed first pilot is limited to the browser and gateway paths stated above.
Integration reference pages distinguish implemented interfaces from dated live-service proof. They do not expand the first pilot scope.All integrations
What a governed path can change
Examples across the broader product. Availability depends on the deployed surface; email and file workflows are outside the first pilot.
An application explicitly routed through RedactWall sends a customer file to an AI provider
The routed request is stopped before forwarding, and the attempt is on the record.
A response returning through the gateway repeats an account number
Caught before the response is forwarded to the application.
Someone emails a customer list to a personal account
Refused before the message is accepted for delivery.
An auditor asks what RedactWall decided on governed paths last quarter
Hand over a sealed package for that period, with the verifier’s stated completeness limits.
Proof you do not have to trust us for
The verifier ships to you and runs on your systems. It checks that entries present still match the record as written, reports signed-checkpoint coverage, and states that it does not prove every event was recorded.
Example audit chain verified.
$ redactwall verify-audit-chain --plane tenant --anchor /var/lib/redactwall/anchor
verify-audit-chain: plane tenant, tenant ten_a1a1a1a1a1a1a1a1a1a1a1a1
verify-audit-chain: head sequence 3, key version 1
verify-audit-chain: head digest sha256:e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4e4
verify-audit-chain: walked 3 entries through sequence 3
verify-audit-chain: signed checkpoint at sequence 3 matches this chain's entry there
verify-audit-chain: VERIFIED - every entry from 1 to 3 re-derived under its own key and MAC domain, and every link digest matched its predecessor.
Example output, reproduced in the format the commands print. The identifiers and digests are examples, not values from any deployment.
Straight answers, limits included
Everything about where the product stands today is on one page.
Start with a path you can prove.
Work with RedactWall to confirm fit, agree the scope and verify one managed device before expanding.
- Pilot starts with one governed surface
- Audit metadata and retained employee activity have separate controls
- Coverage and proof status are published