NODUS HN Radar browser extension · Last updated: July 2026 · v0.16.15
NODUS HN Radar is a fully local-first browser extension. It enhances reading experience on news.ycombinator.com and surfaces rising posts via the public Hacker News API. There is no server, no account, no login, no cloud sync, and no telemetry.
This is a sibling product to the main NODUS extension (AI conversation capture) and to NODUS YT Radar. Each has its own separate privacy policy:
HN Radar connects to three endpoints — two belonging to Hacker News itself, and one small NODUS server used only for a footer promotion:
The site you are reading. The content script enhances pages you load yourself — no proactive fetching.
Hacker News's public Firebase API. Used to fetch trending lists (Top / Show / Ask / Best) and individual item details for the Radar dashboard.
Powers a rotating banner in the extension's footer that cross-promotes other NODUS extensions (e.g. PH Radar). The extension sends only an opaque promotion ID when a banner is shown or clicked, used solely to count aggregate impressions/clicks. No personal data, browsing history, or Hacker News content is ever sent to this server.
All of the following is stored in chrome.storage.local and never sent anywhere unless described in Section 3.
Uninstalling the extension automatically clears all of the above. There is no user account, no email collection, and no way for NODUS to identify you from any of this data.
The extension only fetches from three domains, all declared in host_permissions and visible to your browser before install.
The content script injects CSS and small DOM enhancements (pin buttons, type badges, translation buttons) on pages you load yourself. The extension does not proactively fetch HN pages in the background.
Data sent to HN by the extension: none beyond what your browser already sends when you load the site.
Returns the array of currently trending post IDs. Same source the official HN front page uses.
Data sent: nothing identifying — just the request.
Same as above for the Best, Show HN and Ask HN tabs of the Radar dashboard.
Fetches public details for each post or comment shown in the Radar or in a hover preview.
Data sent: the post ID. No identifier of you.
Hacker News and Y Combinator may log these requests according to their own policies. The extension itself adds no headers, cookies, or auth.
Fetches the pool of active NODUS ecosystem promotions to show in the extension's footer (e.g. an ad for PH Radar). Refreshed at most every 10 minutes, cached locally in between.
Data sent: nothing identifying — just the request. No post IDs, browsing data, or HN content.
Sent when a footer promotion is shown or clicked, purely to count aggregate impressions/clicks for that promotion.
Data sent: a single opaque promotion ID (e.g. cross-hn-to-ph). No user identifier, IP-based profile, or personal data of any kind is attached or stored against you.
Translations happen entirely on your device. HN Radar uses Chrome's built-in Translator API (Chrome 138+), which downloads a small language model locally on first use and translates text without sending it to any server.
This means:
If your browser does not support the Translator API (Firefox or older Chrome), the translation features simply do nothing — there is no fallback to any cloud translation service.
HN Radar is compliant with the Brazilian LGPD, the EU GDPR, and compatible with CCPA. Since all data is local and the extension does no profiling or cross-site tracking, most rights are exercised directly through your browser.
chrome://extensions → HN Radar → Inspect views → Application → Storagechrome.storage.local; you can export it from DevToolsReading the public HN site and the public HN Firebase API is processed under legitimate interest (delivering the reading-layer feature you opted into by installing the extension). No personally identifying data is processed at all.
For privacy questions or feature requests:
This policy may be updated when new features are added. Material changes will be noted in the extension's release notes on the Chrome Web Store and Firefox AMO. Continued use after a policy change constitutes acceptance of the updated policy.