From 72db4892dd056a4bc1f1365ef7b89effcdc14013 Mon Sep 17 00:00:00 2001 From: Dmitry Maranik Date: Sun, 7 Jun 2026 22:55:08 -0700 Subject: [PATCH] docs(data-deletion): note trace deletion does not remove personal data in prompts/datasets Clarify on the Data Deletion page that deleting traces (including a user's traces by userId for a data subject request) removes the traces and their observations/scores, but not personal data that may also live in prompts or datasets - delete those objects as well, or delete the whole project, for complete erasure. Surfaced while verifying GDPR erasure on a self-hosted Langfuse with Sectum AI; AI-assisted contribution. Signed-off-by: Dmitry Maranik --- content/docs/administration/data-deletion.mdx | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/content/docs/administration/data-deletion.mdx b/content/docs/administration/data-deletion.mdx index e1c8d572d6..2e2f7b048a 100644 --- a/content/docs/administration/data-deletion.mdx +++ b/content/docs/administration/data-deletion.mdx @@ -24,6 +24,14 @@ Below, we will walk through each of the options and their guarantees. Note that all trace deletions will delete related entities like scores and observations across all data storages. + + Trace deletion (e.g. deleting a user's traces by `userId` for a data subject + request) removes the traces and their related observations and scores. It does + **not** remove personal data that may also be stored in other objects, such as + prompts or datasets. To erase a user's data completely, delete those objects as + well, or [delete the entire project](#deleting-a-project). + + ### Single Trace