If I had to guess it probably has to do with how Chrome updates itself, which is likely causing the OS to see it as a new binary that hasn’t had permissions set

If I had to guess it probably has to do with how Chrome updates itself, which is likely causing the OS to see it as a new binary that hasn’t had permissions set after each update.