GDPR Deletion

This page describes how Entropy Data handles the deletion of personal data when a user is removed, which data is removed, which data is retained for audit purposes, and how this maps to the requirements of a GDPR deletion concept.

Scope of Deletion

When an organization owner deletes a user, the user record and the user's organization and team memberships are removed. There is no full cascading deletion that strips personal data from all downstream tables, because historical information is required for traceability.

What is deleted

  • The user record (only if the user is no longer a member of any other organization)
  • All organization and team memberships of the user
  • Git credentials and data source connections owned by the user

What is retained

  • Audit fields (created_by, updated_by) on all audit-trail tables
  • Activity history in Events (the principal field contains the user ID or email address)

SCIM Deprovisioning

SCIM deprovisioning via DELETE /api/scim/v2/Users/{userId} behaves the same way as an admin deletion. The user is removed from the organization and, once the user is no longer a member of any other organization, the user record itself is deleted. Audit and activity data remain in place.

References:

Self-Service Deletion

There is currently no self-service option for users to delete their own profile. In enterprise deployments, user lifecycle is typically handled via SCIM or by organization administrators.