The sensor and the enforcer, in the page.
A Manifest V3 extension for Chrome, Edge and Firefox. It reads the message box and the upload field on covered AI sites, classifies content on the device, and applies your policy before the request is sent.
Three things happen before send.
It detects on the device.
The challenge
A person pastes a payment instruction, a customer list or an API key into an AI prompt, or drops a spreadsheet into the upload field.
Why existing controls miss it
Network and endpoint controls see an encrypted request to an approved site. The content of the text box is invisible to them.
How Deltawall enforces it
The extension classifies the text and any attached file in the browser, with the same engine for both. Nothing is sent anywhere to be analysed.
It applies your policy.
The challenge
Different data needs different handling: an email address might be fine, an IBAN should be masked, a private key should never leave.
Why existing controls miss it
Binary allow-or-block controls either stop the work or let everything through.
How Deltawall enforces it
The policy engine resolves department, data class and destination to Allow, Log, Warn, Redact or Block. The user sees a banner that names what happened and why.
It records one line.
The challenge
When a regulator or auditor asks what left the organisation, a screenshot is not evidence.
Why existing controls miss it
Logs that store content create a second copy of the data you were trying to protect.
How Deltawall enforces it
The extension sends a data-class label, a salted hash and metadata. Never the prompt, never the file.
Exactly what it covers, and what it does not.
- Browsers
- ChromeEdgeFirefoxThe on-device model runs in Chrome and Edge. Firefox enforces with the deterministic detector layer.
- AI sites
- ChatGPTClaudeGeminiMicrosoft CopilotPerplexityDeepSeekCoverage is bounded to these sites, and the contract names them. The site catalogue updates without an extension release.
- Channels in the page
- Typed promptsPasted textFile pickerDrag-and-dropPasted files
- File types
- PDFDOCXXLSXPPTXCSVTXTMDJSONScanned PDFs and images are flagged as uninspectable. There is no OCR.
- Actions
- AllowLogWarnRedactBlockWarn can require a written business justification before the user proceeds.
- Deployment
- Chrome enterprise policyEdge enterprise policyFirefox policiesManaged configuration schema
- Failure mode
- Fails openIf the upload guard or the model errors or times out, the AI site keeps working.
Every payload it sends, on one page.
The extension's own options page lists the recent payloads that left the browser: data-class labels, truncated salted hashes and metadata. The IBAN, the BSN and the file contents never appear.
- Show it to the works council in the first meeting
- The privacy argument, made by the product
- Nothing to take on trust
What IT and security ask first.
Does it intercept traffic or install a certificate?
No. There is no TLS interception, no root certificate, no proxy and no kernel driver. The extension runs in user mode inside the browser sandbox.
Can users disable it?
Deployed through enterprise policy, the extension is force-installed and managed; users cannot remove it from a managed browser. Unmanaged browsers and private profiles outside your policy are not covered.
What happens when an AI site redesigns its page?
The extension carries several ways to find the message box and the upload field, and the site catalogue updates without a release. Coverage stays bounded to the sites we list.
Does it slow the browser down?
Detection runs locally on the text being submitted. If a scan errors or exceeds its time budget, the extension fails open rather than block the page.
See it stop real-looking data in a real browser.
A 30-minute technical walkthrough: a prompt redacted, a file stopped, the dashboard, and an evidence pack verified offline in front of you.
No slide deck. Synthetic data only.
