4 ms·
That's a bit of a stretch. Any large organisation would already have a central database of employee names and job titles that are accessible to everyone within
by hnlmorg 6y ago
That's a bit of a stretch. Any large organisation would already have a central database of employee names and job titles that are accessible to everyone within the organisation. That data is available to anyone who looks up an email addresses, let alone any web based services such as Sharepoint. Many businesses even advertise their team publicly as part of their marketing,
I can't see court in the EU ruling in favour of the employee on this specific topic.
More likely the GDPR notice is to remind people about customer data. Which is fine, that's the right thing for Tara to do. However any company using a Tara-like solution for putting customer data on would be in the wrong. That sort of practice would have failed PCI DSS even before GDPR was a thing.
- robertlagrant 6y agoNo. I'm saying that Tara would have access to both my employer name and my name if they had my work email address as a login. That's nothing to do with my employer having my name.
- hnlmorg 6y agoYes, I got that point and you're missing mine: employer databases are seldom treated as confidential. - You can ring the employer up and receptionists will readily hand this information over - Many companies host AD off site - Business cards It trivial to find the names of people who work in a team because it's leaked everywhere and for everything. I guess maybe, just maybe, if you happened to work in a sensitive industry (eg secret services) then there might be a claim here, but no such organisation would host that kind of development content off site in the first place. So it's a moot argument. The reason Tara publish their GDPR statement is very clearly regarding customer data. Arguing about names and email addresses of customer facing project managers massively misses the point of what GDPR exists for.
- robertlagrant 6y agoAll of your examples are for someone's own employer. I'm not talking about people who work for Tara. I'm talking about their customers.
- hnlmorg 6y agoI'm not talking about people working for Tara -- I was only ever talking from the perspective of Tara's customers!!!! The GDPR message is there to stop Tara customers from putting other customers data in there. Like if I'm a customer of Tara and I provide services to you then you are my customer (not Tara's nor an employee of Tara). The GDPR is to tell me not to put your details in there. It's not there to warn me about my own email address being pseudo-public. The reason this needs to be explicit is because sometimes some organisations will put their own customer data into their support system. While this is generally bad practice it can be excused depending on the type of support system it is and how it's hosted. But the type of system Tara is aimed for, it's not intended to be a customer issue tracker ("customer" here meaning "customers of the people who use Tara" -- not Tara's employees nor Tara's direct customers) and Tara are making that point explicit with their GDPR statement.
- robertlagrant 6y ago> I'm not talking about people working for Tara -- I was only ever talking from the perspective of Tara's customers!!!! Sure, in your own comment thread that might make sense :-) I don't see why you think customer data is less worthy of GDPR than customers of customer data.