Find the noise.
Flip the switch.
Explore Windows senders and individual browser profiles. Suppress an unwanted source, or restore a permission when you need it again.
Try the switchesYour attention isn’t up for grabs.
Take back your Windows and browser notifications.
Development build · Windows · No account needed
Try a switch. Enjoy a little quiet.
Illustrative sources. In the app, close Chrome before editing its permissions.
Select a sample notification to inspect it.
Urgent account-verification language was flagged for review. This is a text-screening prompt, not a malware verdict.
Windows sender: Chrome. Website and browser profile: unknown.
Illustrative message. Available records vary; logs may be incomplete.
See what happens when a saved permission changes.
daily-deals.example was last observed off.
Demo only. Guard observes changes while open; it doesn’t block them automatically.
That website you clicked once. That app with too much to say. Bring their saved notification permissions into one place, and choose what deserves your attention.
Explore Windows senders and individual browser profiles. Suppress an unwanted source, or restore a permission when you need it again.
Try the switchesRead available notification titles, messages, and arrival times. Local history helps you look back without sending your messages to the cloud.
Inspect a notificationPrivacy isn’t a setting you have to find.
It’s how Guard works.
No. Guard reads saved Windows and supported browser permissions on a best-effort basis. Internal formats, organization policies, and custom profiles can affect coverage. It shows unavailable integrations rather than promising complete control.
Guard can edit saved explicit website notification permissions in discovered Chrome, Edge, and Brave profiles. Keep the browser fully closed while making changes. Firefox permissions are read-only; change them in Firefox Settings. Browser defaults and future sites are outside these controls.
Recording is on by default. While Guard is open, it saves available notification titles and bodies locally every ten seconds, retaining history for thirty days. You can turn recording off. Clearing saved history also disables recording; it doesn’t clear Windows Notification Center. Available records may be incomplete.
No. It uses local rules to screen available English-language notification text and explain suspicious wording. False positives and missed threats are possible. It doesn’t establish whether a link or message is safe, and a browser sender doesn’t identify a particular website.
No. Permission Watch compares successful observations while Guard is open, normally every four hours and when you refresh or scan. It can flag a previously observed off permission becoming on; it cannot identify who changed it or give the exact time. Changes made through Guard are recognized as authorized.
The current standalone Windows development executable, not a Microsoft Store release or an installer. It uses WebView2 and has no tray service or startup registration. This is an early build; Windows may show a security prompt for an unrecognized app.
Less “look at this.” More getting on with it.
Download for WindowsDevelopment build · Runs locally · No account