EraseRegistry
Back to directory
Qovery logo
Developer ToolsEasy Delete

How to delete your Qovery account

Deletion instructions

Last verified: 10/18/2026

To delete your Qovery account, log in to the Qovery console and navigate to your organization or account settings. Within the settings menu, locate the 'Danger Zone' section. Select the option to delete your account permanently and confirm your request to finalize the process.

Open deletion page

About deleting your Qovery account

Qovery is an Internal Developer Platform (IDP) designed to run on top of your own cloud provider accounts, such as AWS, GCP, or Scaleway. By abstracting the complexities of Kubernetes, Qovery allows developers to deploy applications, manage databases, and handle environment previews with ease. It acts as a bridge between your source code and your cloud infrastructure, storing configurations, environment variables, and deployment histories to maintain application state.

Users may choose to delete their Qovery account for several reasons related to their infrastructure lifecycle or privacy concerns. You might want to close your account if:

  • You have migrated your infrastructure management to a different platform or custom CI/CD pipeline.
  • You are decommissioning a project and want to ensure no stale credentials or configuration metadata remain in the Qovery console.
  • You are concerned about the security of third-party access to your cloud accounts and wish to revoke all platform-level permissions.
  • Your organization is consolidating toolsets and no longer requires the abstracted interface provided by Qovery.

What happens to your data

When you trigger an account deletion in Qovery, the platform typically removes the user profile information and associated metadata from its central console. However, because Qovery operates by interacting with your external cloud accounts, the deletion process does not automatically remove the infrastructure resources—such as EC2 instances, RDS databases, or load balancers—already provisioned in your cloud provider's console. You must manually clean up these resources within your AWS or GCP dashboard to avoid ongoing costs.

Specific data types handled by Qovery include:

  • Git repository authentication tokens for CI/CD integration.
  • Cloud provider IAM access keys or service account credentials.
  • Application environment variables and secret configurations.
  • Build logs and deployment status history metadata.
  • User profile data, including email, login identifiers, and organizational roles.

Privacy considerations

Qovery’s privacy model relies heavily on the principle of least privilege, but since it requires access to your cloud environment, it effectively becomes a central point of failure if your account credentials are compromised. Privacy-conscious developers should perform a thorough audit of what the platform has accessed before deleting the account. If you are concerned about your digital footprint, ensure that you remove all platform integrations before selecting the account deletion option.

  • Revoke IAM roles or service account keys granted to Qovery from your cloud provider console before deleting the account.
  • Audit your connected Git repositories to ensure no deploy keys remain.
  • Download any deployment logs or audit trails you may need for compliance before finalizing account closure.
  • Contact Qovery support if you require a formal Data Processing Agreement (DPA) termination verification.

Frequently Asked Questions

Does deleting my Qovery account automatically delete my AWS/GCP resources?

No, deleting your Qovery account only removes your access to the Qovery console. You must log into your cloud provider separately to terminate or delete the underlying clusters and databases.

Will Qovery retain my build logs after I delete my account?

Generally, Qovery purges metadata associated with your account per their data retention policy, but logs cached during active deployment sessions may be subject to standard platform archival windows.

Can I recover my environment variables after account deletion?

Once the account deletion process is finalized in the Danger Zone, your configuration settings and environment variables are typically unrecoverable. Ensure you export these from the console prior to deletion.

Do I need to delete my GitHub/GitLab integrations before deleting my Qovery account?

While the account deletion should sever these ties, it is a best practice to remove the Oauth app permissions directly within your Git provider’s settings for enhanced security.

What happens to my organization members when I delete the owner account?

If you are the sole owner of a Qovery organization, deleting your account may orphan the organization. You should transfer ownership to another team member or delete the organization first.

Is my deployment history wiped immediately?

Most account deletion requests trigger an immediate removal from the active database, though backups or system snapshots may hold data for a short recovery period as mandated by platform operations.

Was this guide helpful?

Related Developer Tools services

Browse Developer Tools services