How to delete your DeployBot account

About deleting your DeployBot account

DeployBot is a specialized deployment automation tool designed to streamline code deployments from version control systems like GitHub, Bitbucket, and GitLab to your various servers. By connecting directly to your repositories, it automates the release process, ensuring code reaches your environments without manual intervention. Users often rely on it to manage complex deployment pipelines, environment variables, and build configurations.

However, there are several reasons why you might choose to delete your DeployBot account. You may have migrated to a different CI/CD provider, your project has reached its end-of-life, or you wish to consolidate your digital footprint to minimize exposure to third-party integrations. Deleting your account ensures that your server access keys and repository connection tokens are no longer managed or stored by the service.

• Streamlining deployment workflows for multiple code repositories.
• Integration with various cloud providers and private servers via SSH or FTP.
• Management of deployment history and environmental configurations.

What happens to your data

When you trigger the permanent deletion of your DeployBot account, the platform initiates the removal of the data associated with your profile. This typically includes your personal user information, email address, and billing details linked to your account. Because DeployBot functions as a bridge between your code and your infrastructure, it stores sensitive information that requires careful handling upon termination.

• Repository connection tokens and SSH keys linked to your accounts.
• Deployment history, including build logs and success/failure timestamps.
• Environmental variables and server configuration details.
• User profile information and organization association data.

While DeployBot processes deletion requests, they may retain certain transactional records for financial auditing and legal compliance purposes as mandated by accounting regulations. Ensure you revoke any API access tokens or SSH public keys you may have authorized for DeployBot in your external service providers (e.g., GitHub or AWS) after closing your account.

Privacy considerations

Using a CI/CD service like DeployBot involves granting significant permissions to your internal code and infrastructure. Privacy-conscious users should be aware that automated tools require access to your source code and your production server environment to function correctly. This makes the removal of these permissions critical once you stop using the service.

• Always audit the permissions granted to DeployBot in your GitHub or Bitbucket settings before deleting your account.
• Remove any SSH keys stored in your server’s authorized_keys file that were originally generated by DeployBot.
• Consider that metadata regarding deployment frequency may have been recorded during the lifetime of your account.

Frequently Asked Questions

Will deleting my account automatically disconnect my GitHub repositories?

While deleting your DeployBot account removes the connection within the DeployBot interface, it is best practice to manually revoke the OAuth app permissions in your GitHub settings to ensure absolute security.

Can I recover my deployment logs after account deletion?

No, once you initiate the permanent deletion process, your account, including all historical logs and build configurations, is removed from their systems and cannot be restored.

Does DeployBot store my database contents?

DeployBot generally manages the deployment process rather than the data itself; however, if your deployment scripts include database migration tasks, ensure no sensitive data was passed through logs.

Is it possible to pause my account instead of deleting it?

DeployBot does not have a formal 'pause' feature, so you would need to cancel your subscription to stop billing while keeping your account configuration intact.

How long does the data removal take?

Account deletion is designed to be near-instantaneous in the dashboard, but you should allow for standard backend propagation time for the full removal of your information.

What should I do with my SSH keys after deletion?

You should immediately delete any SSH keys or deployment tokens that you provided to DeployBot from your server's access control lists.