User contributions for 84.113.103.211

From GDPRhub
For 84.113.103.211 talk block log logs abuse log
Search for contributionsExpandCollapse
⧼contribs-top⧽
⧼contribs-date⧽
(newest | oldest) View ( | ) (20 | 50 | 100 | 250 | 500)

12 September 2023

11 September 2023

7 September 2023

6 September 2023

1 September 2023

30 August 2023

29 August 2023

23 August 2023

22 August 2023

2 August 2023

1 August 2023

31 July 2023

25 July 2023

  • 10:1210:12, 25 July 2023 diff hist −1,267 AEPD (Spain) - EXP202204881The decision was kind of complicated and inconsistent. I've made several changes to the summary to try to put the facts and line of reasoning into a clearer structure, but there are still contradictory points. Overall, the language used in the summary was good and in line with our guidelines. Tag: Visual edit

19 July 2023

18 July 2023

12 July 2023

11 July 2023

  • 14:4114:41, 11 July 2023 diff hist −874 AEPD (Spain) - EXP202206735I made some changes: - determine who is the data subject and who is the controller early on and refer to them by those names. - when the gender of the data subject is not known, use 'they'. - I put the facts in chronological order: first what happened, then what the data subject claimed, then what the controller claimed. Tag: Visual edit
  • 10:1610:16, 11 July 2023 diff hist +10 HDPA (Greece) - 20/2023Changes were made to adapt to GDPRHub guidelines. - establish at the outset who is the controller and who is the data subject and use this nomenclature throughout the summary - refer to the data subject as 'they' when the gender is unknown - put the facts in chronological order: what happened, what the data subject claimed, what the controller replied - put what the DPA decided in the holding Tag: Visual edit

21 June 2023

16 June 2023

6 June 2023

10 May 2023

9 May 2023

(newest | oldest) View ( | ) (20 | 50 | 100 | 250 | 500)