Saving a privacy control via ajax with simple privacy enabled wipes out privacy rules
If ajax editing a field with a privacy control and simple privacy is enabled it wipes out stored privacy rules. This appears to be due to the storage behavior trying to look for simple privacy rules instead of individual.
This appears to be due to CB Core Fields Ajax firing a profile update trigger, which is only updating 1 field and thus only has output of 1 privacy rule. This however causes the privacy save behavior to fire for all fields. Field privacy likely needs to be moved to a different trigger that's more field specific.