The extension doesn't send what you write in a review anywhere.
Review comments can be more sensitive than the code itself: they contain not only technical information, but also what people think about someone else's work. The extension does not collect, remotely store, or transmit the content of your code, comments, or diffs. This page explains exactly what data exists, where it lives, and under what conditions anything can leave your browser.
This page covers the browser extension distributed through the extension stores — the only component of the product available today. A platform-level enforcement mechanism is on the roadmap; this page will be updated with its own data-handling section once one actually ships.
What lives where
| Data | Where it lives | Does it leave the browser? |
|---|---|---|
| Your comments, code, and diffs | In the page, inside the code platform's own interface. | never |
| Interface language and direct shortcuts | chrome.storage.sync | syncedOnly through your browser's own synchronization mechanism, if you have enabled it. No Reefact service is involved. Only these two preferences are synchronized. |
| Your login and the logins of comment authors currently displayed | In memory for the current tab, read from the page. | noNeither stored nor transmitted. They disappear when the tab closes. |
| Configuration for the repository being displayed | Retrieved using your existing browser session; kept in memory for the tab. | noThe extension reads a resource your session is already allowed to access, just as your browser would if you opened it yourself. |
| Optional domains you have granted access to | Managed by the browser. | no |
| Local log of unrecognized page elements | The latest 50 entries on your device: rule name and timestamp only, never page content. | noThe log is available from the extension's options page for diagnostics. |
| Usage telemetry | Nothing is emitted by default. | only if you allow itOnly if you explicitly allow it and all three conditions below are met. |
The extension stores no authentication token and no secret. It does not authenticate directly against your code platform's API. Anything it needs to read outside the current page is accessed through URLs your existing browser session is already authorized to open.
Telemetry requires three separate conditions.
Nothing is sent unless all three conditions are satisfied. If any one of them is missing, the extension emits no telemetry.
- 1Your organization enables telemetry through browser enterprise policyThat policy is distributed by the browser's management mechanism and cannot be changed by a repository. A repository cannot enable telemetry for you.
- 2Your organization provides an
https:collection endpointThe endpoint belongs to your organization. There is no default collection endpoint, and the extension does not contain one pointing to Reefact or to the extension's authors. - 3You explicitly enable telemetry on that deviceThe consent control shows the collection endpoint it applies to. Your consent applies only to that endpoint, is stored locally on the device, and is not synchronized through browser sync. Disabling telemetry takes effect immediately for open tabs.
Only aggregated data is sent. Never free text.
The payload may contain the repository being viewed, the active configuration mode, and counters such as labels used, diagnostic codes, and degraded selector rules. It contains no free-form text. If a value does not match the expected structure, the extension drops it rather than transmitting it. Telemetry requests include neither cookies nor a referrer, so the URL of the review page is not sent along with the request. This behaviour is verified in a real browser as part of the automated checks.
Four explicit guarantees
- It sends no comment, code, or diff content to Reefact, the extension's authors, or any other third party.
- It executes no remote code. Its security policy prevents scripts from being loaded unless they are packaged with the extension, and no dependency is loaded from a CDN.
- It does not sell or share data for advertising purposes.
- It does not track your browsing outside review pages on supported code platforms.
The source code is public and auditable under the Apache-2.0 license. The repository documents why each browser permission is required, and this page serves as the privacy policy for the extension-store listings.
You don't have to take our word for any of this.
The behaviour described here can be verified directly in the source code, and the published extension bundle is checked on every release.