Delete data

You can delete a single connection, a whole workspace, or your account at any time. Deletion takes effect at once and cannot be undone.

Three ways to delete

Delete	Who	Where
A connection	Owners	Connections, the remove button on the connection
A workspace	Owners	Settings, Delete workspace, after typing its name
Your account	You	Settings, Delete account

Delete a connection

Removing a connection deletes, at once:

Its stored credential: the encrypted token or kubeconfig, or for AWS the role ARN and ExternalId.
Every resource it discovered, and the lines to and from them on the map.
The logs, metrics, and events Groundcrew read for those resources.

Past incidents stay as history, without the deleted resources' details. When the removal is done, the dialog says how many resources were removed from the map and what to remove on your side to end access completely.

Delete a workspace

Deleting a workspace removes everything Groundcrew stored for it: members and invites, connections and their credentials, the map, runs and their steps, approvals, incidents, telemetry, usage, and the activity log. Queued work for its runs is cancelled. Cached cloud sessions for its connections are dropped at once.

Apps Groundcrew deployed keep running in your accounts, and pull requests it opened stay open on GitHub. Remove them there if you no longer want them. How to remove deployed apps.

Delete your account

Deleting your account removes:

Your sign-in identities and pending sign-in links.
Your memberships.
Every workspace where you are the only member, with everything in it.

Shared workspaces stay for the other members. If you are the only owner of a shared workspace, the dialog says so: make someone else an owner there first, or delete that workspace. Your name stays on approvals you made and in the activity logs of shared workspaces, as a record of who did what.

Ending access on your side

Groundcrew can delete only what it stores. The access you granted lives in your own accounts, and removing it there ends it for good:

AWS: delete the groundcrew-read-only CloudFormation stack. Remove apps Groundcrew deployed first, if you used deploys.
GitHub: uninstall the Groundcrew GitHub App in your account or organization settings. Access ends at once, and Groundcrew stops the connections that used it.
Vercel: delete the token in your Vercel account settings.
Kubernetes: delete the service account and its RBAC with kubectl delete -f on the manifests you applied. That also ends every token issued for it.
Slack: remove the incoming webhook in Slack.

Each connect guide has its own removal steps.

What is kept

Server logs, which may include your email address and request addresses, expire after 30 days.
The database has no backups, so a deleted workspace or account cannot be restored, by you or by us.

The Privacy Policy lists everything Groundcrew stores and who processes it.