Skip to main content

Third-party notices

ScreenGuardian™ is the proprietary work of Eric W. The product bundles and links against the third-party components listed below; each is governed by its own license. The same attributions are also bundled inside the desktop app under Help → Third-party notices, so they are available offline.

If you believe a component is missing from this list or that an attribution is incorrect, please contact [email protected].

Desktop app

Qt (PySide6) — GNU Lesser General Public License v3.0

The ScreenGuardian desktop app is built on the Qt framework via the PySide6 Python bindings. Qt is dual-licensed under commercial and LGPLv3 terms; ScreenGuardian uses Qt under LGPLv3.

License text: https://www.gnu.org/licenses/lgpl-3.0.html. Qt source code and instructions for re-linking ScreenGuardian against a modified version of Qt are available at https://www.qt.io/download. PySide6 project page: https://www.qt.io/qt-for-python.

appdirs, keyring, pyobjc — MIT

Platform glue for the desktop app. License texts in each project's repository.

cryptography — Apache 2.0 or BSD-3-Clause

Ed25519 signature verification on the auto-update manifest. License.

Sparkle (macOS) — MIT

sparkle-project.org. Bundled Sparkle source-license headers are preserved inside the framework as shipped.

Other Python packages bundled by PyInstaller

Each transitively included Python package keeps its LICENSE / NOTICE / licenses/ metadata inside the packaged _internal/<package>.dist-info/ directory shipped with the desktop app. Notable transitive dependencies pulled in by MediaPipe include jax, flask, click, pydantic, requests, regex, jsonschema, importlib_metadata, and the opentelemetry family — each under their respective open-source licenses.

Note on OpenTelemetry: it is present in the bundle as a transitive dependency of MediaPipe but is not initialized by ScreenGuardian. No telemetry exporter is started by the app or by its detection code.

Website

PostCSS, Autoprefixer — MIT

Backend

Supabase Edge Functions (Deno runtime)

Account, entitlement, and download functions run on Supabase's Deno runtime. The runtime and platform-provided libraries are governed by the Supabase, Deno, and Postgres license terms. No additional third-party libraries are bundled inside the function code itself.