Database bloat

Hello,

We are experiencing significant database bloat caused by the Stream Activity Log.

The activity log tables are continuously growing in size, and we cannot find any evidence of automatic cleanup, retention limits, or pruning taking place. Over time, this has resulted in very large tables and unnecessary database load.

We have reviewed the settings and documentation but have not found a clear or reliable mechanism that:

• Automatically removes old log entries
• Enforces a maximum retention period
• Prevents unbounded growth in high-activity environments

For production WordPress sites, especially those running for years, this creates a real maintenance and performance concern. An activity logging system should either manage its own data lifecycle or clearly document how administrators are expected to do so safely.

Could you please clarify:

• Whether Stream includes any automatic cleanup or retention logic
• If so, how it is triggered and what the default behavior is
• If not, what the recommended and supported approach is to prevent database bloat

At the moment, the plugin appears to generate data indefinitely without cleanup, which is not sustainable in long-term use.