© 2025 Loopbox

Back to Settings

License

Notices overview

Notices overview.

Loopbox ships multiple products with different distribution models. This page reflects the current 2026-04-16 release-candidate disclosure set. Web notices are a discovery layer, and desktop-installed components also keep offline notice files in the local installation directory.

Release
Release candidate 2026-04-16
Last updated
2026-04-16

Product coverage

Loopbox Web UI

Browser-delivered frontend bundle and its production dependencies.

Distribution: Hosted by Loopbox
Notice location: Published in this page and tracked from the production dependency inventory during release preparation.

Production dependency inventory is generated from the shipped frontend bundle.

User-facing disclosure is grouped at the product level instead of exposing one raw package dump.

Loopbox API

Server runtime dependencies used by the backend service operated by Loopbox.

Distribution: Hosted by Loopbox
Notice location: Managed from the backend runtime notice inventory for each release.

Runtime notices are generated from the deployed server classpath.

This section covers server-side dependencies that users interact with through the service.

Loopbox Worker

Local rendering service installed on the user's Windows machine.

Distribution: Installed locally
Notice location: Installed with the setup app under the local licenses directory.

Worker notices remain available offline after installation.

Current worker candidate version is 0.1.2 and the installer copies the approved worker notice files into the local licenses directory.

Loopbox Worker Installer

Windows installer that bundles the worker runtime, JRE, and service wrapper.

Distribution: Distributed by Loopbox
Notice location: Installed with the setup app under the local licenses directory.

Current installer candidate version is 0.1.2 and the candidate artifact checksum is tracked in the installer release manifest draft.

The installed package includes offline copies of the installer notice file, worker notice file, OpenH264 binary license, FFmpeg notices, and WinSW license text.

Special notices

FFmpeg

The current worker installer candidate requests a Windows x64 FFmpeg runtime for local rendering tasks and keeps offline FFmpeg notices in the installed licenses directory.

Distribution note: Downloaded runtime

The current release candidate expects the Windows runtime package version used by worker version 0.1.2. Final release approval still requires matching source-bundle publication for the exact binary.

The worker installer must install local FFmpeg notice files for offline review after setup finishes.

Release checks must verify that GPL and nonfree FFmpeg options are not enabled in the shipped build.

OpenH264

OpenH264 version 2.6.0 is downloaded directly from Cisco infrastructure when enabled for the worker.

Distribution note: Cisco-hosted binary

Loopbox does not bundle, mirror, or modify the OpenH264 binary payload.

The Cisco binary license is shown during setup flow and installed locally for offline review.

Release checks must confirm that production downloads resolve to Cisco-hosted infrastructure.

Bundled JRE

The current installer candidate bundles Eclipse Temurin 21.0.9+10 for the local worker service.

Distribution note: Bundled runtime

Each release pins the exact JRE vendor and version used by the installer.

Vendor-provided legal files remain installed with the local JRE.

Redistribution terms must be reviewed again before any vendor change or Java image change.

Hosted service policies

Hosted service policies are under /legal.