4 ms·
"Companies cannot just include external software into their products and then hope that they comply with the law. Grindr included the tracking code of external
by user-the-name 6y ago
"Companies cannot just include external software into their products and then hope that they comply with the law. Grindr included the tracking code of external partners and forwarded user data to potentially hundreds of third parties - it now also has to ensure that these 'partners' comply with the law." – Ala Krinickytė, Data protection lawyer at noyb
This has a pretty wide impact, I'd say.
- SiempreViernes 6y agoThe impact comes from Grindr being responsible for the collected data, obviously just handing that data to a third party to do whatever is not responsible handling of it. Grindr actually distributed data from persons that had opted-out, reasoning that setting a flag should stop the down-stream processors from touching the data. That is literally the gossip girl using the the "don't tell anyone this" principle of privacy protection!
- user-the-name 6y agoThe thing is, third-party SDKs often do data collection on their own. Or, even if they don't, they could do so, and you don't really know if they do or not.
- speedgoose 6y agoYes Facebook's SDK is unfortunately very common for example. But Grindr and applications developers in general are responsible for the data. They have to know and have a data policy with their third parties.
- SiempreViernes 6y agoWell, now the GDPR gives you 10% of your revenue as a reason for not using SDKs that will not give you control of data collection. You always had "respect the privacy of users" as a reason not to use them before, but we all know how well that worked.
- user-the-name 6y agoThe problem here is that if you want to implement Facebook login in your app, you have to include the SDK. It is against ToS to do it any other way.
- etripe 6y agoWell, if that SDK contains tracking stuff, the question then becomes whether the SDK has an opt-out option. If yes, it's on the consumer of the SDK. If not, then whether the TOS is enforceable in Europe.
- SiempreViernes 6y agoSeems like the specific problem there is Facebook enticing you to break the law. You could try filing a complain with some appropriate data protection agency.
- TeMPOraL 6y agoThen don't implement Facebook login in your app, unless SDK becomes adapted to make its use GDPR-compliant. It's really a problem between you and Facebook at this point.
- anticristi 6y agoThis. The whole point of Facebook login and like was to collect data from unsuspecting users. Devs and product managers didn't care. GDPR makes this "laisser faire" attitude expensive.
- anticristi 6y ago"We value your privacy" has never been truer.