How to delete your Prisma Data Platform account

About deleting your Prisma Data Platform account

Prisma Data Platform (PDP) serves as a cloud-based interface for managing Prisma projects, providing features like data proxying, query monitoring, and collaborative database management. It integrates deeply with GitHub, hosting schemas and providing metrics on database query performance. Users typically interact with the platform to manage deployment environments and connection strings for their Node.js or TypeScript applications.

Deleting your account is a significant step if you are migrating away from Prisma's managed infrastructure or shifting to a self-hosted architecture. Common reasons for account deletion include:

• Consolidating development tools and removing legacy workspace environments.
• Switching from Prisma's cloud proxy services to direct database connections.
• Security requirements to minimize the attack surface by removing unused cloud configurations.
• Project sunsetting where you no longer require the collaborative management features provided by PDP.

What happens to your data

When you delete your Prisma Data Platform account, the platform initiates a process to purge your associated workspace data. This includes your specific project configurations, environment variables, and cached query metrics. Because PDP acts as a bridge between your application and your database, closing your account ensures that your database connection strings stored within the platform are invalidated.

Prisma generally purges the following data types upon account closure:

• Workspace metadata and team member invitations.
• Cached query logs and performance metrics stored on PDP servers.
• Environment variable configurations used for deployment pipelines.
• Authentication tokens and GitHub integration links.

While PDP deletes user-specific metadata, it is important to note that Prisma may retain aggregate system logs for service stability, and any data already persisted within your own private database remains completely untouched by the deletion process, as PDP does not host the database itself.

Privacy considerations

Using Prisma Data Platform involves granting access to your code repositories via GitHub. This is a critical privacy factor, as the platform monitors project activity to provide its dashboard features. If you are highly sensitive to third-party integrations, you may want to ensure you have revoked the Prisma GitHub App permissions from your GitHub settings in addition to deleting your PDP account.

Key privacy tips for PDP users:

• Audit your GitHub App permissions regularly to see what Prisma can access in your repos.
• Use environment variable management tools that encrypt secrets before they are pushed to the platform.
• Regularly rotate your database credentials, especially if you have used them within a shared workspace environment.

Frequently Asked Questions

Will deleting my Prisma Data Platform account break my production database?

No, Prisma Data Platform is an abstraction layer. If you are using the Data Proxy, you will lose the ability to route queries through PDP, but your actual database (e.g., PostgreSQL or MongoDB) remains intact and accessible via standard connection strings.

Does deleting my account remove my code from GitHub?

No, Prisma only integrates with your repositories to track changes and facilitate deployments. Deleting your PDP account does not touch your source code in GitHub.

Can I recover my workspace settings after deletion?

Once the deletion process is confirmed, workspace data, custom metrics, and configuration logs are purged and cannot be recovered by the Prisma support team.

What happens to my team members when I delete the workspace?

All team members invited to your workspace will lose access to the specific environment settings, query metrics, and project dashboards associated with that workspace immediately.

Does Prisma store my database content?

Prisma Data Platform does not host your primary database content. It processes metadata and query performance logs, but your actual application data resides in your own database infrastructure.