Data residency & retention

Every MeetCrew tenant is hosted in one Azure region, with a fixed retention period 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

Today every MeetCrew tenant is placed in Microsoft Azure’s US East region at onboarding, and the data MeetCrew stores for it stays in the United States: it is stored in US East, and any backup or recovery copies Azure keeps, including in its paired region, are in the United States too. Version 1 serves organizations established in the United States and Canada; self-service signup is open to US organizations, and a Canadian organization onboards by contacting us. Three things leave Azure during a meeting: the meeting audio, which our meeting-connectivity provider carries and our speech-to-text provider transcribes on its own hosted service and does not keep; the teammate’s own synthesized speech, when its animated avatar is on, which Cloudflare carries to a GPU server MeetCrew operates itself in the United States to animate the avatar’s face; and the request to your own backend agent, which goes wherever you host that agent. A region change is not an in-place edit; it means decommissioning and re-onboarding.

Retention

Meeting transcripts and the memory extracted from them are kept for 24 months and then deleted. In v1 the period is fixed, and your console shows it read-only. 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 a priced add-on on Enterprise, arranged with us. In v1 the key is held in MeetCrew’s Azure tenant rather than your own. The key has to be chosen before your tenant stores any meeting memory, and once it is turned off it cannot be turned back on. 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.