Notifications Pro is designed with a strict zero-persistence notification-content model:
- Notification title/body content is never written to disk — not to files, databases, registry, cache, logs, or telemetry.
- Notification text exists only in RAM for the duration it is displayed on screen.
- Overflow notifications store only a count, never content.
- User-configured app-name metadata such as muted apps, spoken-app preferences, and per-app icon/sound/background overrides can be saved in settings or profiles.
- The only persistent data is user settings (
%AppData%\NotificationsPro\settings.json), saved profiles, custom themes, and optional user-provided icon/sound/background assets.
| Version | Supported |
|---|---|
| Latest | Yes |
If you discover a security vulnerability in Notifications Pro, please report it responsibly:
- Do not open a public issue for security vulnerabilities.
- Email the maintainer directly or use GitHub's private vulnerability reporting feature on this repository.
- Include a clear description of the vulnerability and steps to reproduce.
- Allow reasonable time for a fix before public disclosure.
- No external dependencies — the app uses only .NET 8 framework libraries (WPF, WinForms, WinRT). No third-party NuGet packages in the main application.
- No network access — the app makes no outbound connections. No telemetry, analytics, or update checks.
- No elevated privileges — runs as a standard user process. Registry access is limited to read-only Windows metadata queries under current-user/local-machine hives for sound and speech discovery, and notification content is never written to the registry.
- Input validation — startup settings, profile/import payloads, and custom theme JSON are size-limited to 1 MB where Notifications Pro loads them, numeric values are clamped to valid ranges, and custom asset paths are validated to stay within the designated AppData directory.
- Regex safety — keyword matching uses timeouts to prevent ReDoS.
Notifications Pro reads all Windows toast notifications via the WinRT UserNotificationListener API (or UI Automation fallback). This means:
- The app processes notification text from all applications on the system.
- Windows does not automatically give other applications this process's memory, but sufficiently privileged local software, debuggers, or malware that can inspect the running process could still read notification text currently held in RAM.
- Notifications Pro does not claim special process-memory isolation beyond the normal Windows process boundary; its main guardrails are minimizing retention and avoiding persistence, transmission, and logging of notification content.
- An attacker who compromises this process could read notification text currently displayed in the overlay.
- The app does not store, transmit, or log notification content, limiting the window of exposure to what is currently visible on screen.