# Security and data

> What leaves your network, how devices prove they belong to your fleet, and how access is revoked.

## What stays on your network

Models run on your devices. Prompts, replies and the files models read never pass through Cascadia's servers.

Devices send the console a heartbeat so it can show your fleet's health. A heartbeat contains:

- The device's build, hardware, operating system, free memory and disk, and how many requests it's handling
- The models it serves and stores, and its update status
- Its network addresses
- Usage counts per model: requests, errors, token counts and latency
- Results of commands you sent it, such as restarts

It never contains the text of prompts or replies.

## How devices join your fleet

Your organization has its own certificate authority, hosted by Cascadia at `ca.cascadia.to/o/<url-name>`.

- When a device enrolls, it creates its own private key, which never leaves the device. The certificate authority signs a certificate for its public key.
- Every device pins your certificate authority's key at enrollment and refuses certificates signed by anything else.
- A device's certificate names your organization. Devices from another organization can't join your fleet, even if they reach your network.
- Certificates renew automatically. If your organization is suspended, certificates stop renewing and the fleet stops serving within about a week.

Enrollment credentials are one-time and expire. Anyone holding an unspent credential can add a device to your fleet, so treat installers and install links like passwords until they're used.

## Revocation

Revoking a device, API token or Fleet Manager key takes effect across the fleet within about a minute. Devices check your certificate authority's revocation list regularly, so revocation works even without the console reaching the device directly.

## API access

The gateway rejects requests without a valid API token from your organization. Tokens are signed by your certificate authority and checked by each device, and each one has a label you can revoke it by. See [Connect an application](/enterprise/use/connect-an-application/).

## Remote commands

Commands such as restarts, model changes and updates must be signed by a key your organization approved. **Settings → Operator activity** in the console lists every command your devices accepted, including any signed by Cascadia, as reported by the devices themselves.

## Software integrity

Releases are signed. Devices and the Fleet Manager verify a release's signature before installing it, and devices roll back automatically if a new build won't start. See [Updates](/enterprise/fleet-manager/updates/).
