How to delete your Gitpod account

About deleting your Gitpod account

Gitpod provides cloud-based ephemeral development environments that automate the setup of complex coding projects. By integrating directly with platforms like GitHub, GitLab, and Bitbucket, Gitpod manages repositories, environment variables, and pre-built workspace configurations to eliminate the "it works on my machine" problem. Users typically store sensitive information within these environments, including SSH keys, cloud provider credentials for automated deployments, and proprietary source code.

There are several reasons why a developer might choose to delete their Gitpod account. You might have migrated your workflow to a local IDE, completed a specific project that no longer requires cloud-based computation, or you may be concerned about the security of hosting your development secrets within a third-party containerized environment.

• Discontinuing use of cloud-based ephemeral workspaces.
• Consolidating development workflows to self-hosted or local infrastructure.
• Removing linked repository access tokens and OAuth permissions from Gitpod's control.
• Reducing the digital footprint of legacy developer environments.

What happens to your data

When you initiate the deletion process, Gitpod triggers a removal of your personal profile and account-level settings. Because Gitpod operates on a containerized architecture, it handles different categories of data. It is important to understand that while your Gitpod-specific account data is removed, you should also manually revoke Gitpod's access permissions within your connected Git providers (GitHub, GitLab, or Bitbucket).

• Account profile information: Your email, username, and authentication tokens.
• Workspace configurations: Custom Dockerfiles, .gitpod.yml files, and environment setup scripts.
• Workspace persistence data: Snapshots, specific user-defined environment variables, and any files stored in the workspace file system.
• Usage history: Logs related to your workspace activity and compute consumption.

Gitpod generally purges these environments upon account closure, though some metadata may remain in audit logs to comply with tax and service billing requirements. If you have granted Gitpod write access to your repositories, removing the account from Gitpod does not retroactively delete code or changes you have pushed back to your primary Git provider.

Privacy considerations

Using Gitpod involves granting significant permissions to your VCS (Version Control System). Gitpod needs these permissions to clone private repositories and manage webhooks. If you are concerned about your development privacy, you should treat the deletion process as a complete audit of your third-party integrations.

• Regularly rotate any secrets, API keys, or SSH keys that were used within a Gitpod workspace.
• Revoke OAuth application permissions in your GitHub/GitLab settings after account deletion.
• Review your Git provider’s webhooks to ensure Gitpod-related hooks have been removed.
• Be aware that Gitpod logs compute metrics for billing purposes; ensure your workspace does not contain sensitive hardcoded credentials that might be ingested into these telemetry systems.

Frequently Asked Questions

Does deleting my Gitpod account delete my GitHub repositories?

No, deleting your Gitpod account only removes the connection and the cloud-based workspace environments hosted by Gitpod. It does not affect the source code stored in your connected GitHub repositories.

Can I recover my Gitpod workspace after account deletion?

No, once the account deletion process is finalized, all associated workspaces, snapshots, and configuration files are permanently purged from Gitpod's systems and cannot be recovered.

Is it necessary to revoke Gitpod access from my GitHub settings?

Yes, it is highly recommended. While Gitpod removes the account, manually revoking OAuth access in GitHub ensures that no residual tokens or webhooks remain active.

What happens to my environment variables in Gitpod?

When the account is deleted, your stored environment variables are deleted alongside your profile and workspaces.

Does Gitpod store my credit card information if I have a paid plan?

Gitpod utilizes third-party payment processors like Stripe. While Gitpod keeps billing history for accounting, specific credit card data is handled securely by the payment processor, not directly stored by Gitpod.

Will my workspace images be deleted?

Yes, any custom Docker images or pre-builds associated with your user account and workspaces are removed upon account closure.