Skip to main content
20 events
when toggle format what by license comment
Jun 26, 2018 at 4:48 history closed Bernhard Barker
gnat
OldPadawan
Neo
Bluebird
Not suitable for this site
Jun 25, 2018 at 15:53 comment added Kyle Wardle My answer about anonymous data still applies however from what you are saying , @Horkrine , if the data is being stored for a period of time on another database whilst not anonymous until someone actually runs a function to anonymous, this could be getting into a grey area with GDPR as if the database is hacked during a time when there is non anonymous data, that is personally identifiable data which you should not have. I would IMO create an automated function which runs after the initial deletion and migration. Then at least you are covered. Otherwise I would tread carefully.
Jun 25, 2018 at 15:00 vote accept Horkrine
Jun 25, 2018 at 15:00 comment added Horkrine @Dan Thats exactly my point - it is the entire user being exported from a record in System A's database, into an XML file, and then imported into System B later where a manual anonymise function must be ran. It just doesn't seem right, but the answers so far tell me it's compliant which is what I was looking for :)
Jun 25, 2018 at 14:45 comment added Dan Maybe calling it an "export" is the wrong part. He should say, "When a user is deleted from the database, it fires a trigger to insert the anonymised user's religion into a counter table before deleting. This data cannot be tied back to a user and purely informational." That sounds better than saying, "a user is exported..." because then it implies being tied back to users.
Jun 25, 2018 at 12:38 comment added speciesUnknown This is 100% not a GDPR violation as you are under legal obligation to keep the data.
Jun 25, 2018 at 12:34 history edited David K
edited tags
Jun 25, 2018 at 12:18 history edited David K CC BY-SA 4.0
edited title
Jun 25, 2018 at 11:29 comment added pmf The GDPR might actually conflict with other regulatory requirements in some cases.
Jun 25, 2018 at 11:06 answer added Kyle Wardle timeline score: 13
Jun 25, 2018 at 6:53 comment added amar Anonymised data is GDPR compliant and can be used for statistical analysis.
Jun 25, 2018 at 6:07 comment added Shaeldon Regarding your concerns: "where they can be anonymised" is all that matters. As long as I can't link the Information I have to a person GDPR is satisfied. Name/Surname/Birthday/Email have to go. After that you are fine.
Jun 25, 2018 at 2:38 comment added aem I am not a lawyer, but gdpr-info.eu/art-17-gdpr seems to say that deleting a user's data is not required if processing that data is needed "for compliance with a legal obligation which requires processing by Union or Member State law to which the controller is subject". That suggests to me if the count of people by religion is required by some law the customer is subject to, then it is allowed to retain that data.
Jun 24, 2018 at 22:44 review Close votes
Jun 26, 2018 at 4:48
Jun 24, 2018 at 22:44 comment added Bernhard Barker See: My boss wants me to do something that might be illegal
Jun 24, 2018 at 22:34 answer added Neuromancer timeline score: -2
Jun 24, 2018 at 22:22 history edited Horkrine CC BY-SA 4.0
added 49 characters in body; edited tags
Jun 24, 2018 at 22:13 answer added gnasher729 timeline score: -2
Jun 24, 2018 at 21:49 comment added Neuromancer Are you from NI ? if so you may not know there are strict laws about equal treatment of both traditions not being able to prove that you treat Catholics and Protestants the same can get you into serious trouble and not just with the law
Jun 24, 2018 at 21:30 history asked Horkrine CC BY-SA 4.0