Currently, the contact offlining rules are very basic and only seem to use opt-in date as a criteria. Whilst this is useful for Transact and databases where not contact history is needed, it's often not suitable.

I would love to see configurable data retention rules where customers can craft their own logic as to when their data would be offlined, using database fields, behaviours and relational table fields in a manner similar to the query builder.

This would assist those operating with European data where they are obliged under GDPR to not hold data longer than required and thus, this would be feature they could leverage when they define what their retention rules are.