Skip to main content
Roomote can share anonymous telemetry with the Roomote team to help improve the product. This is on by default, controlled entirely by deployment admins, and designed so that Roomote-generated identifiers and the default payload cannot identify your company, users, code, or repositories.

​
What gets sent

When anonymous telemetry is enabled, your deployment sends:
  • Usage events — page views (as route patterns like /task/[taskId], never actual URLs or IDs) and product events such as tasks being created or settling as completed, failed, or canceled, plus setup progress such as reaching authenticated setup and configuring or connecting communications, source-control, inference, and sandbox providers. Setup events include only the provider type and, where Roomote can determine it from deployment state, whether it was configured before the wizard. Other events include non-identifying facts like the harness, model, source surface, and sandbox provider used. Session events include bounded outcome and retry counts; setup and response phase durations; aggregate model-request and token-usage counts; prompt-size, context-size, environment, integration, and active-task counts; and whether a turn is the session’s first human message. They do not include conversation or message identifiers, prompt or reply text, or tool content.
  • A daily instance report — aggregate deployment metadata and usage: setup timestamps; counts of users, environments, and connected repositories; task, model, token, and cost totals for the past day; session counts grouped by source surface, source trigger, and owner kind; session-attributed token and cost totals for the past day; pull-request statistics for the past week; configured provider types; and enabled built-in integrations.
What is never sent: names, emails, repository names, task contents, prompts, code, access tokens, or credentials.

​
How it is identified

Activity is identified by two anonymous IDs:
  • an instance ID for the deployment as a whole
  • a user analytics ID for each user
By default, both are short random strings created locally. They are not derived from your domain, company, email addresses, or any other real-world identifier, and they cannot be edited or read through the app. If you override R_INSTANCE_ID, use a random, non-identifying value. Roomote sends the configured value with telemetry and version checks.

​
Turning it off

Anonymous telemetry is opt-out:
  • during setup, the final step includes an Anonymous analytics switch
  • afterwards, admins can change it any time in Settings > Deployment
The setting applies to everyone in the deployment. When disabled, no analytics code runs in the browser and no usage events or daily reports leave your servers.

​
Roomote Cloud Specifics

Roomote Cloud deployments always keep Roomote anonymous analytics enabled and do not show this switch, as described in our privacy policy. Cookie consent controls only optional support and product-experience services such as Intercom and PostHog.

​
Version checks

Separately from analytics, your deployment checks once a day whether a newer Roomote release is available. This check is not optional and carries only the anonymous instance ID and your running version — no usage data.

​
Local development

Deployments running in development or preview mode send nothing by default. Telemetry runs there only when ROOMOTE_FORCE_TELEMETRY=true and a Ping endpoint is explicitly configured.