Privacy and telemetry
The vendor control-plane link should stay explicit, coarse, and optional.
This page explains the small amount of data Move Big Rocks collects when a self-hosted instance is explicitly registered with the Move Big Rocks fleet control plane.
Registration data
What registration collects
When an operator runs the explicit registration workflow, Move Big Rocks collects only the registration data needed to identify and contact the instance operator.
- operator email address
- instance name
- instance ID
- use case
- registration source
- platform version
Heartbeat data
What the weekly heartbeat collects
When heartbeat is enabled, the host sends a coarse weekly snapshot for adoption and support visibility.
- instance ID
- platform version
- installed extension slugs and versions
- workspace count
- a coarse 30-day activity bucket such as `0`, `1-10`, `11-100`, or `100+`
What is excluded
What it must not collect
The intended fleet-registration path must not collect operational customer content.
- case content
- conversation content
- end-user identities
- customer records
- uploaded attachments
Control and purpose
Why it exists and how operators control it
The intended purposes are support for registered operators, understanding adoption and extension usage, managing grandfathering commitments, and planning future commercial transitions and entitlements. Registration stays manual, the heartbeat can be disabled in `mbr.instance.yaml`, and the host keeps running even if the callback is disabled or unreachable.
References
Canonical next surfaces.
Each link goes to the next authoritative page, reference, or support surface.
Move Big Rocks
Let agents inspect the CLI-first surface. Let humans decide trust, rollout, and boundaries.
Start from /agents, use
/docs/cli as the official product
tour, inspect /resources for
source and proof, and review /security
before making deployment or data-handling decisions.