Data Protection Regimes have been enhanced to support conditional retention durations. This allows for dynamic retention period calculation, such as having a longer retention period for the Norway Jurisdiction when the entity has a High Risk Rating. Where no conditional rules are configured (or none are matched), the regime’s default retention duration continues to apply.
When an entity undergoes partial data deletion, the data for an offboarded jurisdiction is deleted, having reached the end of it's retention period. With this deletion, related products may also be selected to delete. When using Dynamic Access Layers, if the deleted data was an input to the Entity's Access Layers, they will now be re-evaluated based on the remaining data.
This release introduces Automatic Client Re-onboarding, an enhancement that simplifies bringing previously offboarded jurisdictions back into scope.
When the Automatic Re-onboarding Toggle is disabled, re-onboarding continues to require users to explicitly select the jurisdictions they intend to re-onboard on the Journey Launchpad; only selected jurisdictions return to scope. To make this clearer, the Re-onboarding Journey Hub now displays messaging when scoping criteria are met for a jurisdiction that was not selected for re-onboarding.
When the Automatic Reonboarding Toggle is enabled, partially offboarded jurisdictions automatically return to scope once their trigger conditions are met again, while fully offboarded jurisdictions still require a Re-onboarding Journey to reapply the client chip and re-evaluate policy scoping. Data deletion schedules will be paused while an offboarded jurisdiction is being reonboarded.
This feature enables users to query information related to data retention for offboarded and partially offboarded entities.
The Data Deletion feature has been enhanced to ensure that entity records with outbound associations (i.e. where the entity is a Related Party to another entity) are not fully deleted. Instead, Client-specific data and documents are removed, while Related Party information is preserved. This ensures compliance with data protection regulations while maintaining critical relationship data.