Every year we look at quite a few companies, this is the first year that I've spotted a DPO in the wild, and impressively, they even knew their stuff.
https://www.eugdpr.org/key-changes.html
Maybe his company doesn't need one. Of course, whether he has a DPO or not, still the question remains of how to "properly" delete the personal data.
So, in summary: likely the vast majority of the companies affected is only now starting to wake up to the fact that they are affected, for quite a few of these companies the effects will be relatively benign unless their servers are compromised, for the more serious offender and the larger companies that have not yet started to address these issues it is likely too late to get anything done in time but since this goes for the vast majority of them they are simply playing a complicated game of Russian roulette with the oversight bodies and a couple of them will undoubtedly get lucky to great relief of the remainder.
Data protection authorities tend to be vastly understaffed, but this too will hopefully change in the future.
It would be interesting to know whether the big companies have addressed (at least partially) their GDPR compliance. Maybe they do just "play Russian roulette" like you said, and hope for the best.. Of course, implementation guidelines are not yet fully defined (like WP29 opinions, some of them will change, even then, those opinions are not legally binding).
Note that my sample is relatively small and mostly western European countries (nl, be, de, uk).
I've seen one in all of 2017 (out of ~20 companies).
> Is it an internal or external person?
In that case it was internal
> How technical are they?
More legal than technical, but that's a very small sample.
> I'm a developer and I have a law degree; would that put me in an advantageous position to become one?
Yes. In fact that's probably one of the most lucrative combinations of fields.
> Is there a market for 'consulting DPO's', like companies hire accountants, if that's allowed?
YES! In fact if you are halfway decent this would be an extremely lucrative thing to do, but it probably will become less so over time as the knowledge gets diffused.
1) It was not their main role
2) It was a token gesture, someone to address post too!
Every consulting firm I know is trying to sell GDPR services atm...
GDPR says you must delete information about the customer; but there are cases where you still might need to have that data available.
If your customer can interact with another one inside your app/platform, he/she can commit a crime, and you might be required by court (and by law) to disclose some information (even conversations! inside the platform).
Setting something to "deleted" might not be the best way to do the actual soft delete.
Sometimes you can "delete" that user moving it to a separate part of an LDAP branch (where nobody except someone with authority can access).
In other cases, you can add the "deleted" flag on the table. If so, MAKE SURE your app access the data from a view of the table where the 'deleted' users are not present. Even better: partition the underlying table based on the "deleted" field to physically separate active and deleted users.
But whatever you do, ask your Data Protection Officer first.