AI 产品解读A local browser privacy settings manager that provides a unified UI to control Chrome privacy settings, manage cookies, monitor network requests, and automatically clear browsing data on browser startup
Chrome's privacy settings are scattered across different menus and difficult to manage. This extension centralizes privacy controls, provides cookie inspection/management, network traffic visibility, and automated data cleanup — giving users transparency and control over their browser privacy.
User clicks extension icon → popup opens with three tabs (Main, Cookies, Network). Main tab: toggle privacy settings on/off and configure which browsing data types to auto-clear on startup. Cookies tab: browse cookies by domain, search, edit, delete, whitelist. Network tab: view captured HTTP request/response headers with download and clear options. The extension operates entirely locally with no external services.
Toggle Chrome privacy settings (third-party cookies, hyperlink auditing, referrer headers, autofill, safe browsing, search suggestions, translation, network prediction, WebRTC IP handling, etc.)Automatically clear selected browsing data types on browser startup (cache, cookies, history, downloads, passwords, localStorage, IndexedDB, etc.)Cookie management — view, search, edit, delete, and whitelist cookies per domainNetwork request monitoring — log and inspect HTTP send/receive headers with download capabilityUser-agent header blocking via declarativeNetRequest rulesQuick open current page in incognito mode
- 目标用户
- Privacy-conscious users who want granular control over Chrome privacy settings / Users who want automated browser data cleanup on startup / Developers and security researchers who want to monitor network traffic and cookies
- The extension is webpack-bundled so some JS is minified; however the core logic in back.js (service worker) is readable and clearly shows only local Chrome API usage with no external service calls.
- No explicit 'login' or 'paid' UI or code was found, but the bundle could theoretically hide such features in obfuscated portions — though there is no evidence of this given the small codebase and transparent GPL licensing.
