[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fq4WaaWNBpJRW_0fxnGT8sM3Kba9Df8Yb6Lvzl7JLX9w":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":51,"imageThumbUrls":52,"id":53},false,"In all data processing, care must be taken to ensure the **quality of the data** used. This data must comply with the strict rules set out in **[Article 5 of the GDPR](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32016R0679)**.\r\n \r\nIn particular, it must not be excessive in relation to the purpose of the processing. This is the principle of **data minimisation**.\r\n \r\n## The data minimisation principle\r\n \r\nThe principle of data minimisation stems from the [**purpose principle**](https://www.dastra.eu/en/guide/purpose-of-processing/56312): it involves **collecting strictly what the data controller needs to meet the defined purpose**.\r\n \r\nThe data collected must be :\r\n \r\n- **Appropriate**,\r\n- **Relevant**: i.e. there must be a direct link with the purpose of processing,\r\n-** Limited** to what is strictly necessary.\r\n\r\n### 1. Data relevance\r\n \r\nTo understand the principle of data relevance, a distinction must be made between mandatory data and optional data: mandatory data, even if relevant, must be limited to what is necessary. Optional data, on the other hand, can be requested, leaving the data subject the choice of whether or not to provide it.\r\n \r\nTo determine whether data should be minimised, we need to adopt the precautionary principle and ask ourselves a number of questions relating to data processing:\r\n\r\n- What is my purpose?\r\n- What data is essential to achieve this objective?\r\n- Do I have the right to collect this data?\r\n- Have I made a clear distinction between mandatory and optional data?\r\n\r\n### 2. Data accuracy\r\n \r\nData must be accurate and, if necessary, kept up to date: \"*All reasonable steps must be taken to delete or rectify inaccurate data*\".\r\n\r\n> For example, inaccurate bank details can have a very negative impact on the person concerned: the institution might not record the repayment of a loan that has already been made.\r\n\r\n### 3. Some special cases\r\n\r\n- **Date of birth**  \r\n\r\nThe date of birth is not relevant for all types of processing. For example, if the [data controller](https://www.dastra.eu/en/guide/what-are-my-obligations-as-a-data-controller/56294) wishes to know more about its electorate, it can collect only the age group concerned by the elections. On the other hand, this data can be collected on an optional basis at the time of collection.\r\n- **Video surveillance**\r\n\r\nRelevance also applies to video surveillance systems. The principle of minimisation applies to the choice of the number of cameras installed, their technical characteristics, the area to be filmed, etc.\r\n\r\nThe principle of minimisation applies to the choice of the number of cameras installed, their technical characteristics, the area to be filmed, etc. > Ex: ban on filming employees at their workstations, break areas, union premises and access to these specific premises, except in special circumstances (handling money, food dispensers, etc).\r\n\r\n**4. Some good practices:**\r\n \r\n*1. Sort your data regularly*.  \r\n Question the nature, quantity and accuracy of the data collected, particularly when you create or identify a contact form.\r\n \r\n*2. Look for less intrusive alternatives*.  \r\n Always ask yourself whether a less intrusive solution exists.\r\n \r\n*3. Do not collect data as a precaution*.  \r\n Ban all preventive data collection.\r\n \r\n*4. Remember to pseudonymise*  \r\n Pseudonymise data whenever it is not necessary to store it in a directly identifiable form.\r\n\r\n> For example, for statistical purposes, pseudonymisation consists of replacing surnames and first names with random numbers.\r\n\r\n*5. Give preference to drop-down menus*.  \r\n Limit the number of free comment zones / Use drop-down menus instead.\r\n\r\n","\u003Cp>In all data processing, care must be taken to ensure the \u003Cstrong>quality of the data\u003C/strong> used. This data must comply with the strict rules set out in \u003Cstrong>\u003Ca href=\"https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32016R0679\" rel=\"nofollow\">Article 5 of the GDPR\u003C/a>\u003C/strong>.\u003C/p>\r\n\u003Cp>In particular, it must not be excessive in relation to the purpose of the processing. This is the principle of \u003Cstrong>data minimisation\u003C/strong>.\u003C/p>\r\n\u003Ch2 id=\"the-data-minimisation-principle\">The data minimisation principle\u003C/h2>\r\n\u003Cp>The principle of data minimisation stems from the \u003Ca href=\"https://www.dastra.eu/en/guide/purpose-of-processing/56312\">\u003Cstrong>purpose principle\u003C/strong>\u003C/a>: it involves \u003Cstrong>collecting strictly what the data controller needs to meet the defined purpose\u003C/strong>.\u003C/p>\r\n\u003Cp>The data collected must be :\u003C/p>\r\n\u003Cul>\r\n\u003Cli>\u003Cstrong>Appropriate\u003C/strong>,\u003C/li>\r\n\u003Cli>\u003Cstrong>Relevant\u003C/strong>: i.e. there must be a direct link with the purpose of processing,\r\n-** Limited** to what is strictly necessary.\u003C/li>\r\n\u003C/ul>\r\n\u003Ch3 id=\"data-relevance\">1. Data relevance\u003C/h3>\r\n\u003Cp>To understand the principle of data relevance, a distinction must be made between mandatory data and optional data: mandatory data, even if relevant, must be limited to what is necessary. Optional data, on the other hand, can be requested, leaving the data subject the choice of whether or not to provide it.\u003C/p>\r\n\u003Cp>To determine whether data should be minimised, we need to adopt the precautionary principle and ask ourselves a number of questions relating to data processing:\u003C/p>\r\n\u003Cul>\r\n\u003Cli>What is my purpose?\u003C/li>\r\n\u003Cli>What data is essential to achieve this objective?\u003C/li>\r\n\u003Cli>Do I have the right to collect this data?\u003C/li>\r\n\u003Cli>Have I made a clear distinction between mandatory and optional data?\u003C/li>\r\n\u003C/ul>\r\n\u003Ch3 id=\"data-accuracy\">2. Data accuracy\u003C/h3>\r\n\u003Cp>Data must be accurate and, if necessary, kept up to date: \"\u003Cem>All reasonable steps must be taken to delete or rectify inaccurate data\u003C/em>\".\u003C/p>\r\n\u003Cblockquote>\r\n\u003Cp>For example, inaccurate bank details can have a very negative impact on the person concerned: the institution might not record the repayment of a loan that has already been made.\u003C/p>\r\n\u003C/blockquote>\r\n\u003Ch3 id=\"some-special-cases\">3. Some special cases\u003C/h3>\r\n\u003Cul>\r\n\u003Cli>\u003Cstrong>Date of birth\u003C/strong>\u003C/li>\r\n\u003C/ul>\r\n\u003Cp>The date of birth is not relevant for all types of processing. For example, if the \u003Ca href=\"https://www.dastra.eu/en/guide/what-are-my-obligations-as-a-data-controller/56294\">data controller\u003C/a> wishes to know more about its electorate, it can collect only the age group concerned by the elections. On the other hand, this data can be collected on an optional basis at the time of collection.\u003C/p>\r\n\u003Cul>\r\n\u003Cli>\u003Cstrong>Video surveillance\u003C/strong>\u003C/li>\r\n\u003C/ul>\r\n\u003Cp>Relevance also applies to video surveillance systems. The principle of minimisation applies to the choice of the number of cameras installed, their technical characteristics, the area to be filmed, etc.\u003C/p>\r\n\u003Cp>The principle of minimisation applies to the choice of the number of cameras installed, their technical characteristics, the area to be filmed, etc. > Ex: ban on filming employees at their workstations, break areas, union premises and access to these specific premises, except in special circumstances (handling money, food dispensers, etc).\u003C/p>\r\n\u003Cp>\u003Cstrong>4. Some good practices:\u003C/strong>\u003C/p>\r\n\u003Cp>\u003Cem>1. Sort your data regularly\u003C/em>.\u003Cbr />\r\nQuestion the nature, quantity and accuracy of the data collected, particularly when you create or identify a contact form.\u003C/p>\r\n\u003Cp>\u003Cem>2. Look for less intrusive alternatives\u003C/em>.\u003Cbr />\r\nAlways ask yourself whether a less intrusive solution exists.\u003C/p>\r\n\u003Cp>\u003Cem>3. Do not collect data as a precaution\u003C/em>.\u003Cbr />\r\nBan all preventive data collection.\u003C/p>\r\n\u003Cp>\u003Cem>4. Remember to pseudonymise\u003C/em>\u003Cbr />\r\nPseudonymise data whenever it is not necessary to store it in a directly identifiable form.\u003C/p>\r\n\u003Cblockquote>\r\n\u003Cp>For example, for statistical purposes, pseudonymisation consists of replacing surnames and first names with random numbers.\u003C/p>\r\n\u003C/blockquote>\r\n\u003Cp>\u003Cem>5. Give preference to drop-down menus\u003C/em>.\u003Cbr />\r\nLimit the number of free comment zones / Use drop-down menus instead.\u003C/p>\r\n",null,562,3,"Data minimisation principle",0,"en","data-minimisation-principle","The principle of minimisation stems from the principle of purpose: it involves collecting only what the data controller needs to meet the defined objective. ","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-27T14:11:31.145","2023-12-27T15:11:29.8104569","2023-12-28T13:50:52.0040101",{"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},[],"https://static.dastra.eu/content/827e0709-2018-44ec-b5c9-607e34136308%2Fminimisation-1000.png",[],56347]