How to delete your RunKit account

About deleting your RunKit account

RunKit is an interactive, browser-based Node.js environment that allows developers to prototype code, test npm packages, and share interactive notebooks directly in the cloud. Because RunKit integrates deeply with the Node.js ecosystem, it creates a unique trail of technical experimentation and cloud-hosted code snippets that may not be intended for long-term archival.

Users often choose to delete their RunKit accounts to clear out stale project prototypes, reduce their digital footprint, or move away from cloud-hosted IDEs for better local control. Key reasons for deletion include:

• Removing proprietary code snippets that were used for quick testing.
• Minimizing the number of platforms where your GitHub credentials or email addresses are stored.
• Clearing out deprecated npm package experiments that are no longer actively maintained.

What happens to your data

When you trigger the account deletion process in RunKit, the platform generally removes your associated notebooks and profile data from their primary database. RunKit acts as a playground for Node.js, meaning the primary assets associated with your identity are the code blocks and their output states.

• User Profile: This includes your linked email address and potentially associated authentication tokens from social logins.
• Notebooks: All saved REPL instances, custom endpoints, and API proxies created within your workspace.
• Metadata: Timestamps and configuration settings related to your coding environment.

While primary data is removed, RunKit may retain information in backups or server logs as required for operational security or to comply with applicable legal regulations. Once the account deletion is finalized, the persistent links to your previously shared notebooks will generally result in 404 errors.

Privacy considerations

Using a platform like RunKit involves trusting a third party with your experimental code and potentially sensitive logic. Because RunKit interfaces with the wider npm ecosystem, privacy is a major concern for developers who test private-package-related logic in a public or shared notebook environment.

• Audit Dependencies: Before deleting, ensure you have locally backed up any logic that you might want to reuse elsewhere.
• Public Notebooks: If you have made notebooks public, keep in mind that these snippets may have been indexed by search engines or shared in technical forums before deletion.
• Authentication: RunKit often uses third-party authentication services, so ensure you manage your linked account permissions via your service provider (e.g., GitHub) after deletion.

Frequently Asked Questions

Does deleting my account remove my public notebooks?

Yes, initiating the account deletion process via the settings sidebar triggers the removal of all associated content, including public and private notebooks.

Can I recover my data after deleting my RunKit account?

No, RunKit typically treats account deletion as an irreversible action. Ensure you have exported any essential code before starting the process.

Does deleting my account also remove my npm account?

No, RunKit and npm are separate services. Deleting RunKit only removes your account data stored on the RunKit platform.

Will my shared notebook links continue to work?

Once the account is deleted, the notebooks are removed, and any existing URLs to those notebooks will no longer display content.

Is there a way to delete just one notebook instead of the whole account?

Yes, you can manage and delete individual notebooks directly from the notebook menu interface without deleting your entire profile.

Is my code protected while it is on RunKit?

RunKit provides tools to share code, but it is not intended for storing sensitive credentials or proprietary production logic. Always practice good security hygiene by not hardcoding keys in your notebooks.