# Privacy Front End A privacy front end is an alternative interface or routing layer that lets a user reach information or device functionality while reducing reliance on the upstream platform's native client, tracking, or account model. ## Notebook cluster PDF page 41 of [[Scanned_20260730-1913]] groups [[Gadgetbridge]], [[UntrackMe]], [[Nitter]], [[Invidious]], [[Bibliogram]], and [[OpenStreetMap]]. Page 88 adds [[Tor]], [[Brave Browser]], and [[Startpage]]. Together they express a coherent substitution strategy: **upstream platform or device → user-selected intermediary → content or function** The intermediary can reduce some telemetry or account dependence, but it does not automatically provide anonymity, correctness, availability, or protection from all upstream and network observation. ## Archive significance This is one instance of [[Control-Plane Continuity]]: the user tries to retain a service's useful function while changing who controls the interface and what metadata is exposed. ## Boundaries Listing or researching a privacy tool does not prove installation or use. Privacy front ends also inherit operational and trust risks from their operators, instances, dependencies, and routing paths. ## Source - [[Scanned_20260730-1913]], PDF pages 41–42 and 88.