Europe’s New Data Law Went Into Effect on May 25 – Is Your Nonprofit GDPR Compliant?
Does your organization collect personal data such as names, email addresses or other personally identifying information as part of its activities, or contract with a third party to do so? If not, then it may be possible that Europe’s new data law does not apply to you.
But if your organization keeps mailing lists, distributes a newsletter, fundraises, sells products directly or indirectly, or has employees or program activities, and any of those reaches residents in Europe, then it is time to hit the pause button and make sure your organization has fulfilled its obligations to properly protect that information and obtain the appropriate consents required under GDPR.
What is GDPR?
The General Data Protection Regulation (“GDPR”), which became effective on May 25, 2018, was designed to enable individuals to better control their personal data, to know who stores, processes, and has access to their data, and even to request access to or deletion of it. GDPR applies to certain kinds of data inside the European Union, Liechtenstein, Norway and Iceland (the “EEA”), but also to data that flows outside of the EEA involving persons from the EEA. Thus, U.S.-based organizations may be subject to the law. GDPR requires enhanced security, data protection, appropriate technical and organizational measures, transparency, record keeping, and accountability. It also requires a 72-hour personal data breach notification to authorities.
“Personal data” is broadly defined to include any information relating to an identified or identifiable natural person, including their name, address, social security number, email address, banking information, medical information, or IP address. It also extends to online identifiers specific to the physical, physiological, genetic, mental, economic, cultural or social identity of a person.
GDPR requires that organizations holding protected personal data, whether nonprofit or for-profit, in the EEA or elsewhere, must have a lawful basis for processing personal data, including for example, with the individual’s consent, in order to perform a contract, to comply with legal obligations, or for the legitimate interests of the organization. Because GDPR does not grandfather in personal data collected prior to its enforcement, processing of previously collected personal data may continue only if the manner by which such data was collected would have complied with GDPR in the first place. Thus, where processing of data was based on consent, the consent obtained must meet the standard required by GDPR.
The Consent Standard:
GDPR requires that consent be freely given, specific, informed, and unambiguous, requiring a statement or clear affirmative action. The UK’s Information Commissioner’s Office suggests that, to meet the consent standard under GDPR, the affected organization should:
- not use pre-ticked boxes, opt-out boxes or any other method of default consent;
- be clear on why your nonprofit wants the data and what your nonprofit will do with it;
- name any third parties who will rely on the consent;
- make it easy for people to withdraw consent and tell them how (e.g., unsubscribe links in every email/newsletter);
- keep evidence of consent – who, when, how, and what your nonprofit told people; and
- avoid making consent a precondition of a service.
How to comply with GDPR: