"7. Right to Terminate or Modify Software
LinkedIn may modify the Software and this EULA with notice to you either in email or by publishing notice on the Website, including but not limited to charging fees for the Software, or changing the functionality or appearance of the Software. In the event LinkedIn modifies the Software or the EULA, you may terminate this EULA and cease use of the Software. LinkedIn may terminate your use of the Software, the EULA or the LinkedIn Service at any time, *with or without notice.*" (emphasis mine)[0]
Fundamentally, I cannot ever trust them. Because we proactively separate a member’s submission data from their
Member ID when compensation data is submitted, it enables us to
secure the system in such a way that we cannot even support the
ability for a member to update their previously submitted salary
information - they have to resubmit.
How is this possible? If the salary data is not associated to the user in any way can't a user submit their salary over and over again drastically swaying the aggregate salaries?1. You submit a salary info struct, which includes time of submission. The struct does not contain a userId.
2. Your account's lastUpdatedSalaryDate gets updated, with only day/week/month level precision.
Someone with access to the entire database may be able to connect the two if the salary set for your job is small enough.
Then they weigh salary information based on how fresh the entry is. Stale entries don't get a good weight, and you updating your salary is just another info point, and it might go into another bucket if you got a title change (ex software eng -> sr. software eng.). If you got promoted, then the old salary info is probably still relevant for people in lower level positions.
Both should be in the data.
NO.