2026-09-16

“Nothing leaves the machine” is the marketing line because enhancement does not. The honest version is EULA §7.

The app processes video locally. It may still talk to the internet to check for and download updates, to activate or release a licence key when you ask, to fetch NVIDIA and PyTorch wheels for the GPU add-on pack when you request it, to download model weights you request, and to load the public model index when you open Model Hub. It sends no usage analytics, no crash reports, and no information about your files to FrameLathe.

That is a short allowlist, not “offline forever.” Activation sends the key and a fingerprint derived at that moment — not stored as hardware inventory, not sent at launch or at Start. Checking for updates sends the stored licence document; after activation that document includes the fingerprint hash. The app does not phone home to run.

The website is a different program. Waitlist mail and an optional docs assistant run on Cloudflare. They still must not see footage. If you escalate from the chat widget, you send text to the team by email — not into a third-party ticketing cloud.

Update, 0.1.20: you can now connect an AI app such as Claude Code to FrameLathe yourself (off unless you turn it on). FrameLathe still sends nothing. What its tools return to that app (file names, clip details, progress, and any preview frame you ask for) goes to that app’s provider under its terms. See AI apps.

If a future build grew crash telemetry, that would be a product change and an EULA change. Today’s contract is the list above. Docs, Privacy, EULA.