It’s hard to believe that we’re approaching the one Year Anniversary of the GDPR. After a two-year transition period, the GDPR came into force on the 25th May 2018, and completely transformed how organisations approach data privacy.
The legislation was introduced to reflect our increasingly digitalised world and recognise the rights of individuals with regards to the use of their personal data.
Many organisations have spent a lot of time and effort ensuring they are compliant with the new legislation, however for others, it has been a more difficult and arduous journey. Demonstrating compliance with the GDPR is an ongoing process and there are many aspects of the legislation that still require clarification and can prove confusing for organisations.
Two terms that we hear constantly in relation to GDPR are ‘Data Controllers’ and Data Processors’. It’s important to understand the distinction between these two terms as it will determine your responsibilities under the legislation.
The distinction between a Data Controller and a Data Processor can have significant real-world consequences. If an organisation is involved in data processing, it’s vital they establish roles and responsibilities at an early stage to avoid any confusion should a data breach occur. This will help ensure that there are no gaps in responsibilities and organisations can deal with these issues efficiently and effectively.
If your organisation processes personal data, then the GDPR applies to you. The EU defines ‘Personal Data’ as any information that can be used to directly or indirectly to identify an individual (data subject). This will include everything from a name, email address, IP address and images. It also includes sensitive personal data such as biometric data or genetic data which could be processed to identify an individual.
If your organisation determines the purposes and manner in which personal data is processed, then it’s considered to be a Data Controller.
Date Controllers play a key role in GDPR compliance because of the customer and employee personal data that they retain and collect.
Data Controller duties include:
If a person, organisation, agency or other body acts on behalf of a Data Controller, then they are considered to be a Data Processor.
Examples of a Data Processor include:
Read also the Dummies guide to ePrivacy Regulation
Data Processor duties include:
Data Processors are subject to several new obligations under the GDPR, which include maintaining measures that allocate adequate levels of security for personal data relative to the potential risk.
Data processors are required to abide by the instructions of Data Controllers unless these instructions conflict with the GDPR itself.
There are certain grey areas where situations may overlap making it difficult to distinguish if you are a Data Controller or Data Processor. However, the ICO is clear in its advice stating: “An organisation cannot be both data controller and processor for the same data processing activity; it must be one or the other.
This means that in order to establish which organisation has data protection responsibility for which data, it is necessary to look at the processing in question, as well as the organisations involved. It is also important that, as far as is practicable, systems and procedures distinguish between the organisation’s ‘own’ data and the data it processes on behalf of the other data.”
Learn also what is valid GDPR consent
To ensure full GDPR compliance, organisations will need to clearly define roles and responsibilities to avoid falling foul of the legislation. If you are in anyway unsure where your organisation stands, you should consult legal advice for further clarification.
MetaPrivacy has been designed to provide the best practice approach to data privacy compliance. Contact us for further information on how we can help your organisation improve its compliance structure.
DISCLAIMER: The content and opinions within this blog are for information purposes only. They are not intended to constitute legal or other professional advice and should not be relied on or treated as a substitute for specific advice relevant to particular circumstances, the Data Protection Act, or any other current or future legislation. MetaCompliance shall accept no responsibility for any errors, omissions or misleading statements, or for any loss which may arise from reliance on materials contained within this blog.