Developing a large language model such as ChatGPT requires gathering vast bodies of text through a process called web scraping. These datasets ingest details from open online sources such as social media profiles. If data is pulled from publicly available sources, it is in the scope of privacy laws. AI is now regulated by standard privacy laws, like the General Data Protection Regulation (GDPR) and similar law regimes.

GDPR places various stringent obligations on any organization storing, transmitting, or performing analytics on personal data. The most fundamental issue under GDPR is identifying a legal basis for scraping the personal data of millions of people without their knowledge or consent. This matter has been subject to heavy regulatory and judicial scrutiny across Europe, and there’s no simple solution in sight.

It is still unknown how GDPR will apply to generative AI, but some decisions have been made. ChatGPT was temporarily banned by the Italian Data Protection Authority over incorrect results and a lack of lawful grounds for the processing, as well as the mismanagement of children’s data. Google then had to postpone the EU launch of its competitor Bard over similar privacy challenges.

You may also like:

Data privacy laws in the United States and how they affect your business

11 new privacy laws around the world and how they’ll affect your analytics

Data privacy breach


  • Privacy by design in practice: How “just enough” data beats “just in case” collection

    While collecting more data “just in case” feels safer, according to Matt Gershoff, it’s also one of the biggest sources of unnecessary compliance risk, analytical noise, and wasted organizational resources in the analytics industry today. His approach of “just enough” data collection is more intentional, more aligned with privacy regulation, and often more analytically effective.

  • 4 ways to make your analytics HIPAA-compliant: Implementation guide

    Healthcare organizations have four main approaches to achieving HIPAA-compliant analytics. Each has different trade-offs in cost, technical complexity, and analytics capabilities. This guide compares all four implementation methods – from using Google Analytics with workarounds to deploying fully HIPAA-compliant analytics platforms – so you can choose the right approach for your organization’s needs and resources.