The one exception to the "no server" principle
Community lists let you fetch shared filter lists from an address you choose yourself. Off by default, never automatic, always triggered by hand.
What Noise Guard actually does
If the feature is actively enabled and a list address entered, Noise Guard can fetch it on request. New suggestions (e.g. additional filter terms) are shown but never adopted automatically, you review and confirm each entry individually or in bulk.
This address is the only network connection Noise Guard makes anywhere in the entire product. Without this feature, Noise Guard never sends anything to any server.
Why any exception to local-first at all
Some filter rules (like new ad domains or current manipulation patterns) change faster than a fixed, bundled list can keep up with. Shared lists solve this without Noise Guard itself becoming a centrally controlled cloud detection system. Control stays entirely with you: you choose the source, you confirm every change.