Chrome, load unpacked
Download the zip, unzip it, open chrome://extensions, enable Developer mode, and choose Load unpacked. Pair it from the Devices page with a one-time activation code.
BROWSER EXTENSION
Precyz for your browser.
Download the Chrome zip, unzip it, enable Developer mode, and load unpacked. This is not a Chrome Web Store listing. Firefox loads as a temporary add-on from about:debugging. Compare the SHA-256 checksum on the verify page. The extension observes browser connection metadata through read-only request events and reduces site names to their registrable domain on the device.
Context
The situation
Download the Chrome zip, unzip it, enable Developer mode, and load unpacked. This is not a Chrome Web Store listing. Firefox loads as a temporary add-on from about:debugging. Compare the SHA-256 checksum on the verify page. The extension observes browser connection metadata through read-only request events and reduces site names to their registrable domain on the device.
Developer-preview clients are unsigned zips and binaries you load yourself. They are not Chrome Web Store, EV-signed, or notarized listings. Compare the SHA-256 checksum before you run them. Signed store and desktop builds will use the same download URLs when they exist.
On this page
What you get from this
Firefox, load temporary
Open about:debugging, choose This Firefox, then Load Temporary Add-on and select the Firefox zip. Paste the activation code in the Precyz popup.
Verify the zip
Compare the SHA-256 checksum on the verify page. This preview is not a Chrome Web Store package and is not EV-signed.
Desktop and signed store builds
Windows, macOS, and store listings are not published as signed installers yet. A Linux developer-preview binary is on the Linux download page. Join the waitlist for signed artefacts; the URL structure stays.
Collection boundary
The boundary
We observe here
Byte and packet counts, protocol, an encryption indicator, destination country, network operator, registrable domain, the app or browser that opened the connection, timestamps, and direction.
We never collect here
Communication content, URLs, paths, query strings, DNS names beyond the registrable domain, headers, cookies, tokens, files, screenshots, form data, keystrokes, usernames, email addresses, hardware serial numbers, or precise location.
Coverage is not complete. Some traffic paths are not observable from the interfaces we use, and geolocation is advisory rather than authoritative.
Availability across plans
Personal
Included
Pro
Included
Team
Included
Enterprise
Included