How to delete your PayloadCMS account

About deleting your PayloadCMS account

PayloadCMS is a headless CMS and application framework built on Node.js and TypeScript, designed to give developers total control over their data structures and admin UI. Payload Cloud provides hosting and managed infrastructure for these instances, handling environment variables, database backups, and media storage for deployed projects.

Users may choose to delete their Payload Cloud account for various reasons. Perhaps you have migrated your self-hosted instance to a different cloud provider, consolidated your development workflow, or are decommissioning a legacy project that no longer requires managed hosting services. Deleting your account ensures you are no longer billed for active slots and prevents your administrative credentials from remaining accessible in the cloud dashboard.

• Streamlining infrastructure costs by removing inactive project slots.
• Migrating from Payload Cloud back to a self-hosted environment using Docker or Node.js.
• Ensuring compliance with internal data governance policies by purging development credentials.
• Minimizing the attack surface by reducing the number of external platforms holding your admin login data.

What happens to your data

When you trigger a deletion request through the Payload Cloud dashboard, the service initiates a cleanup process for the account-level metadata. Because PayloadCMS emphasizes developer sovereignty, deleting the account focuses on the Cloud management layer rather than your actual database content stored within your private project databases unless those databases are hosted within the Payload Cloud ecosystem. Types of data handled by Payload Cloud include:

• Authentication tokens and profile information associated with your GitHub or Email login.
• Environment variables and secret keys configured within the Payload Cloud dashboard.
• Billing history, payment method tokens, and subscription invoices generated by the platform.
• Deployment logs and build history metadata stored for debugging your headless CMS applications.

Privacy considerations

Using Payload Cloud involves trusting the provider with your deployment configurations and access to your repositories. While PayloadCMS is open-source and transparent regarding its core framework, the cloud-managed service acts as a custodian of your configuration data. To maintain high privacy standards when using PayloadCMS, consider these practices:

• Regularly rotate your MongoDB or PostgreSQL connection strings if you suspect a breach.
• Use environment variables for sensitive API keys rather than hardcoding them into your schema files.
• Audit your team members' permissions within the Payload admin panel to ensure the principle of least privilege.
• Download all project assets and database dumps before initiating an account deletion to avoid permanent data loss.

Frequently Asked Questions

Does deleting my Payload Cloud account delete my local codebase?

No, deleting your Payload Cloud account only removes your cloud-hosted environment and associated cloud dashboard profile. Your local repository, codebase, and database files remain untouched on your machine.

Will deleting my account stop my recurring billing?

Yes, closing your account and removing your associated cloud projects cancels your active subscriptions, preventing further charges for the next billing cycle.

Can I recover my Payload Cloud account after deletion?

Account deletion is typically permanent. Once you confirm the deletion in the dashboard, the association between your GitHub identity and the cloud management portal is severed, and associated metadata is purged.

Does PayloadCMS store my actual content data in their cloud?

If you are using Payload Cloud to host your database, your content data is stored there. If you use a remote database like MongoDB Atlas or Neon, Payload Cloud only stores the credentials to connect to those services.

Are my repository webhooks removed upon deletion?

Yes, initiating account deletion removes the cloud-side management of your deployments, which includes the removal of active webhooks that Payload Cloud maintained to trigger builds on your commits.

Is the open-source PayloadCMS framework affected by my cloud account status?

The open-source framework is independent of the cloud service. You can continue to run and develop your PayloadCMS projects locally even without a Payload Cloud account.