The lifecycle of a session.
Four stages, in order, from the moment a press connects through to the moment the data is gone. Plus the region map, the retention default, and the one commitment that doesn’t bend.
Capture
Only what the session needs. Chat is captured by default. Voice is captured as audio; transcripts are derived on request and stored separately. Screen-share is captured only when the customer turns on recording, never on by default. Customer code shared in-session is captured to the session transcript and never to a separate corpus.
Retention
Ninety days, by default. After ninety days, transcripts and recordings are erased from primary storage and removed from backups within the next backup rotation. Enterprise customers can configure retention from 7 days up to 7 years per workspace, or set legal-hold on a per-session basis.
Anonymization
When session data is used for internal quality review, it is anonymized first, customer identifiers, code repository names, and personal data are stripped before any human reviewer sees the content. Anonymized samples never leave the Relay environment and are not used to train any model.
Deletion
Customer-initiated deletion is honored within seven days for primary stores and within thirty days for backups. A signed deletion certificate is issued on request. Engineering accounts that lose access to a tenant lose access to the tenant's session data within minutes, not days.
Region map.
Customers choose where session data lives at workspace creation. Enterprise plans can pin specific data classes to specific regions.
- ·United States, AWS us-east-1 (N. Virginia), us-west-2 (Oregon)
- ·European Union, AWS eu-central-1 (Frankfurt), eu-west-1 (Ireland)
- ·United Kingdom, AWS eu-west-2 (London)
- ·India, AWS ap-south-1 (Mumbai) for India-resident handling
- ·Asia Pacific, AWS ap-southeast-1 (Singapore), ap-northeast-1 (Tokyo)
- ·Australia, AWS ap-southeast-2 (Sydney)
90 days. Change it any time.
The default retention is ninety days because most teams need to re-watch a session within the first quarter and rarely after. To change it: Workspace → Settings → Data → Retention.
Set it to 7, 30, 90, 180, 365 days, or a custom value up to 7 years. Enterprise plans support per-session legal hold.
We don’t train on your code.
Customer code, prompts, transcripts, and session recordings are never used to train a foundation model, not ours, not a vendor’s, not under any plan, not under any agreement negotiated separately. This is in the master subscription agreement and it does not get redlined.