Third-Party Services
Telemetry
No usage analytics are collected — no page views, no feature metrics, no session recording, 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, and CI_TELEMETRY=off or CI_LOCAL_ONLY=true disables it for a
self-hosted app.
See Crash Reporting for exactly what is sent, what is stripped, and the limits of the scrubber.
Note that the allowErrorMonitoring setting on Hub’s Settings page does not currently
control Hub’s own crash reporting — Hub reports whenever it is configured with a reporting
address. This is documented in full on the Crash Reporting 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 mandatory phone-home — Companion Hub runs fully offline after installation, apart from pulling Docker images and (unless you turn it off) sending crash reports
External Connections
Companion Hub may make outbound connections for:
- Docker Hub / GitHub Container Registry — Pulling app images
- App Store Repository — Fetching the app catalogue
- Let’s Encrypt — SSL certificate generation (if exposing apps)
- Cloudflare — If using the Cloudflare Gateway via your CI Account
- Sentry — Only if you opt in to crash reporting