Keep data as long as required, not automatically longer.
Retention and deletion depend on purpose, service, legal requirements and the specific contractual agreement. HTS Europa therefore does not publish one technical retention period for every service.
The data lifecycle follows the actual purpose.
Engagement- and service-specific details are defined in the relevant contractual context.
Data minimisation
Only data required for the agreed purpose should be processed.
Engagement-specific periods
Retention or return periods are defined according to the service and processing.
Return or deletion
After processing on behalf of the customer ends, customer data is returned or deleted according to the agreed and legal requirements.
Legal retention
Legal retention duties remain unaffected; any continued processing remains limited to the required purpose.
Public pages do not expose operational parameters.
Backups or technically necessary copies can be subject to specific constraints. These are handled in the appropriate contractual and evidentiary context rather than by publishing operational details.
No universal period
Different services involve different purposes and data types, so a single public period would be misleading.
No operational detail
Internal backup cycles, storage locations, deletion mechanisms or system architecture are not published.
The period or return/deletion process relevant to an engagement belongs in the engagement-specific documentation.
More public information
The overview brings together information about data processing, TOMs, subprocessors, retention and deletion.