Privacy

Last updated: 2026-10-04

This page is about the Voro documentation site and the Voro beta software as it ships today. It is not a claim that Voro never connects to a network, never uploads anything, or never will.

This documentation site

These pages are static. This repository does not add analytics, accounts, cookies for tracking, or a sign-in.

The site is hosted by a third-party static host. That host may keep ordinary web-server logs (such as IP address, user agent and the pages requested) under its own terms.

Search on this site runs in the browser against a local index. It does not send your query to Dotsimulate.

The Voro beta

The Windows installer registers the package folder on this machine so hosts can find it. That registration is local.

Voro runs on a lease tied to your Voro code. When you sign in, and when the lease renews (about once a day while Voro runs and the computer is online), Voro sends Dotsimulate’s licensing server your Voro code (at sign-in only), a one-way hash of this computer’s Windows machine id, the computer’s name and the Voro build. For each of your computers the server keeps that hash, the name, the build, when it was last seen and the IP address it was seen from, so you can release a computer and a shared code can be noticed. Voro sends nothing about your projects. The lease is checked on the computer before each graph runs; that check does not contact the server.

Voro can use the local network when you ask it to. Rig Serve can put a surface on a phone or tablet on the same network. That is your session, on your machines.

Optional modules, models and services can reach other computers:

• GPU-dependent image and geometry modules need an NVIDIA driver stack on the machine.
• Kernel FX and Script FX can download a pinned Python runtime when you run the bootstrap script in the package.
• Stream Diffusion wraps an existing StreamDiffusionTD install and follows that product’s terms.
• Model operators may load bundled weights or optional downloads. Some optional weights have their own restrictions; see Third-party notices.
• Third-party APIs and hosts you connect yourself (including TouchDesigner) keep their own privacy policies.

The separately supplied desktop application, the Lab SDK and any future hosted services, if you receive them, will say what they collect in their own start instructions. A runtime package alone does not include those applications.

Email

If you write to support@dotsimulate.com or licensing@dotsimulate.com, we use that message to answer you. Include the release name from release.manifest.json when the question is about a specific build.

Contact

Privacy and licensing: licensing@dotsimulate.com.