Discussion about this post

User's avatar
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
Lyra's avatar

I agree on your main point -- I'm no great fan of the GDPR & its idiot clicking nightmare, but I do care about privacy (as do many people I know) and take steps to minimize tracking, and I work in this field. So please forgive my "akshully" here, but for the record, "incognito mode" merely grants you privacy from your spouse (or anyone else who shares access to your computer) -- only local data is deleted, so it does exactly nothing to prevent you from being tracked online by the wider internet powers that be.

Expand full comment
34 more comments...

No posts