How to delete your LayerCI account

About deleting your LayerCI account

LayerCI is a powerful platform designed to provide full-stack preview environments for developers, allowing teams to spin up ephemeral clones of their entire application stack with every pull request. By integrating directly with version control systems, it automatically generates environments that mirror production, facilitating rapid testing and collaboration. Users rely on LayerCI to manage complex infrastructure states, database snapshots, and environment variables.

Deleting your LayerCI account is a significant step for developers moving away from the platform or looking to consolidate their infrastructure. Common reasons for account deletion include:

• Migrating to a different preview environment provider or self-hosted solution.
• Dissolving a project where the ephemeral environments are no longer needed.
• Security compliance requirements to purge persistent development snapshots from third-party servers.
• Minimizing the attack surface by removing access tokens associated with connected GitHub or GitLab repositories.

What happens to your data

When you initiate the deletion process for your LayerCI account, the platform triggers a cleanup routine designed to purge the artifacts associated with your development workflow. LayerCI handles sensitive data including configuration files, environment variables, and cached build outputs. While the primary objective of deletion is the removal of active environments, you should be aware that logs and metadata may persist in accordance with their legal retention policies. Types of data handled by LayerCI include:

• Repository access tokens and credentials for Git providers.
• Persistent database snapshots and volume data generated during preview sessions.
• Environment-specific configuration files and secrets.
• Build history logs and performance metrics linked to your personal user ID.

Privacy considerations

Using LayerCI involves granting third-party access to your codebase and deployment pipelines, which necessitates careful privacy management. Because LayerCI requires read/write access to your version control provider, your account deletion is the only way to effectively revoke these automated permissions and stop the synchronization of your project data to their infrastructure. Consider these privacy tips:

• Revoke OAuth application access in your GitHub or GitLab security settings after deleting your LayerCI account to ensure no dangling permissions exist.
• Audit your environment variables for any production-level API keys that may have been stored in LayerCI settings before finalizing deletion.
• Export any necessary build logs or debugging data locally, as these will be irrecoverable once the account is purged.

Frequently Asked Questions

Will deleting my LayerCI account remove my connected GitHub repository?

No, deleting your LayerCI account only removes the platform's access and your environment history; it will not delete or alter the source code stored in your connected GitHub or GitLab repository.

Can I recover my preview environments after account deletion?

No, once you initiate the account deletion process, all ephemeral environments, database snapshots, and build logs are permanently scrubbed from the LayerCI servers.

Does LayerCI keep backups of my environment after deletion?

Generally, production services like LayerCI do not retain user-specific project data after an account is closed, though metadata may briefly exist in encrypted backups required for system integrity.

Should I clear my secrets before deleting the account?

Yes, it is best practice to rotate any API keys or secrets that were input into LayerCI environment settings before submitting your deletion request.

How long does the deletion take to process?

Once you finalize the request in your settings tab, the removal of your account data is typically instantaneous on the platform's active servers.

Will I still receive marketing emails after deleting my LayerCI account?

Deleting your account should stop all functional communications, but you may need to separately unsubscribe from their marketing mailing list if you previously opted in.