How to delete your Envoyer account

About deleting your Envoyer account

Envoyer is a specialized deployment service designed specifically for Laravel applications. By automating the deployment process through Zero Downtime Deployments, it allows developers to push code updates to servers without interrupting the user experience. Because it integrates directly with version control systems like GitHub, GitLab, and Bitbucket, the platform handles sensitive access tokens, server SSH keys, and configuration environment variables.

Users often choose to delete their Envoyer account when they transition away from Laravel-based architecture, consolidate their DevOps toolchain into a single CI/CD provider, or simply need to purge server credentials after a project is deprecated. Common reasons for account closure include:

• Security lifecycle management for decommissioned project infrastructure.
• Transitioning to serverless deployment models that do not require Envoyer's specific provisioning.
• Compliance requirements to purge third-party access to production environments.

What happens to your data

When you initiate the deletion process for your Envoyer account, the service aims to purge the metadata associated with your deployment history, server connections, and heartbeat monitors. Since Envoyer acts as a bridge to your own cloud infrastructure, the actual code residing on your servers remains untouched unless you manually remove it from those instances.

Data categories typically purged upon account deletion include:

• Deployment logs and version history associated with your projects.
• API keys and repository access tokens used for GitHub/GitLab integration.
• Server SSH configurations and environment variable mappings.
• Notification channel settings, such as Slack or SMS integrations.
• Payment and billing history stored within the Envoyer interface.

Privacy considerations

Envoyer functions as an intermediary, meaning it requires elevated permissions to interact with your code repositories and production servers. Privacy-conscious users should be aware of the extent of these permissions before maintaining a long-term account. To maximize your privacy, consider the following:

• Rotate your server SSH keys immediately after deleting your Envoyer account to invalidate any previous connection paths.
• Revoke the OAuth access tokens you granted to Envoyer within your GitHub or Bitbucket settings under 'Authorized OAuth Apps'.
• Check your cloud provider (DigitalOcean, Linode, AWS) to ensure that no lingering deployment scripts or Envoyer-specific agents remain active.

Frequently Asked Questions

Does deleting my Envoyer account remove my code from my server?

No, Envoyer only manages the deployment process. Your source code and database remain on your host server until you manually delete them.

Can I recover my deployment history after deleting my account?

No, once the account deletion process is finalized, all historical deployment logs and activity metrics are permanently removed from the Envoyer database.

Do I need to remove my server before deleting my Envoyer account?

It is best practice to remove servers from your Envoyer dashboard first to ensure the service disconnects its SSH handshake protocols before you close the account.

Does deleting my account cancel my active subscription?

Yes, selecting the deletion option within the billing or profile section will automatically terminate your subscription and prevent further charges.

Will my linked GitHub repositories be affected by account deletion?

Your actual repositories remain safe; only the link between Envoyer and those repositories is severed, meaning Envoyer will no longer have permission to pull code.