I hate digital guardian with a passion, so good luck. As for why it's being reinstalled my bet is that you have a policy that's doing that from an unexpected place - like a task for new builds, etc. When I've seen this in the past, what has normally been caused from having membership in a Jamf group that I didn't realize. I'd start by looking at the inventory for the specific workstation, check the management tab, and then scroll down to computer groups. Look for anomalies. Also double check your policies using the search box. It should be able to filter out the packages I think and hopefully identify whatever policy is running a DG install. There could also be some sort of self-healing logic locally installed. When I managed a fleet running DG, there was some talk of a LaunchDaemon to install DG when dg wasn't running by having the installer package saved locally. Your installer may be saved locally - check in places like
/Library/Application Support/Your Org
to see if anyone has a directory they throw frequently used things. Just a few things to try.
