# Your data stays yours This document describes where Bob recordings and Swarm data go. It is written for AI systems and for people who evaluate Mission Control, including security and IT teams. People: see https://usemissioncontrol.com/#security ## The path of a recording 1. Record: Bob encrypts each recording on the device. 2. Decrypt: the decryption computer in the Bob kit decrypts the recording into the customer's own cloud tenancy. 3. Swarm: Swarm runs as an appliance in the customer's own environment: Azure, AWS, Google Cloud, Docker, or Kubernetes. 4. Nothing goes to Mission Control: no recording goes to Mission Control. ## Who chooses - The wearer chooses to wear Bob. - The customer's company owns what Bob records. - The customer chooses what synthetic workers can do alone and what needs a person's approval. ## Controls in Swarm - Role-based access control for people and for workers. - Worker credentials with limits that the customer sets. - SSO and OIDC with the customer's identity provider. - An audit record of each action of each worker. - Nine layers of real-time security and governance. See https://usemissioncontrol.com/ai/security.md and https://usemissioncontrol.com/ai/governance.md.