Retention policy limits and data export behavior with eDiscovery holds

Goal is to understand plan-dependent limits for message history accessibility and file upload capability, and how retention policy behavior interacts with compliance features.

Slack documentation describes varying message history windows by plan and plan-dependent file upload limits. Paid plans can configure retention policies to automatically delete messages and files after a set period, with separate settings for channels and direct messages.

The precise interaction between an active retention deletion, eDiscovery holds, and availability of data via admin data export is not consistently clarified.

Specific questions:

• Is content subject to an active retention policy excluded from admin data exports once deletion is scheduled?
• Does an eDiscovery hold prevent retention-based deletion for messages and files?
• Are retention limits applied uniformly to channel messages and direct messages for export and hold purposes?