How to delete your DeployHQ account

About deleting your DeployHQ account

DeployHQ is a sophisticated deployment platform designed to automate code delivery from repositories like GitHub, Bitbucket, or GitLab to your web servers via FTP, SFTP, or SSH. It streamlines the development lifecycle, allowing teams to manage multiple projects and deployment environments with precision. By centralizing build processes and release notifications, DeployHQ creates a high-stakes environment where your server credentials and source code metadata are constantly in motion.

Users may choose to delete their DeployHQ account for several reasons related to the platform’s nature. Perhaps you have migrated your CI/CD pipelines to a native integrated tool like GitHub Actions, or your project requirements have shifted away from traditional FTP/SFTP deployment patterns. Additionally, if your team is auditing security footprints or consolidating SaaS tools, removing the persistent access DeployHQ holds to your production servers becomes a critical security hygiene step.

• Streamlining infrastructure by moving away from legacy FTP/SFTP workflows.
• Reducing the attack surface by revoking DeployHQ's SSH key access to production servers.
• Consolidating development toolchains into a single ecosystem.
• Ending subscription cycles for inactive legacy projects.

What happens to your data

When you initiate the deletion of your DeployHQ account, the platform attempts to purge account-specific records. However, because DeployHQ acts as a conduit between your version control system and your production environments, specific data points are handled with varying retention policies.

• Server connection details: SSH keys, FTP passwords, and server IP addresses stored within your projects.
• Deployment logs: Historical records of every push, build, and deploy execution initiated through the platform.
• Repository configurations: Webhook tokens and source control integration settings.
• User profile information: Associated email addresses, account billing history, and team member permissions.

Please note that while DeployHQ removes active data from your dashboard, snapshots of deployment history may exist in secure, offline backup archives held by their parent company, Rugged Interactive, for a limited time to comply with accounting and operational auditing requirements.

Privacy considerations

DeployHQ functions as a processor of highly sensitive deployment data. By its very design, it requires wide-reaching permissions to access your server infrastructure. Failing to delete your account correctly can leave orphan SSH keys or old project configurations active on your servers, which creates a significant privacy and security vulnerability.

• Audit your server's authorized_keys files to ensure no DeployHQ-generated keys remain after account closure.
• Revoke OAuth permissions for DeployHQ within your GitHub or Bitbucket account settings.
• Review your project logs before deletion to ensure no sensitive API keys were inadvertently committed to the platform’s internal build history.
• Ensure that all collaborators have removed their personal instances from the platform to avoid lingering team associations.

Frequently Asked Questions

Will deleting my account automatically cancel my subscription?

No, you must manually cancel your subscription plan in the billing section before the account closure option becomes fully available.

Does deleting the account revoke SSH access to my servers?

While deleting the account stops DeployHQ from triggering new deployments, you must manually remove the SSH public keys from your server's authorized_keys file for complete security.

Can I recover my deployment history after deleting the account?

No, once the account is terminated, all deployment logs, server configurations, and history are permanently scrubbed from the active DeployHQ database.

Do I need to remove my GitHub/Bitbucket repository links separately?

It is highly recommended that you revoke the application access for DeployHQ within your version control provider's security settings to ensure total disconnection.

What happens to the team members associated with my DeployHQ account?

Deleting an account generally removes the entire organization or team structure, meaning all members will lose access to the shared projects simultaneously.

Is my credit card information stored by DeployHQ after deletion?

DeployHQ uses third-party payment processors like Stripe; while they may retain transaction records for tax compliance, your sensitive payment instrument details are not held directly on DeployHQ's internal servers.