Privacy and network access
What Loom sends, what stays local, and when development tools use the network.
Data sent to Snack
Loom GUI does not send telemetry, analytics, crash reports, Unity project files, UI source, or bridge data to Snack Software. The package and player runtime do not require a Snack account or contact a Snack licensing service.
Unity-to-UI bridge traffic stays within the running Editor or player. The Editor-only browser debugging connection binds to loopback, and player builds do not expose that debugging connection.
Development-time network access
Tools > Loom > Setup UI Project runs npm install for the starter UI.
Loom’s matching @loomgui/bridge and @loomgui/vite-plugin archives are bundled
with the Unity package, while Solid, Vite, and their third-party dependencies
come from your configured npm registry, cache, or mirror.
Your UI is application code. Network requests made by that code, or by npm packages you choose to add, are controlled by your project and are your responsibility to disclose where applicable.
Website privacy
The Studio license contact form and website infrastructure are covered by the Loom GUI privacy page. You can contact support@snack.onl without using the form.