Data residency & retention

Each MeetCrew deployment is pinned to a single region, with retention you configure and control commitments that hold for every customer by default. This page describes where your data lives, how long it stays, and who holds the keys.

Residency

Your tenant is placed in one region at onboarding, and all of its data stays there. There is no cross-region replication. Version 1 regions are the United States (excluding Illinois) and Canada. A region change is not an in-place edit; it means decommissioning and re-onboarding.

Retention

Retention is configurable per tenant and enforced to the statutory ceiling for your jurisdiction. When a record’s retention period expires, it is cryptographically shredded rather than merely marked deleted. At the capture layer, the meeting bot runs zero-data-retention: it stores no recording at any point, so your durable memory exists only in your own MeetCrew tenant store.

Keys and use

Customer-managed encryption keys are supported, so your meeting memory can be encrypted at rest with a key held in your own Azure Key Vault and revocable by you. Customer meeting content is never used to train, retrain, or fine-tune any model. Identity is attributed from platform metadata only — MeetCrew holds no voiceprints.