Where Waterfox Stands on AI and LLMs
I talked about how I don’t believe LLMs have their place in a browser such as Waterfox, due to the inherent privacy risk of sending your browsing data out or having it processed by third parties. Even if you were to use a local LLM, there can still be a privacy risk, unless you develop it yourself from scratch. My position will likely never change for LLM usage in the browser.
- ▪I talked about how I don’t believe LLMs have their place in a browser such as Waterfox, due to the inherent privacy risk of sending your browsing data out or having it processed by third parties.
- ▪Even if you were to use a local LLM, there can still be a privacy risk, unless you develop it yourself from scratch.
- ▪My position will likely never change for LLM usage in the browser.
Hacker News (AI / LLM) files mainly under ai. We currently carry 5,472 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Waterfox |
| Canonical URL | https://www.waterfox.com/blog/where-waterfox-stands-on-ai-llms/ |
| Publication time | Fri, 18 Sep 2026 12:01:25 +0000 |
| Retrieval time | 2026-09-18T12:13:45.178Z |
| Last seen | 2026-09-18T12:13:45.178Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 93TDL5YPncud · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Back in December, I wrote No AI* Here. I talked about how I don’t believe LLMs have their place in a browser such as Waterfox, due to the inherent privacy risk of sending your browsing data out or having it processed by third parties. Even if you were to use a local LLM, there can still be a privacy risk, unless you develop it yourself from scratch. My position will likely never change for LLM usage in the browser. But since then, some users have taken it upon themselves to extrapolate what Waterfox is into more than a privacy focused, customisable browser, and instead treat it as anti-AI in every single aspect.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Waterfox.
Discussion
0 commentsMore from Waterfox
