Privacy
Last updated 2026-08-11
Easy for Hacker News has no server. There is nothing to send your data to, so it doesn't collect any: no analytics, no tracking, no ads, no account. This page exists only because the Chrome Web Store and Firefox Add-ons require a privacy policy from every extension. It covers everything the extension can see and everything it stores.
What it can see
Easy runs only on
news.ycombinator.com. It reads the HTML that page already
sent your browser and replaces it with its own rendering. It never
talks to any other site, and no page you read is sent anywhere else.
Hacker News sees only what your browser would have sent it without the
extension.
Signing in, voting, and replying
Easy doesn't have its own login. When you sign in, you're using Hacker News's own form, and Hacker News sets the session cookie the same way it always has. Easy never sees your password. Voting and replying work by submitting Hacker News's own links and forms with that session, the same as the native page. It only reads the session Hacker News reports back, and never creates or stores one.
What's stored on your device
Easy uses the browser's built-in
storage permission to remember two things:
- Your display settings (theme, font, size, density), so they carry across your open tabs.
- Which threads you've opened, so it can mark comments posted since your last visit. You can turn this off in Settings, under Mark comments added since your last visit. That stops both the marks and the recording; anything already stored stays on your device until you remove the extension.
If your browser syncs extension storage across your own devices (Chrome and Firefox both offer this), that sync belongs to your browser, not to Easy. It is the same mechanism any extension's settings use, and nothing here leaves your browser through it.
Third parties
None. Easy makes no network requests of its own. Every request it makes is one you could make by clicking around Hacker News yourself.
Source
Easy is MIT-licensed. The source that ships is in the GitHub repository, so you can check every claim on this page against it.
Contact
Have a question? Open an issue on GitHub, or message @harrispjose on X.