Privacy policy

EngGauge AI · last updated 10 August 2026

EngGauge has no server. There is no account, no telemetry, no analytics, and no component of this product that we operate and you connect to. Everything below follows from that.

Who processes your data

Nobody, on our side. The extension runs entirely inside your browser. It calls your code host, optionally Atlassian, and optionally the AI model provider you configured — each directly, with credentials you supply, from your machine. We do not receive, store, see, or have any means of obtaining any of it.

This is a structural property, not a promise about our intentions: there is no backend to send data to.

What the extension stores, and where

Everything lives in chrome.storage.local — this Chrome profile, on this machine.

What	Why
API tokens and keys for your code host, Atlassian and model provider	To make the requests you asked for, on your behalf
Your settings: hosts, analysis rules, competency models	So you do not re-enter them every run
Generated reports, and any notes or exclusions you add to them	So you can reopen and compare them
A short-lived cache of fetched merge requests and comments	So a re-run does not repeat 150 API calls. Expires after a few hours; clearable at any time

Storage is deliberately local and never chrome.storage.sync. Sync would replicate your API tokens to Google’s servers, which would defeat the point.

Local storage is not encrypted at rest. Anyone with access to your unlocked machine, or to this Chrome profile’s directory, can read the tokens stored here. We say this plainly rather than implying an encryption we do not have. Use minimum-scope, short-expiry, read-only tokens.

What leaves your machine, and where it goes

To your code host (GitLab or GitHub): Authenticated API requests for the engineer’s merged work, review comments and diffs. Same data your own account can already see.
To Atlassian — only if you connect it: Requests for Confluence pages and Jira issues attributed to the assessed engineer.
To your AI model provider — only if you set an API key: The assembled prompt. This does contain your source code and your colleagues’ review comments: diff excerpts from the analysed requests, reviewer comments, request titles and descriptions. It is sent directly from your browser to OpenAI, Anthropic or Google, on your own key, under whatever data-handling terms you have with them. We are not a party to that request and cannot see it. If your organisation restricts where source code may be sent, this is the item to check.
To us: Nothing. Ever. There is no endpoint.

On-device mode

With no API key configured, the analysis runs on Chrome’s built-in on-device model. In that mode no code, comment or prompt leaves your machine at all — the only network requests are to your code host to fetch the data.

Data about other people

This product assesses a named individual using their work and their colleagues’ review comments. That data is about people who have not installed this extension and have not agreed to anything.

You are responsible for having a legitimate basis to process it — an employment or management relationship, your organisation’s policies, and whatever your local law requires. Under GDPR and similar regimes, the person being assessed generally retains rights over data about them, including the right to see it. The export exists partly for that reason: an assessment you cannot show the subject is one you should not be making.

Retention and deletion

Reports stay until you delete them — individually, from the Recent assessments list, or all at once.
The fetch cache expires on its own and can be cleared in Settings.
Settings → Analysis & privacy → Delete all credentials and reports removes everything the extension has stored.
Uninstalling the extension deletes all of it with it.

Data already sent to your code host, Atlassian or your model provider is governed by their retention policies, not ours. Deleting a report here does not reach into their logs.

What we do not do

No analytics, telemetry, crash reporting or usage tracking of any kind.
No selling or transferring data — there is none to sell.
No advertising, profiling, or use of your data to train anything.
No remote code: everything that executes ships in the extension package.

Permissions, and why each exists

Permission	Reason
`storage`	The local settings and reports described above. There is no server, so this is the only place they can live.
Host access to gitlab.com and api.github.com	Reading the review history the assessment is built from.
Host access to `*.atlassian.net`	Optional Confluence and Jira signal.
Host access to the model provider APIs	Sending the prompt on your own key.
Access to other hosts, requested at runtime	Only when you enter a self-hosted GitLab, GitHub Enterprise or Atlassian URL. Requested per host, at the moment you enter it, and never for anyone using only the cloud services above.

The tabs permission is deliberately not requested. It would prompt for browsing-history access to power a convenience feature, which is not a trade worth making.

Changes

Material changes will be reflected here and in the extension’s release notes, with the date at the top updated. Since nothing is collected, a change of practice would mean a change of architecture — which would be visible in the source.

Contact

Questions about this policy, or about what the extension does with a particular piece of data: CONTACT_EMAIL_PLACEHOLDER.