Skip to Content
DocumentationReferenceThird-party services

Third-Party Services

Telemetry

No usage analytics are collected β€” no page views, no feature metrics, no profiling of how you use the software.

Crash reports are sent by default. When something throws an error, a report goes to SentryΒ  after passing through a scrubber that removes credentials, your username and email, your machine’s hostname, home-directory paths, URL query strings, and request bodies. Crash reporting is opt-out: each first-party app has a Share crash reports switch, Companion Hub has Allow anonymous error monitoring in Settings β†’ General, and CI_TELEMETRY=off or CI_LOCAL_ONLY=true disables it for a self-hosted app or Hub.

DataCollectedNotes
Usage analytics, page views, feature metrics–Not collected
Session replayβœ“Hub's dashboard can record masked replays around errors, only after consent; the same switches stop it
Your memories, files, and messages–Stay on your server; the scrubber keeps them out of error reports too
Crash reportsβœ“On by default, opt-out; errors only, scrubbed before sending
What leaves your appliance, and what never does.

See Crash Reporting for exactly what is sent, what is stripped, and the limits of the scrubber. Hub honors the Settings switch: turning it off stops the next report without a restart. Details are under Companion Hub on that page.

What We Don’t Do

  • No user tracking β€” No analytics, no usage metrics, no advertising or profiling
  • No data collection β€” Your memories, files and messages stay on your server. They are never uploaded, and the crash-report scrubber exists to keep them out of error reports too
  • No hidden phone-home β€” Apart from the connections listed below, Companion Hub runs on your machine. Once installed and paired, the connections that always happen are the hourly check-in with your CI Account and the catalog and image traffic you trigger yourself. Crash reports are the only optional one you must switch off

External Connections

Companion Hub may make outbound connections for:

ServicePurposeWhenDocumented in
Docker HubΒ  / GitHub Container RegistryΒ Pulling app images and the Hub stack imageInstalling or updating an app, or updating HubDocker and Companion Hub
CI Cloud (hub.ci.computer)The app catalog, the alternatives list, each app’s definition at install time, the list of Hub releases, and device pairingBrowsing or refreshing the app store, installing an app, or pairingApp store, Custom app stores
CI Cloud check-inConfirms your device key is still valid and records when the Hub was last seen. Portal treats a device as stale after three hours without oneAbout 10 seconds after Hub starts, then every hour, once the Hub is pairedDevice pairing
dl.ci.computerDesktop app update checks and installer downloadsWhen the desktop app or Settings β†’ System checks for updatesUpdating Companion Hub
Let’s EncryptΒ SSL certificate generationOnly if you expose apps on a public domainExpose your apps
CloudflareΒ Managed tunnel for the Cloudflare GatewayOnly if you use the Cloudflare Gateway via your CI AccountCloudflare Gateway
TailscaleΒ Sign-in and coordination for the private VPN sidecar. If you add an OAuth client, Hub also calls Tailscale’s API to list your tailnetOnly if you turn on Private VPNEnvironment variables
OpenAI, Anthropic, Google, GitHub CopilotInference requests, sent straight from your Hub to the providerOnly for a cloud provider you configure in Settings β†’ AIAI and inference
SentryΒ Crash reportsUnless you opt out of crash reportingCrash Reporting

Every connection is outbound from the Hub. Four of these happen only when you turn the feature on, and one stops when you turn it off:

Last updated on