Skip to main content
On the device

Device & Browser ProtectionGovern supported paths on the laptop.

Some sensitive data moves on a laptop instead of through the hosted gateway. The Chrome extension governs measured submission paths on supported origins in enrolled profiles. The Windows sensor observes text clipboard generations and can replace or clear a transformation-required value only while that exact generation remains current. It does not know which application, destination or paste action may consume it, and cannot prove another application did not read the original first.

The first pilot

One message, from the composer to the record

The managed Chrome extension is the only endpoint component the first pilot installs. This is the path it governs.

The first pilot, end to end

The RedactWall Chrome extension on an enrolled Windows 11 device, watching the ChatGPT composer.

01

What the employee types

chatgpt.com, in the managed Chrome profile

chatgpt.comEnrolled profile

Set up the direct deposit. Routing number: 555000005, checking account number 000123456789. Draft the confirmation letter.

Send
02

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.

03

What lands on the record

One row in your own evidence, readable by the people you name

ObservedSurfaceDecisionFindings
10:42:07 UTCBrowser · Text submissionMandatory protectionRouting 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.

Outside the first pilot

Clipboard generation: card 4111 1111 1111 1111

Replaced while generation current

No paste destination inferred

In practice

The broader endpoint implementation

These capabilities have distinct limits. They do not expand the proposed first pilot beyond the scope above.

A transformation-required value appears in the Windows text clipboard

The agent replaces or clears the exact current generation when it can; it does not identify a destination or intercept a paste.

Files land in a folder that syncs to a staff member’s personal cloud

Observed after the local write, then reported and handled under policy.

Enrolled Windows machines report supported AI application signals

Installed, declared, seen-running and tool-ran states stay distinct; only tool-ran is positive evidence of use.

A device reports that it blocked something

The server confirms it against your rules before it counts.

What you get

What you get

Reach where no server sits in the path

Measured AI-site submission paths, generation-bound Windows clipboard observation, and configured cloud-sync roots on enrolled devices.

Reported inventory before you enforce

Keep installed, declared, seen-running and tool-ran states distinct across enrolled machines; only tool-ran is positive evidence of use.

Verified, not believed

A device claim is checked centrally against the rules your risk owner approved, and refused if it disagrees.

One rule set

A reported clipboard-generation decision and a governed browser submission are judged under the same approved policy and land on the same record.

Boundaries

Where this fits with the other surfaces

What your applications send to an AI provider is covered by AI Data Protection, and an agent’s tool calls by AI Agent Security.

Start with one managed device

Confirm the policy and device health, run the agreed synthetic test, and inspect the resulting evidence before expanding the cohort.

  • Measured submission paths on supported origins only
  • Clipboard replacement is bound to the current generation
  • No destination-aware paste interception is claimed
  • Reported device decisions are rechecked centrally