Matters Browser Agent — Privacy Policy
Draft for legal review. Host at a stable, public URL with no login wall, and set that URL on the Chrome Web Store Account page before submitting.
Chrome Web Store & Code Behavior Consistency Guarantee
This document must match, exactly, both the data disclosure in the Chrome Web Store developer dashboard and the behaviour of the code. Google's stated penalty for a discrepancy between the three is suspension of every item the publisher owns and a ban of the publisher entity. When a collector or a default changes, this file changes in the same release.
What this extension is
Matters Browser Agent is an enterprise observability tool. It is installed by an organisation's IT administrators through managed-browser policy, on devices that organisation manages, and it is configured entirely by that organisation.
Out of the box it collects nothing.
With no administrator configuration there is no destination, no credential and no content capture; the extension installs and remains inert. Every collector described below is off until an administrator turns it on by name.
The deploying organisation is the data controller.
Matters AI supplies the software and, where the organisation chooses, operates the prompt-evaluation service described below as its processor. Matters AI does not otherwise receive, store or have access to the records.
What is recorded
On devices where an administrator has enabled the relevant collector:
File uploads and downloads
Filename, size, MIME type, SHA-256 hash, destination host or save path. Not file contents.
Clipboard activity
Copy, cut and paste events, with the value's length, shape and a salted SHA-256. Whether the value's text itself is included is an administrator setting, off by default.
Navigation
Top-level page navigations, including the full URL.
AI prompts
Text submitted to ChatGPT, Claude and Gemini. Whether that text is stored in the record, as opposed to only evaluated and discarded, is an administrator setting, off by default.
Device and principal context
A device identifier, the signed-in work email address, the application-level account in use, and tab session context, attached to every event.
Agent health
A heartbeat describing the extension's own state and any gaps in its coverage.
Authentication information
The extension is built to avoid handling secrets, and does not fully avoid it. Stated precisely, because the distinction matters:
Credential-shaped clipboard values
Password-manager output, one-time codes, private keys, JSON Web Tokens and API keys — never have their text transmitted, in any configuration. The record instead carries the value's length and shape, a salted SHA-256 of it, and a label naming the kind of secret that was withheld.
Authentication tokens observed in transit
Read to resolve which application account is in use. Identity claims such as an email address are retained; the token, its signature, its scopes and its session claims are discarded and never transmitted.
Both are disclosed in the Chrome Web Store listing as collection of authentication information, because a salted hash of a password is still derived from that password.
What is never recorded
Properties of the code, not settings an administrator can change:
Keystrokes, screenshots, and page content outside the three named AI endpoints.
The contents of request bodies outside those three endpoints. To detect file uploads the browser delivers request bodies to the extension on every origin, but outside the named AI endpoints no body content is retained.
Only derived metadata is extracted: the shape of the body, form field names, filename-shaped values, the declared byte count, and — on Chrome only — the local path of a file being uploaded. Form field values are never read, so a password typed into a login form is not captured.
The text of credential-shaped clipboard values, as above.
Bearer tokens.
Enforcement: what the extension can block
By default the extension is observational: with no administrator configuration it blocks nothing at all. An administrator may enable either of two enforcement controls. No other enforcement path exists in the source.
Domain blocking
Off by defaultA list of domains the organisation supplies is handed to the browser's own declarativeNetRequest engine, which blocks matching requests inside the network stack. The extension never sees, reads or modifies the requests that match, and cannot inspect their bodies. Off unless the organisation sets blocking.enabled to true.
File-upload blocking
Off by defaultOn the named AI platforms only, and only for the platforms the organisation lists, selecting a file for upload can be prevented. The user is shown an on-page notice explaining why. Off unless the organisation sets upload_blocking.enabled to true.
Both gates are strict. Anything other than an explicit boolean true — absent, malformed, or the string "false" — leaves the control off.
Prompt text, downloads, and navigation are never blocked, cancelled or modified. No enforcement path exists for them in the source.
Where the data goes
Telemetry goes to an ingest endpoint the deploying organisation specifies in policy, writing to storage that organisation controls.
Prompt text, where AI evaluation is enabled, is additionally sent to the evaluator endpoint named in that same policy. That endpoint may be operated by Matters AI or by a third party, in either case as a processor acting on the organisation's instruction and under its data-processing agreement. It returns a verdict; it never returns code.
Both destinations must be HTTPS. The extension refuses to attach its credential to a non-HTTPS destination, or to any host outside the administrator's allow-list.
Retention, access and deletion
Governed by the deploying organisation's own policies, as controller.
Employees should direct access and deletion requests to their employer. Matters AI cannot action a request against records it holds no copy of; where it operates the evaluator, prompt text submitted for evaluation is handled under the organisation's data-processing agreement.
Transparency to the people recorded
Deployment is through managed policy on corporate devices, so the extension is installed by the employer rather than chosen by the employee. The deploying organisation is responsible for informing its workforce and for any works council, consultation or notice obligations that apply.
The extension exposes its own state — what is enabled, what is being recorded — so that disclosure can be verified rather than taken on trust.
Changes
Material changes to what is collected are reflected here and disclosed before the version implementing them is distributed.