Usage telemetry

Usage telemetry is a condition of the SimForge account and download terms, which cover SimForge's services and downloads; the runtime's own license is PolyForm Noncommercial 1.0.0. The runtime reports how it is used, tied to the account you signed in with, so we can see which GPUs people use, how many jobs they run and where the local stack breaks. There is no off switch; commercial licences can agree otherwise.

Collected#

• Your account id (from sign-in) and an id for this installation.
• The CLI and runtime versions, the operating system and architecture.
• The GPU model, its memory, the driver version and the GPU count.
• For each job: its kind (simulate, render 2D, schematic or 3D, preview, RL episodes, evaluate), the render profile, the sensor count, frames, wall-clock seconds, GPU-busy seconds, and the outcome (ok, or the error code).
• For reinforcement learning: episodes and environment steps.
• The name of a public map, when one is used.

Never collected#

• Your email, name, username or host name. The account id is enough; your email stays in the account system.
• Your IP address: the server drops it.
• File paths, scenario content or names, environment variables.
• Anything about a private or customer map.

See what is sent#

simforge telemetry show

prints the batches waiting to be sent, exactly as they will be sent. When you are signed out it shows the batches sealing would make, with no account id.

The runtime records each finished job (and, for reinforcement learning, a session's episodes and steps) in ~/.simforge/usage/. The runtime, not the open CLI, sends the records in the background, at most once a day after a job and also after simforge login, maps pull and runtime install. A job never waits on the network, and records that cannot be sent yet stay on the machine until the next attempt. DO_NOT_TRACK does not apply.