Your paragraph Rubrik relates to very serious breaches and there is no question that if the incident is serious enough the data should be de-identified. In Ezy however any ASR will de-identify the data even if unrelated and this means that even though you may file an ASR for a TCAS event you may end up having to explain why you did not descend at econ speed later on in the flight. In practical terms this means that for most folk (ie most of us that would file ASR when needed and not only in extreme cases) the data is not protected. You may be surprised to hear that some people even file an ASR for very minor excedances (Vref +12 at 500´ on a turbulent day and after a fully stable approach from 1000´).
A different issue that comes up in your post is who manages the system. In Ezy we have a couple of young FO´s as well as a number of captains. While I am sure they are very bright and able pilots I feel that this is a job where some extra experience will be quite beneficial.