The publicbeta is liveon Chrome.

Install from Chrome Web Store

Google approved PhishCues Beta. Install the reviewed version directly from the official Chrome Web Store listing.

Store status
Published · version 0.8.0
Store item
jhgobopogccpagfkonnpobommcgkgenp
Open source
Apache-2.0 repository

01 / Manual developer option

GitHub stays
secondary.

Developers who understand unpacked Chrome extensions can inspect the public source and install the deterministic prerelease manually. Most people should use the reviewed Chrome Web Store version above.

Install from GitHubView source and installation notes
Release
0.8.0
Source
d5a2bf800cf1c274e51e06ee8593a8c4db1a4ee6
SHA-256
b61e8d017b203d7763deaafca747739434bf8447265f224b5a08a05240ee7aa5 checksum file
  1. 01

    Download and unzip

    Download the public beta ZIP from GitHub Releases, verify it if you wish, then unzip it into a folder you will keep.

  2. 02

    Open Chrome Extensions

    Type chrome://extensions into Chrome's address bar.

  3. 03

    Turn on Developer mode

    Use the Developer mode switch at the top-right of the Extensions screen.

  4. 04

    Load the extension

    Choose Load unpacked, then select the unzipped PhishCues folder.

  5. 05

    Pin PhishCues

    Open Chrome's Extensions menu and pin PhishCues so the analysis is easy to reach.

02 / This build

Local first. Sharing is separate.

Trusted and Suspicious remain local Chrome decisions and send nothing by themselves. After Suspicious, a separate confirmation can share only the exact From address, bounded displayed name, Suspicious decision, one fixed reason, and policy version. Choosing No sends nothing. A second default-No choice can include only the exact link-free two-sentence preview shown before consent, limited to 220 characters. PhishCues never uploads the full email, subject, headers, recipients, attachments, images, HTML, raw links, Gmail marks, scores, message identifiers, browsing activity, or past local choices.