Request: Log retention on workspace level

[MegaMinxCoding]

Summary:
Introduce a log retention mechanism that allows each workspace to define how long logs (e.g., email delivery, event, and user activity logs) are stored before automatic deletion.

Background / Current Behavior:
Currently, the system stores all logs indefinitely. This can lead to increased storage costs, slower query performance, and potential compliance issues for customers who require specific data retention limits (e.g., GDPR or internal data governance policies).

Proposed Solution:

• Implement a log retention policy framework that supports automatic log cleanup after a defined period.
• Allow configuration at the workspace level, so each workspace can specify its own retention_duration (e.g., 30, 90, 180, or 365 days).
• Add a system job to handle periodic deletion of expired logs / go with the cron solution.
• Optionally provide an audit record of purged data for compliance visibility.

Benefits:

• Prevents unbounded log growth and reduces storage costs.
• Improves system performance and manageability.
• Enables compliance with diverse data retention and privacy requirements.
• Offers flexibility for multi-tenant environments.

[pierre-b]

Thanks for the request, I still need to think of the implications... if we just purge events (messages, webhooks) or contacts too.
If we purge contacts we need to define what is an inactive contact?!

[MegaMinxCoding]

Good thought about the contacts. I would rather say that contacts should not be deleted automatically. If you can implement a multi select on the contact table view with a delete button this should be enough. Maybe you provide the option to sort the list based on lastUsedTimestamp. so you can do this manually.

[pierre-b]

Quick update on this: it's fine to get at least a year of history to see seasonal trends so I'll plan this feature mid-2026.

[MegaMinxCoding]

Absolutley fine! Thx in advance..