Disclaimer: I'm a fan of anonymisation because I'm working on a project to bundle this in to a service - https://anon.ai - would be great to understand more about your use case.
Ask HN: How are you implementing GDPR-compliant soft deletes?
31–40 of 86 posts
Re: Ask HN: How are you implementing GDPR-compliant soft deletes?
#32What would be the sort of dispute you envisage?
Government: "You know that data you were required to delete when $(USER) requested to be forgotten? We require you to provide it in connection with our ongoing investigation of $(USER)."
Re: Ask HN: How are you implementing GDPR-compliant soft deletes?
#33Consult your Data Protection Officer first. 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 "…
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.
Re: Ask HN: How are you implementing GDPR-compliant soft deletes?
#34Deletion of backup-data is also an interesting topic
Re: Ask HN: How are you implementing GDPR-compliant soft deletes?
#35Deletion of backup-data is also an interesting topic
I won't touch my backups even if it means my company is killed by fines or I go to jail. Still worth it just to refuse submitting to this nonsense.
Re: Ask HN: How are you implementing GDPR-compliant soft deletes?
#36Re: Ask HN: How are you implementing GDPR-compliant soft deletes?
#37What would be the sort of dispute you envisage?
Re: Ask HN: How are you implementing GDPR-compliant soft deletes?
#38About the GDPR, can anyone recommend a company in the UK they have dealt with, that brought them up to compliance?
Re: Ask HN: How are you implementing GDPR-compliant soft deletes?
#39Earlier quoted context omitted.
My understanding, as someone implementing the GDPR-compliance for my company right now, is that if you could produce the same one-way hash a second time from the same input email address then the hash is still considered PI.
Do you know how you are supposed to handle disputes in the future? If I ask that all my information be deleted and I say n months later I was charged for something I never received, how does the company disprove that?
Re: Ask HN: How are you implementing GDPR-compliant soft deletes?
#40> it helps for documentation purpose should the dispute arise over some issue in future. If you are required to hold on to the data for legal purposes such as dispute settlement, there is no issue. The customer can request you delete such data but you have no obligation to do so. Issues arise when holding on to the data is no longer "necessary". At that point soft deletion is not enough and you must be able to remove…
Are you sure about throwing away encryption keys is sufficient to be GDPR complient? Does this comes from IP lawyer as well?