Skip to main content
Roomote keeps the data boundaries for a deployment explicit. Self-hosted deployments send no analytics or usage telemetry to the Roomote team. Managed deployments on Roomote Cloud send the anonymous telemetry described below and follow their own privacy policy. This page covers the telemetry payload managed deployments send, its identifiers, and the version-availability check. It does not replace the privacy terms of the upstream inference, sandbox, communications, or integration providers you connect.

Privacy boundaries

  • session and task content stays in the deployment and the providers that the work explicitly uses; it is not included in anonymous telemetry
  • provider credentials, access tokens, prompts, replies, code, repository names, task contents, and user names are never sent in the default telemetry payload
  • cost analytics stays inside the deployment for members to review; it is separate from anonymous telemetry
  • connected providers may receive the data required to perform their own service, such as model context sent to an inference provider or a message sent to a communications provider

Anonymous telemetry

Managed deployments on Roomote Cloud share anonymous telemetry with the Roomote team to help improve the product. It is designed so that Roomote-generated identifiers and the payload cannot identify your company, users, code, or repositories. Self-hosted deployments never send it.

What gets sent

A managed 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. Model fallback events include only the previous and replacement provider and model names. 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 on a managed deployment, use a random, non-identifying value. Roomote sends the configured value with telemetry.

Managed deployment controls

Managed deployments always send anonymous telemetry, as described in our privacy policy. Cookie consent controls only optional support and product-experience services such as Intercom and PostHog.

Version checks

Once a day, every deployment reads the latest published Roomote release from GitHub to power the in-app update notice. The request goes to GitHub’s public API and carries no instance ID, version, or usage data.

Local development

Deployments running in development or preview mode send nothing and skip the version check by default. They run only when ROOMOTE_FORCE_TELEMETRY=true and a Ping endpoint is explicitly configured.