Apparently there is no official way to remove the serverlog data of completed process instances, but the system saves the name and FQN of the originator of any process in those tables. So basically this means K2 is not GPDR compliant which is quite astonishing. Only archiving would be possible, but we do not want to archive - we HAVE to delete. There is a stored procedure in the system database to remove serverlog entries by process ID, but it's not allowed to use it. The request is to make this function officially available as a SMO so we can create data deletion processes because there are different retention policies per application.