[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fNVPpaz0iPWBkLqY9XGUbqAPOUlAK6gqzm9Mi1CpHZ1M":3},{"tableOfContents":4,"markDownContent":5,"htmlContent":6,"metaTitle":7,"metaDescription":7,"wordCount":8,"readTime":9,"title":10,"nbDownloads":11,"excerpt":7,"lang":12,"url":13,"intro":14,"featured":4,"state":15,"author":16,"authorId":17,"datePublication":21,"dateCreation":22,"dateUpdate":23,"mainCategory":24,"categories":44,"metaDatas":50,"imageUrl":7,"imageThumbUrls":51,"id":52},false,"The right to object allows each person concerned by a processing operation to **object to the use of their data by an organisation**. \r\n\r\nThe organisation only has the option **of refusing to exercise this right if it can demonstrate compelling legitimate grounds for continuing to process the data**.\r\n\r\nThe data controller must then **define what these interests are** and how **they take precedence over the interests or rights and freedoms of the data subject**. \r\n\r\nThis is a **new feature** since the adoption of the GDPR entails a **reversal of the burden of proof**. Previously, the right to object required the data subject to prove a legitimate reason.\r\n\r\nNow it is up to the [data controller](https://www.dastra.eu/en/guide/what-are-my-obligations-as-a-data-controller/56294), when faced with a request to object, to demonstrate that there are legitimate and compelling grounds.\r\n\r\n## But how are these legitimate and compelling grounds to be assessed?\r\n\r\nAssessing whether an interest is legitimate presupposes : \r\n* first of all that it is **manifestly lawful in the eyes of the law**; and \r\n* the interest in question must also be **not too vague or hypothetical**, but set out in sufficiently clear terms \r\n* it must be **real and present**.\r\n\r\nThe treatment must also be **imperative**, which means that it must be **strictly necessary**, or even indispensable. \r\n\r\nHowever, no **general rule can be laid down** and it is necessary for the data controller to assess each exercise of the right to object **on a case-by-case basis**, and to be able to **argue the refusal precisely** in the event of a question from the competent supervisory authority or the individual concerned.\r\n\r\nFor example, compelling reasons may include processing relating to and necessary **for the performance of a contract or the recovery of a debt**.\r\n\r\n\r\nFinally, when personal data is processed for canvassing purposes, the data subject has the right **to object at any time to the processing of data concerning him or her for these purposes** without the data controller being able to oppose this on compelling and legitimate grounds. \r\n\r\n","\u003Cp>The right to object allows each person concerned by a processing operation to \u003Cstrong>object to the use of their data by an organisation\u003C/strong>.\u003C/p>\r\n\u003Cp>The organisation only has the option \u003Cstrong>of refusing to exercise this right if it can demonstrate compelling legitimate grounds for continuing to process the data\u003C/strong>.\u003C/p>\r\n\u003Cp>The data controller must then \u003Cstrong>define what these interests are\u003C/strong> and how \u003Cstrong>they take precedence over the interests or rights and freedoms of the data subject\u003C/strong>.\u003C/p>\r\n\u003Cp>This is a \u003Cstrong>new feature\u003C/strong> since the adoption of the GDPR entails a \u003Cstrong>reversal of the burden of proof\u003C/strong>. Previously, the right to object required the data subject to prove a legitimate reason.\u003C/p>\r\n\u003Cp>Now it is up to the \u003Ca href=\"https://www.dastra.eu/en/guide/what-are-my-obligations-as-a-data-controller/56294\">data controller\u003C/a>, when faced with a request to object, to demonstrate that there are legitimate and compelling grounds.\u003C/p>\r\n\u003Ch2 id=\"but-how-are-these-legitimate-and-compelling-grounds-to-be-assessed\">But how are these legitimate and compelling grounds to be assessed?\u003C/h2>\r\n\u003Cp>Assessing whether an interest is legitimate presupposes :\u003C/p>\r\n\u003Cul>\r\n\u003Cli>first of all that it is \u003Cstrong>manifestly lawful in the eyes of the law\u003C/strong>; and\u003C/li>\r\n\u003Cli>the interest in question must also be \u003Cstrong>not too vague or hypothetical\u003C/strong>, but set out in sufficiently clear terms\u003C/li>\r\n\u003Cli>it must be \u003Cstrong>real and present\u003C/strong>.\u003C/li>\r\n\u003C/ul>\r\n\u003Cp>The treatment must also be \u003Cstrong>imperative\u003C/strong>, which means that it must be \u003Cstrong>strictly necessary\u003C/strong>, or even indispensable.\u003C/p>\r\n\u003Cp>However, no \u003Cstrong>general rule can be laid down\u003C/strong> and it is necessary for the data controller to assess each exercise of the right to object \u003Cstrong>on a case-by-case basis\u003C/strong>, and to be able to \u003Cstrong>argue the refusal precisely\u003C/strong> in the event of a question from the competent supervisory authority or the individual concerned.\u003C/p>\r\n\u003Cp>For example, compelling reasons may include processing relating to and necessary \u003Cstrong>for the performance of a contract or the recovery of a debt\u003C/strong>.\u003C/p>\r\n\u003Cp>Finally, when personal data is processed for canvassing purposes, the data subject has the right \u003Cstrong>to object at any time to the processing of data concerning him or her for these purposes\u003C/strong> without the data controller being able to oppose this on compelling and legitimate grounds.\u003C/p>\r\n",null,336,2,"Legitimate and compelling reasons",0,"en","legitimate-and-compelling-reasons","What are the legitimate and compelling reasons in the GDPR?","Published",{"id":17,"displayName":18,"avatarUrl":19,"bio":7,"blogUrl":7,"color":7,"userId":17,"creationDate":20},38,"Paul-Emmanuel Bidault","https://static.dastra.eu/tenant-27/avatar/38/paul-emmanuel-bidault-150.jpg","2019-12-03T19:09:28","2023-12-27T09:41:49.892","2023-12-27T10:41:48.1393074","2023-12-27T10:43:31.8735911",{"id":25,"name":26,"description":27,"url":28,"color":29,"parentId":7,"count":7,"imageUrl":30,"parent":7,"order":11,"translations":31},21,"Glossary","Definition of every word used by Dastra","glossary","#643bb0","https://static.dastra.eu/tag/b308b9d3-37af-4e92-8354-ab8adec1740a/documentation-1000.png",[32,36,40],{"lang":33,"name":34,"description":35},"fr","Glossaire","La définition de tous les termes utilisés dans Dastra",{"lang":37,"name":38,"description":39},"es","Glosario","La definición de todos los términos utilizados en Dastra",{"lang":41,"name":42,"description":43},"de","Glossar","Die Definition aller in Dastra verwendeten Begriffe",[45],{"id":25,"name":26,"description":27,"url":28,"color":29,"parentId":7,"count":7,"imageUrl":30,"parent":7,"order":11,"translations":46},[47,48,49],{"lang":33,"name":34,"description":35},{"lang":37,"name":38,"description":39},{"lang":41,"name":42,"description":43},[],[],56325]