Data Deletion and GDPR Considerations
Witzo enables deletion of knowledge sources, chats, and key resources, while GDPR compliance depends on operational and legal processes.
Overview
Data removal is supported at resource level. Full regulatory compliance requires policy, documentation, and workflow controls outside the application.
Deleting Data Sources
You can delete:
| Item |
|---|
| Website URLs |
| Individual scraped pages |
| Uploaded documents |
Deletion removes indexed content and prevents it from being used in future responses.
Deleting Chats
Chat records and session data can be removed through backend resource deletion endpoints. Deletion removes:
| Item |
|---|
| Conversation history |
| Associated summaries |
| Lead-linked chat references |
Plan-based history limits affect visibility, not underlying storage logic.
Account Deletion Workflow
A complete self-serve account deletion flow is not fully productized in the current repository. For full account purge, a cascading deletion workflow should include:
| Step |
|---|
| User account removal |
| Widget removal |
| Knowledge cleanup |
| Leads deletion |
| Conversation cleanup |
| Session cleanup |
GDPR Compliance Considerations
GDPR compliance requires:
| Requirement |
|---|
| Legal basis for processing |
| Data retention policy |
| Data Processing Agreement (DPA) |
| Data access requests handling |
| Deletion request audit logs |
Application-level deletion alone does not equal GDPR compliance.
Compliance depends on: