Data lifecycle
Control cloud workspace data without a support ticket.
Workspace owners control the hosted copy; developers control repo-local Brief files. The two stores are separate so deleting one never pretends to delete the other.
Last updated July 19, 2026Workspace export
In Workspace Settings, owners and admins can download a no-store JSON export containing membership, repo metadata, maps, source records, rules, skills, context packets, reviews, handoffs, learnings, usage, and audit records. Connector key prefixes and scopes are included for audit; connector secret hashes are not.
Delete a cloud workspace
A workspace owner can type the exact workspace name in Settings and permanently delete that workspace. Database cascades remove its connectors, memberships, invitations, repo records, maps, source records, team guidance, context packets, reviews, handoffs, learnings, usage, and audit records. The organization, subscription, authentication account, and any other workspace are deliberately left unchanged.
Delete local data
Repo-local indexes, wiki pages, receipts, and preferences live under the repo's .briefdirectory or the connector's configured local cache. Remove those files with the same filesystem and source-control process used for other developer tooling. Deleting the hosted workspace does not reach into a developer machine.
Retention
Hosted records remain while the workspace is active so maps, team guidance, and proof history continue to work. Brief does not currently advertise a shorter automatic retention window. Owners can export and delete the workspace at any time. Backup expiry is governed by the managed database provider's backup lifecycle.
Account requests
Delete owned workspaces first. For authentication-account access, correction, or deletion after workspace cleanup, contact privacy@runbrief.ai from the account email. Brief will verify the request before changing an authentication record.