How to delete your Cloud66 account

About deleting your Cloud66 account

Cloud66 is a specialized platform that simplifies the deployment and management of containerized applications across multiple cloud providers like AWS, GCP, and Azure. By providing a wrapper around complex infrastructure orchestration, it handles everything from CI/CD pipelines to database backups and SSL management. Users often manage highly sensitive production environments, SSH keys, and cloud provider credentials through this interface.

There are several reasons a developer or organization might decide to delete a Cloud66 account. Perhaps you have migrated your infrastructure to a native Kubernetes environment, consolidated your stack management under a different internal tool, or simply need to purge unused infrastructure connections to mitigate potential security risks. Removing your account is a critical step in offboarding your DevOps stack.

• Infrastructure migration to native EKS or GKE.
• Security consolidation by removing third-party access to cloud credentials.
• Sunset of specific legacy projects managed via Cloud66 stacks.
• Transitioning away from managed services to minimize attack surfaces.

What happens to your data

When you initiate the deletion process for your Cloud66 account, the platform takes steps to revoke its access to your cloud provider resources. However, it is essential to understand that while Cloud66 stops managing your infrastructure, you should also manually remove any IAM roles or service account keys you previously granted to them. Data retained during the deletion process generally includes metadata related to billing cycles and support logs necessary for regulatory compliance.

• Cloud provider integration tokens and API keys.
• Deployment history and application build logs.
• Database configuration settings and environment variables.
• SSH keys used for server provisioning.
• User metadata and team permissions within the organization.

Privacy considerations

Using Cloud66 involves providing the service with significant control over your cloud environment. Because Cloud66 interacts directly with your production infrastructure, privacy concerns often center on the storage of your cloud credentials and the potential access the platform has to your environment logs. To maintain optimal privacy, ensure that the IAM policies you grant to Cloud66 are strictly scoped using the principle of least privilege.

• Regularly audit the permissions granted to the Cloud66 service account in your cloud provider dashboard.
• Rotate your cloud API keys immediately after deleting your Cloud66 account.
• Ensure that all environment variables containing sensitive secrets are encrypted within your cloud provider's secret manager rather than relying solely on Cloud66 storage.
• Review your stack logs for any sensitive information that may have been cached by Cloud66.

Frequently Asked Questions

Does deleting my Cloud66 account destroy my cloud infrastructure?

No, deleting your account removes the Cloud66 management layer, but your actual servers and databases running on AWS, GCP, or other providers remain active.

Will my billing stop immediately upon account deletion?

Yes, once the account is closed, your subscription is terminated and no further charges will be applied to your payment method.

Can I recover my stack configurations after deletion?

No, once an account and its associated stacks are deleted, the configurations, deployment history, and internal settings are permanently purged from Cloud66 servers.

Should I revoke IAM permissions before deleting my account?

It is highly recommended to revoke the IAM roles or service account permissions you granted to Cloud66 in your cloud console before finalizing the account deletion.

How long does Cloud66 keep my data after I request deletion?

Cloud66 follows standard data retention policies, usually purging most user data shortly after deletion, though certain transactional and billing records may be retained for legal compliance.

Can I delete my organization without deleting my individual account?

Yes, you can leave or delete specific organizations within your account settings, provided you are an administrator of those entities.