A community for people using data in the social sector

Data and the Law

Small charities and community organisations often don’t have the funding to get bespoke legal advice. However, they still have the need for processes and policies about data use in order to guide best practice, abide by regulations, and manage organisational risks. The information below is from a 2021 Data Collective surgery session with Chloe Parker, service user database expert at Core Insights; and Alex Matheson, Senior Associate at DLA Piper law firm.

Privacy by design

Chloe Parker of Core Insights comments that “A good litmus test when thinking about data protection is thinking about the most vulnerable people in your life. Would you be happy processing data about them in this way?”

Top tips for built-in privacy

Start from a good foundation

Document all of your processes, especially where data is stored. Here’s a data security starter checklist:

  • What data is stored where?
  • Who has access to each piece of data? 
  • Who do you share your data with? When? How?
  • Is this documented?

You can make a copy or download this GDPR Record of Processing Activities template, from The Data Place.

Get the right tools for the job

Use CRMs and software with built-in data privacy processes, such as email encryption, multi-factor authentication, and user level permissions. Keep in mind that default settings might mean that these features are available but hidden away in a settings panel somewhere, waiting to be switched on.

Remember practical security

Systems may be encrypted, but people can be forgetful! Make sure sensitive paper files are locked away. If you have to share data outside of your secure systems, e.g. by email, make sure it is password protected and you only share the password separately from the email you are sending (e.g. over the phone).

Processing data legally

Alex Matheson of DLA Piper tells us about legal aspects of data protection and data sharing with volunteers.

All data sharing is a form of processing. When processing data, first consider whether you are compliant with UK-GDPR. A data sharing agreement between any parties sharing data is good practice, and the Information Commissioner’s Office has guidance and templates for these.

The Information Commissioner’s Office (ICO) is the supervisory authority for the UK, and enforces UK-GDPR regulations. It is interested in organisational culture: if you make mistakes with data processing, but have a good culture and can evidence that you have tried your best e.g. by documenting your processes and showing that you have trained staff to follow them, this will influence their enforcement decision. Not all data breaches require notifying the ICO – they explain more on their website.

Sharing with volunteers

If your organisation regularly works with volunteers, it’s very important to:

  • Have a Data Protection Policy that is consistent with your privacy notice
  • Provide regular data protection training, even if volunteers are only with the organisation for a short period of time

When sharing data with volunteers, consider the outcomes of worst case scenarios, such as if someone takes a database. That’s a criminal offence and is committed by the individual – one of the few cases where there’s personal liability. An individual who takes a database without consent can be prosecuted for this, and it has happened. The ICO has more on data sharing here: Data sharing information hub.

Who is responsible?

Two roles to understand the differences between are a data controller and a data processor.

The data controller is the organisation which owns the data and is ultimately responsible for it. They decide what happens to the data. If there’s a data breach, the controller is responsible for notifying the ICO.

The data processor can be a separate organisation which carries out a function, for instance they might help you do some analysis you can’t do in house. For charities, this may be a third party company that owns and runs their CRM platform.

The ICO also provides full information on the difference between data controllers and data processors.

Before any data project, it will help to run a Data Protection Impact Assessment (DPIA) – the ICO has very detailed information on its website: How do we do a DPIA?

Q&A with Chloe and Alex

If as a consultancy we collect data about people for an organisation that has hired us, are we the controllers or the processors? We are likely to be the ones keeping the database on our servers.
Ask yourself three things:

  1. Are you retaining or deleting the data? If you are the one deleting the data, you might be the controller. If you’re retaining the data because of an agreement, you might not be the controller. If you’re keeping it for your own purposes, either you shouldn’t, because you’re the processor, or you’re the controller.
  2. If there’s a breach, who would you expect to notify the ICO? If it’s you/your organisation, then you’re the controller.
  3. Who sends the privacy notices? If it’s your organisation, you’re the controller.

Does data sharing with another data controller need an agreement?
It’s not strictly required to have data sharing agreement, but definitely good practice and we’d recommend it.

At which point do we need to contact people whose data has been breached?
You must notify the ICO within 72 hours, and notify data subjects without ‘undue delay’. It helps to have a policy in place on what constitutes a breach, and clear timelines detailing how you will contact all of your data subjects.

Are there additional requirements if working with an organisation in an EU country and processing data, eg running a joint event and processing participant data?
In the UK, we now have two GDPRs: EU GDPR and UK GDPR, which are very similar. For data sharing, generally the EU and UK trust each other. This is not always the case with non-EU countries. And if there’s a data breach, you may need to notify multiple supervisory authorities (i.e the EU authority of an EU member state, not just the ICO). Further information on UK/EU data transfers can be found here.

If there’s a breach due to a widespread failure in a tool, such as an email marketing platform, do we need to notify authorities?
Typically, the company would notify all their customers. The customers then need to assess whether they need to notify authorities and data subjects.

There are additional requirements for working with non-EU organisations: a data transfer agreement is usually needed, to make sure data is safe in the jurisdiction it is being sent to.

If data subjects come from different countries do you need to contact other country’s regulatory authorities?
It depends on the country.