Retention
Set retention per project, not per organisation. This lets a strict workload minimise stored content while an inbound workflow keeps the information it needs.
Content and metadata
For minimal-content workflows, Boundry processes the message inside its selected region, sends it or delivers a webhook, then retains only the project’s chosen metadata. Delivery metadata is useful for observability; email body retention is a separate decision.
Choose by workload
Receipts and notifications Short-lived body retention is usually enough for debugging delivery issues.
Inbound support workflows Keep content long enough for your application to process and retrieve conversations.
Strict data boundaries Retain only metadata required for delivery status and operational troubleshooting.
Keep projects separate
Retention is deliberately attached to the project. A high-retention support project and a minimal-retention notification project can live in the same organisation without sharing message data or settings.