Discussion about this post

User's avatar
Richard Gadsden's avatar

Personally, I am that sort of privacy maven. I do find the "reject all" button for cookies; I use multiple plug-ins to block all of this stuff. And I don't think that personalised advertising is a fair trade for free things on the internet. As far as I'm concerned, every person that looks at a piece of content should get the same ad - permanently: when I look at an article from 1999, I should see the pets.com ad that originally ran with it; when I look at articles form 2006, I should see Enron ads, just like when I read a magazine from back then.

But I absolutely understand that I'm in the small minority who think like this.

Expand full comment
Klaus's avatar

Hey, a thing I know about! I worked in a company that had a huge data compliance team, so I can speak to this.

Quick background: "SQL tables" are how programmer and data analysts can access and use data in an intuitive manner. Engineers create "data pipelines" that put data into SQL tables in an efficient and automated manner.

So because of GDPR we couldn't put some Salesforce (customer relations) data into SQL tables without some long approval process from the compliance team. For what it's worse, I could easily download this Salesforce data, attach it to an email, and send it to literally anyone. In other words, keeping the data out of SQL tables secured no one, but GDPR applies to the SQL tables and not Salesforce itself for reasons.

So keeping the data out of SQL tables was pointless... but we didn't keep the data out of SQL. We needed the data for our jobs, so multiple teams would just say fuck it and manually upload the data to SQL tables. Until my last day, I was manually uploading this data while waiting for compliance to approve a data pipelines.

Basically, GDPR created extra compliance processes to allow people to do what they were doing anyway, and the data could have been attached to an email and sent out anyway.

Expand full comment
36 more comments...

No posts