They can choose disclose it. I will not decide to do so on their behalf.
You might, for example, try asking them, and seeing how many feel that their privacy would be violated by publishing aggregate anonymous salary data. The answer will be 0.
Keep in mind if you have a reasonable belief that all but one of your employees will collaborate to unmask another's salary, they have ample support to form a union and require internal transparency in the contract. Your threat model is illegitimate.
If I publish a names-redacted list of everyone's salary and track/level/job code, or a mean & std-deviation per track/level/job code, I am almost certain to divulge private information of at least one employee. I have spoken with employees on this topic. Publishing their data, even inadvertently (as in the Netflix contest example), does not have anywhere near 100% support.
1. Don't worry about that failure mode. There will always be ways for collusion among employees to gain salary information.
2. Publish the methodology by which compensation is calculated. That is, it is presumably some combination of algorithm based on location and role, performance, and discretion. Make the calculation methodology transparent (internally). This will also set a range you can publish externally.
This allows people to ask informed questions ("why is my perceived performance not being rewarded") instead of being completely baffled by numberwang. Transparency about the process and forces the company to do better, which is a good thing.