# Privacy And Telemetry Notice

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.

## Summary

- Registration is explicit: A self-hosted instance is registered through a manual workflow in the private instance repo.
- Heartbeat is optional: The weekly heartbeat can be disabled in `mbr.instance.yaml`.
- Core keeps running: Disabling or blocking the callback does not stop the core platform from running.
- Coarse signals only: The heartbeat is intended to carry adoption and support signals, not customer content.
  Proof:
- Definition: docs/CUSTOMER_INSTANCE_SETUP.md (https://github.com/MoveBigRocks/platform/blob/main/docs/CUSTOMER_INSTANCE_SETUP.md) — Defines the explicit self-host fleet-registration and disclosed heartbeat model.
- Contract: docs/AGENT_CLI.md (https://github.com/MoveBigRocks/platform/blob/main/docs/AGENT_CLI.md) — Documents `mbr fleet register` as the explicit registration command.
- Implementation: instance-template/mbr.instance.yaml (https://github.com/MoveBigRocks/instance-template/blob/main/mbr.instance.yaml) — Shows the `spec.fleet` block carried by the private instance repo.
- Implementation: instance-template/deploy/README.md (https://github.com/MoveBigRocks/instance-template/blob/main/deploy/README.md) — Documents the host-owned registration workflow, fleet config files, and weekly timer.


## 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

## 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 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

## 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.

- Contact Move Big Rocks: mailto:support@movebigrocks.com

## Related

- Self-host guide: /docs/self-host
- Self-host overview: /self-host
- Security: /security
- Resources: /resources