How to delete your Puck account

About deleting your Puck account

Puck is a specialized visual editor for React, designed to help developers build content-managed pages without relying on traditional, restrictive CMS platforms. By allowing developers to create drag-and-drop interfaces directly within their codebase, Puck handles sensitive project configurations, API keys, and repository links that act as the backbone of your web applications.

Users often choose to delete their Puck accounts when migrating to different design systems, pivoting their development workflow, or strictly minimizing the footprint of third-party tools within their infrastructure. Deleting your account is the only way to ensure that your project metadata and associated workspace settings are no longer accessible through Puck's interface.

• Project configuration files
• Integrated component libraries
• User-specific dashboard settings
• API connection logs

What happens to your data

When you initiate the deletion process via the Danger Zone in your project settings, Puck marks your account and associated project data for removal. While active project assets stored within your own repositories remain under your control, Puck purges the internal registry entries and metadata associated with your workspace.

• Workspace configuration and naming conventions
• Authentication tokens linked to Puck dashboard access
• Audit logs of changes made via the visual editor
• Personal user profile information stored on Puck servers

Puck typically retains system-level logs for security purposes, though personal identifiers are removed from the production database upon request. Note that any static content already deployed to your production servers via Puck remains live, as Puck acts as an editor and not a hosting provider.

Privacy considerations

Puck functions as a tool that integrates deeply into your React environment, meaning it may have visibility into your component structures and property types. If you are concerned about your development workflow being tracked or your private component structures being surfaced in analytics, removing your account is a critical privacy step.

• Ensure you audit your codebase for any residual Puck dependencies after deletion.
• Revoke any OAuth permissions or API keys associated with Puck in your GitHub or cloud provider settings.
• Review your environment variables to ensure no Puck-specific configurations remain active.

Frequently Asked Questions

Does deleting my Puck account remove my actual website code?

No, Puck is a visual editor; deleting your account removes your access to the Puck dashboard and workspace, but it does not delete the code in your own repository.

Will my React components break after I delete my Puck account?

Your components will continue to function, but you will lose the ability to edit them via the Puck drag-and-drop interface.

Is the deletion process reversible?

No, once you verify the account deletion via email, the process is permanent and all associated workspace data is purged.

Do I need to remove Puck packages from my project before deleting the account?

While not strictly required for account deletion, it is best practice to uninstall Puck packages to ensure your project remains clean and free of unnecessary dependencies.

Can I export my data before deleting my Puck account?

Yes, ensure you manually copy any custom configurations or JSON layouts from your dashboard settings before initiating the permanent deletion.

How long does it take for Puck to purge my data?

Most data is purged from the production database immediately upon the final email verification, though backups may take a short period to cycle out.