Retention and Storage

On each plan, there is a maximum total storage allowed for all inbox items across all projects. When this limit is reached, the behaviour depends on your plan and settings, but generally involves either rejecting new items or automatically deleting old items to make room for new ones.

This includes message size, attachments and all metadata. The total storage used is the sum of the sizes of all inbox items across all projects in the organisation.

Retention time

The maximum retention period is the maximum amount of time that inbox items are kept before they are automatically deleted. This ensures that items do not stay in the system indefinitely, and helps you comply with data retention policies.

On lower plans this is a fixed period that applies to all items, while on higher plans you can set custom retention periods globally or per project.

Note that retention time is different from storage limits. Retention time determines how long items are kept before they are automatically deleted, while storage limits determine how much total data can be stored across all items. Even if your retention time allows items to be kept for a long period, you may still run into storage limits if you have a large number of items or large attachments.

Custom retention periods

Set custom retention periods to match your project and compliance needs. Higher plans allow setting this both globally and per project.

With customizable retention, you can set different retention periods for different projects. This allows you to keep items in some projects for a longer time while automatically deleting items in other projects sooner, based on your specific needs and data policies.

The retention period can be set to any value from 1 minute up to the maximum allowed retention time for your plan.

Ingestion policy

When FIFO (First In, First Out) is enabled, storage pressure removes the oldest inbox items first to accept newer items. This can be disabled on higher plans to reject new items instead of deleting old ones.

Note that this applies organisation wide. E.g. if you have multiple projects, the oldest items across all projects will be deleted first when storage pressure is applied.

If your plan does not include this feature, the default behaviour is to reject new items when storage limits are reached, without deleting old items.

Automatic deletion configuration

This setting can be set on the organisation level to control the behaviour when storage limits are reached. The options are:

• Delete oldest (FIFO): When storage limits are reached, the oldest inbox item(s) are automatically deleted to make room for new items. Note that an ingestion of a single item might delete multiple old items if they collectively exceed the storage limit.
• Reject: When storage limits are reached, new items are rejected and not ingested, while existing items are kept until they reach their retention period.

Pinned items

Items that you have pinned are exempt from automatic deletion. They are not deleted when their retention period expires, and they are not deleted by the FIFO storage policy. However, if your storage limit is reached and you only have pinned items left, your inbox will reject new items until you unpin or delete items.