Mintplex-Labs/anythingllm-docs
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anythingllm-docs.git synced 2026-07-21 01:05:22 -04:00
Code Issues 16 Packages Projects Releases Wiki Activity

[PR #259] [MERGED] docs(privacy): clarify document deletion vs workspace removal for full erasure #239

New Issue
Closed
opened 2026-06-05 15:22:47 -04:00 by yindo · 0 comments
yindo commented 2026-06-05 15:22:47 -04:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/Mintplex-Labs/anythingllm-docs/pull/259
Author: @dmitrymaranik
Created: 6/5/2026
Status: ✅ Merged
Merged: 6/6/2026
Merged by: @timothycarambat

Base: main ← Head: docs-document-erasure

📝 Commits (1)

  • 5a251c1 docs(privacy): clarify document deletion vs workspace removal for full erasure

📊 Changes

1 file changed (+17 additions, -0 deletions)

View changed files

📝 pages/features/privacy-and-data-handling.mdx (+17 -0)

📄 Description

What

Adds a short "Deleting documents and full erasure" section to the Privacy & Data page.

Why

The distinction between removing a document from a workspace and deleting it from My Documents isn't documented anywhere, and it matters for data-deletion / right-to-erasure requests:

  • Remove from a workspace (Document.removeDocuments) deletes that workspace's vectors but keeps the parsed source file and cached embeddings in the document library (intentional, for reuse).
  • Delete from My Documents (purgeDocument) is the full erasure path — it calls purgeSourceDocument + purgeVectorCache and removes the document from every workspace.

An operator fulfilling a GDPR/DSR erasure request who only removes a document from a workspace would leave the parsed text and vector cache on disk. This documents the correct path. No behavior change — docs only.

Disclosure

Surfaced while testing a self-hosted instance with an automated multi-tenant-isolation checker (Sectum AI); drafted with AI assistance.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/Mintplex-Labs/anythingllm-docs/pull/259 **Author:** [@dmitrymaranik](https://github.com/dmitrymaranik) **Created:** 6/5/2026 **Status:** ✅ Merged **Merged:** 6/6/2026 **Merged by:** [@timothycarambat](https://github.com/timothycarambat) **Base:** `main` ← **Head:** `docs-document-erasure` --- ### 📝 Commits (1) - [`5a251c1`](https://github.com/Mintplex-Labs/anythingllm-docs/commit/5a251c1f65ba0ed2030a90185688c3533fd86ec5) docs(privacy): clarify document deletion vs workspace removal for full erasure ### 📊 Changes **1 file changed** (+17 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `pages/features/privacy-and-data-handling.mdx` (+17 -0) </details> ### 📄 Description ### What Adds a short **"Deleting documents and full erasure"** section to the Privacy & Data page. ### Why The distinction between *removing a document from a workspace* and *deleting it from My Documents* isn't documented anywhere, and it matters for data-deletion / right-to-erasure requests: - **Remove from a workspace** (`Document.removeDocuments`) deletes that workspace's vectors but **keeps** the parsed source file and cached embeddings in the document library (intentional, for reuse). - **Delete from My Documents** (`purgeDocument`) is the full erasure path — it calls `purgeSourceDocument` + `purgeVectorCache` and removes the document from every workspace. An operator fulfilling a GDPR/DSR erasure request who only removes a document from a workspace would leave the parsed text and vector cache on disk. This documents the correct path. No behavior change — docs only. ### Disclosure Surfaced while testing a self-hosted instance with an automated multi-tenant-isolation checker ([Sectum AI](https://github.com/sectum-ai/sectum-ai)); drafted with AI assistance. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-06-05 15:22:47 -04:00
yindo changed title from [PR #259] docs(privacy): clarify document deletion vs workspace removal for full erasure to [PR #259] [MERGED] docs(privacy): clarify document deletion vs workspace removal for full erasure 2026-06-07 16:46:45 -04:00
yindo closed this issue 2026-06-07 16:46:45 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
enhancement
good first issue
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anythingllm-docs#239
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?