How to delete your GitKraken account

About deleting your GitKraken account

GitKraken is a powerful cross-platform Git client and tool suite designed to streamline version control workflows for developers. It integrates directly with providers like GitHub, GitLab, and Bitbucket to visualize commit graphs and manage complex branching operations. Many developers choose to delete their GitKraken account when migrating to native CLI workflows, switching to integrated IDE tools like VS Code’s built-in Git capabilities, or when offboarding from a team-managed subscription.

Users often seek to close their accounts for several specific reasons unique to the GitKraken ecosystem:

• Consolidating toolchains to reduce the software footprint in a development environment.
• Removing cached authentication tokens that link GitKraken to private enterprise repositories.
• Terminating a subscription plan to prevent recurring charges for unused seats in the GitKraken Client or the GitKraken Dev Ecosystem.
• Addressing concerns regarding data synchronization between local repositories and the GitKraken cloud-hosted services.

What happens to your data

When you initiate the deletion process for your GitKraken account, the platform triggers a removal request for your user profile and associated cloud-stored configurations. GitKraken typically purges your stored preferences, profile details, and links to integrated third-party Git hosts. However, it is essential to note that while GitKraken removes your account access, they may retain certain data for billing and regulatory compliance purposes.

Types of data GitKraken collects and processes include:

• Identity and authentication credentials for third-party Git providers.
• Usage statistics related to repository interactions and feature performance.
• Subscription history and billing information for Pro or Enterprise tiers.
• IP address and browser-related telemetry for security authentication.

Privacy considerations

Using GitKraken involves connecting highly sensitive repository data to their application. From a privacy perspective, keeping an inactive account increases your surface area for potential security vulnerabilities, especially if the account is linked to your private or work-related GitHub/GitLab organizations. If you are moving away from the GitKraken platform, deleting your account helps ensure that old API tokens and workspace configurations are no longer stored on their infrastructure.

• Revoke GitKraken application access from your GitHub or GitLab 'Authorized OAuth Apps' settings before deleting your GitKraken account.
• Manually delete local configuration folders (usually found in your home directory under .gitkraken) to remove all cached local data.
• Ensure all team-shared GitKraken workspaces are transferred to another administrator before closing your account to prevent data loss for your colleagues.

Frequently Asked Questions

Does deleting my GitKraken account remove my source code from my Git provider?

No. GitKraken acts as a client interface. Your repositories hosted on GitHub, GitLab, or Bitbucket remain unaffected, though you will lose the UI-based connection provided by GitKraken.

Will deleting my account automatically cancel my Pro subscription?

Yes, but you should verify this in the billing dashboard before deletion to avoid potential automated renewal issues during the final processing window.

Can I recover my GitKraken account after deletion?

Account deletion is typically permanent. Once the account is purged from their servers, your workspace history and connected account associations cannot be restored.

Does GitKraken store my Git credentials?

GitKraken stores authentication tokens securely to allow you to interact with your repositories. Deleting your account revokes these tokens on the GitKraken side.

Is my local repository affected by deleting the GitKraken app?

No. Your local files and the .git directory within your project remain intact, as GitKraken only monitors these files; it does not store the files themselves on its servers.