How to Comply with EU AI Act using PrivateGPT

Oct 31, 2023
Share this post
Sharing to FacebookSharing to LinkedInSharing to XSharing to Email

The recently amended EU AI Act proposal we introduced in this blog post, would regulate “foundational models,” defined in Art. 3(1c) as “an AI model that is trained on broad data at scale, is designed for generality of output, and can be adapted to a wide range of distinctive tasks.” This blog post sets out what compliance obligations will be imposed on OpenAI’s ChatGPT and other foundational models upon the coming into force of the proposed act, the most recent amendments to which were recently endorsed by Parliament.The obligations imposed on a provider of a foundation model include additional transparency criteria, such as disclosing that the content is generated by artificial intelligence, ensuring the model is designed to prevent the generation of unlawful content, and providing summaries of copyrighted data utilized for training purposes. See how current foundation model providers do with their compliance here. Spoiler alert, they’re not doing great. We’ll dive into each of the requirements under the Act in detail and follow with what PrivateGPT can do to facilitate compliance with these new obligations.

Obligations of the Provider of a Foundational Model

Classifying ChatGPT as its own type of AI system by introducing the new category of “foundation model” and the subcategory of “generative AI” is apparently a compromise that intends to support innovation. If ChatGPT were instead classified as a “high-risk” AI system under the EU AI Act, more stringent obligations would apply than the ones that follow:1. Registration and Transparency: Like high-risk AI models, foundational models must be registered in an EU database established and managed by the Commission, including the following information:a) Name, address and contact details of the provider;b) Where submission of information is carried out by another person on behalf of the provider, the name, address and contact details of that person;c) Name, address and contact details of the authorised representative, where applicable;d) Trade name and any additional unambiguous reference allowing the identification of the foundation modele) Description of the data sources used in the development of the foundational modelf) Description of the capabilities and limitations of the foundation model, including the reasonably foreseeable risks and the measures that have been taken to mitigate them as well as remaining non-mitigated risks with an explanation on the reason why they cannot be mitigatedg) Description of the training resources used by the foundation model including computing power required, training time, and other relevant information related to the size and power of the modelh) Description of the model’s performance, including on public benchmarks or state of the art industry benchmarksi) Description of the results of relevant internal and external testing and optimisation of the modelj) Member States in which the foundation model is or has been placed on the market, put into service or made available in the Union;k) URL for additional information (optional).2. Demonstrable risk mitigation: Providers of foundational models are required to ensure that risk of identification, to health, safety, fundamental rights, the environment, democracy, and the rule of law is demonstrably reduced and mitigated through design, testing, and analysis, and remaining non-mitigable risks are documented. (Art. 28b(2)(a)).3.Suitable data sources: Data sources must be examined for their suitability, possible biases, and appropriate mitigation. (Art. 28b(2)(b)).4. Long-term view to design and development: Design and development of foundational models must achieve appropriate levels of performance, predictability, interpretability, corrigibility, safety, and cybersecurity throughout its lifecycle. Relevant documentation must be kept for 10 years. (Art. 28b(2)(c)).5. Environmental sustainability: The foundational model must be designed and developed making use of applicable standards to reduce energy use, resource use and waste, as well as to increase energy efficiency, and the overall efficiency of the system. (Art. 28b(2)(d)).6. Instructions to downstream providers: Providers of foundational models must enable downstream providers to comply with their respective obligations under the Act by drawing up extensive technical documentation and intelligible instructions. (Art. 28b(2)(e)).7. Quality management system: Providers of foundation models must also implement a quality management system to ensure and document their compliance. The Act does, however, explicitly allow for “the possibility to experiment in fulfilling this requirement.”

Additional Obligations for Generative AI Models

Foundation models used in AI systems specifically intended to generate, with varying levels of autonomy, content such as complex text, images, audio, or video are called “generative AI.” Providers of these kinds of AI systems have to meet the same obligations set out above, and in addition, the following:1. Additional Transparency:a) Notify individuals that they are interacting with an AI system, unless it is obvious, or the AI system is authorized to be used to detect, prevent, investigate and prosecute criminal offences, unless those systems are available for the public to report a criminal offence.b) If the foundation model is used as an emotion recognition or a biometric categorization system, the person exposed to it must be informed of the operation of the system, with the same exception noted under a.c) Users of an AI system that generates or manipulates image, audio or video content that appreciably resembles existing persons, objects, places or other entities or events and would falsely appear to a person to be authentic or truthful (‘deep fake’), shall disclose that the content has been artificially generated or manipulated, with certain exceptions for law enforcement purposes and fundamental rights protections.2. Safeguards against rights violations and breaches of Union law: Adequate, state-of-the-art safeguards must be implemented to ensure that the generated content does not breach Union law or fundamental rights, incl. freedom of expression.3. Copyright law compliance: Providers of generative AI systems must make publicly available a sufficiently detailed summary of the use of training data protected under copyright law without such publication itself violating applicable copyrights.

Consequences of Non-Compliance

Violation by a foundation model of EU AI Act provisions discussed above would cost € 10 million or for businesses 2 % of total worldwide annual turnover, whichever is higher (Art. 71(4)). Orders and warnings are also measures that can be imposed either instead of or in addition to monetary fines (Art. 71(6)).

How Can Private AI Help with EU AI Act Compliance When Using ChatGPT?

First, Private AI’s PrivateGPT is uniquely equipped to help achieve compliance with the “demonstrable risk mitigation” requirement, in particular, the requirement to mitigate the risk of identification. The EU AI Act doesn’t say anything more about this requirement. It stands to reason that the risk of identification is a subtle reference to the GDPR, with which the foundation model of course also has to comply. For example, this requirement demands that the inclusion of personal information in the data set is closely monitored and ideally avoided.PrivateGPT filters out more than 50 entity types including personally identifiable information, protected health information, and Payment Card Industry data before such identifiers are sent to ChatGPT. Here is how:

Had ChatGPT been trained on data that was rendered safe by Private AI, there would be no risk of re-identification and the “Suitable data source” requirement could have more easily been met as well. PrivateGPT can be used to render any training data set safe if employed early on in the development and training process.View the Huggingface guide for privacy-preserving sentiment analysisFurthermore, when deployed for the subsequent use of an LLM, PrivateGPT can make sure no personal data of users is fed to the model which may or may not be used to train the model. In any case, the privacy filter will prevent the disclosure of personal data and hence ensure that the identification of the user by third parties with access to the chat history will not be possible.Second, by removing personal identifiers from the input before it is disclosed to ChatGPT, PrivateGPT can help mitigate the risk of biased output, as we have demonstrated in this blog post. This ability can help address the requirement under Art. 28(b)(2)(b), namely, to examine data sources for their suitability, possible biases, and appropriate mitigation. Again, a data source can’t be rendered unbiased by PrivateGPT once the bias is in there, but it can certainly mitigate the risk of having biased outputs as a result of the data source containing biased content, for example by removing any indicators regarding race, ethnicity, gender, etc.

Conclusion

In conclusion, the introduction of the EU AI Act and its recent amendments highlights the need for increased transparency, risk mitigation, environmental consciousness and more in the deployment of foundation models like ChatGPT. PrivateGPT by Private AI emerges as a valuable solution to address some of these requirements. PrivateGPT can contribute to a more privacy-conscious and ethically sound AI ecosystem. By leveraging PrivateGPT's capabilities, compliance with the EU AI Act can be facilitated, fostering responsible AI development and improved protection of individuals' privacy.

Get started with PrivateGPT today:

Try it free today

Data Left Behind: AI Scribes’ Promises in Healthcare

Data Left Behind: Healthcare’s Untapped Goldmine

The Future of Health Data: How New Tech is Changing the Game

Why is linguistics essential when dealing with healthcare data?

Why Health Data Strategies Fail Before They Start

Private AI to Redefine Enterprise Data Privacy and Compliance with NVIDIA

EDPB’s Pseudonymization Guideline and the Challenge of Unstructured Data

HHS’ proposed HIPAA Amendment to Strengthen Cybersecurity in Healthcare and how Private AI can Support Compliance

Japan's Health Data Anonymization Act: Enabling Large-Scale Health Research

What the International AI Safety Report 2025 has to say about Privacy Risks from General Purpose AI

Private AI 4.0: Your Data’s Potential, Protected and Unlocked

How Private AI Facilitates GDPR Compliance for AI Models: Insights from the EDPB's Latest Opinion

Navigating the New Frontier of Data Privacy: Protecting Confidential Company Information in the Age of AI

Belgium’s Data Protection Authority on the Interplay of the EU AI Act and the GDPR

Enhancing Compliance with US Privacy Regulations for the Insurance Industry Using Private AI

Navigating Compliance with Quebec’s Act Respecting Health and Social Services Information Through Private AI’s De-identification Technology

Unlocking New Levels of Accuracy in Privacy-Preserving AI with Co-Reference Resolution

Strengthened Data Protection Enforcement on the Horizon in Japan

How Private AI Can Help to Comply with Thailand's PDPA

How Private AI Can Help Financial Institutions Comply with OSFI Guidelines

The American Privacy Rights Act – The Next Generation of Privacy Laws

How Private AI Can Help with Compliance under China’s Personal Information Protection Law (PIPL)

PII Redaction for Reviews Data: Ensuring Privacy Compliance when Using Review APIs

Independent Review Certifies Private AI’s PII Identification Model as Secure and Reliable

To Use or Not to Use AI: A Delicate Balance Between Productivity and Privacy

To Use or Not to Use AI: A Delicate Balance Between Productivity and Privacy

News from NIST: Dioptra, AI Risk Management Framework (AI RMF) Generative AI Profile, and How PII Identification and Redaction can Support Suggested Best Practices

Handling Personal Information by Financial Institutions in Japan – The Strict Requirements of the FSA Guidelines

日本における金融機関の個人情報の取り扱い - 金融庁ガイドラインの要件

Leveraging Private AI to Meet the EDPB’s AI Audit Checklist for GDPR-Compliant AI Systems

Who is Responsible for Protecting PII?

How Private AI can help the Public Sector to Comply with the Strengthening Cyber Security and Building Trust in the Public Sector Act, 2024

A Comparison of the Approaches to Generative AI in Japan and China

Updated OECD AI Principles to keep up with novel and increased risks from general purpose and generative AI

Is Consent Required for Processing Personal Data via LLMs?

The evolving landscape of data privacy legislation in healthcare in Germany

The CIO’s and CISO’s Guide for Proactive Reporting and DLP with Private AI and Elastic

The Evolving Landscape of Health Data Protection Laws in the United States

Comparing Privacy and Safety Concerns Around Llama 2, GPT4, and Gemini

How to Safely Redact PII from Segment Events using Destination Insert Functions and Private AI API

WHO’s AI Ethics and Governance Guidance for Large Multi-Modal Models operating in the Health Sector – Data Protection Considerations

How to Protect Confidential Corporate Information in the ChatGPT Era

Unlocking the Power of Retrieval Augmented Generation with Added Privacy: A Comprehensive Guide

Leveraging ChatGPT and other AI Tools for Legal Services

Leveraging ChatGPT and other AI tools for HR

Leveraging ChatGPT in the Banking Industry

Law 25 and Data Transfers Outside of Quebec

The Colorado and Connecticut Data Privacy Acts

Unlocking Compliance with the Japanese Data Privacy Act (APPI) using Private AI

Tokenization and Its Benefits for Data Protection

Private AI Launches Cloud API to Streamline Data Privacy

Processing of Special Categories of Data in Germany

End-to-end Privacy Management

Privacy Breach Reporting Requirements under Law25

Migrating Your Privacy Workflows from Amazon Comprehend to Private AI

A Comparison of the Approaches to Generative AI in the US and EU

Benefits of AI in Healthcare and Data Sources (Part 1)

Privacy Attacks against Data and AI Models (Part 3)

Risks of Noncompliance and Challenges around Privacy-Preserving Techniques (Part 2)

Enhancing Data Lake Security: A Guide to PII Scanning in S3 buckets

The Costs of a Data Breach in the Healthcare Sector and its Privacy Compliance Implications

Navigating GDPR Compliance in the Life Cycle of LLM-Based Solutions

What’s New in Version 3.8

How to Protect Your Business from Data Leaks: Lessons from Toyota and the Department of Home Affairs

New York's Acceptable Use of AI Policy: A Focus on Privacy Obligations

Safeguarding Personal Data in Sentiment Analysis: A Guide to PII Anonymization

Changes to South Korea’s Personal Information Protection Act to Take Effect on March 15, 2024

Australia’s Plan to Regulate High-Risk AI

How Private AI can help comply with the EU AI Act

Comment la Loi 25 Impacte l'Utilisation de ChatGPT et de l'IA en Général

Endgültiger Entwurf des Gesetzes über Künstliche Intelligenz – Datenschutzpflichten der KI-Modelle mit Allgemeinem Verwendungszweck

How Law25 Impacts the Use of ChatGPT and AI in General

Is Salesforce Law25 Compliant?

Creating De-Identified Embeddings

Exciting Updates in 3.7

EU AI Act Final Draft – Obligations of General-Purpose AI Systems relating to Data Privacy

FTC Privacy Enforcement Actions Against AI Companies

The CCPA, CPRA, and California's Evolving Data Protection Landscape

HIPAA Compliance – Expert Determination Aided by Private AI

Private AI Software As a Service Agreement

EU's Review of Canada's Data Protection Adequacy: Implications for Ongoing Privacy Reform

Acceptable Use Policy

ISO/IEC 42001: A New Standard for Ethical and Responsible AI Management

Reviewing OpenAI's 31st Jan 2024 Privacy and Business Terms Updates

Comparing OpenAI vs. Azure OpenAI Services

Quebec’s Draft Regulation Respecting the Anonymization of Personal Information

Version 3.6 Release: Enhanced Streaming, Auto Model Selection, and More in Our Data Privacy Platform

Brazil's LGPD: Anonymization, Pseudonymization, and Access Requests

LGPD do Brasil: Anonimização, Pseudonimização e Solicitações de Acesso à Informação

Canada’s Principles for Responsible, Trustworthy and Privacy-Protective Generative AI Technologies and How to Comply Using Private AI

Private AI Named One of The Most Innovative RegTech Companies by RegTech100

Data Integrity, Data Security, and the New NIST Cybersecurity Framework

Safeguarding Privacy with Commercial LLMs

Cybersecurity in the Public Sector: Protecting Vital Services

Privacy Impact Assessment (PIA) Requirements under Law25

Elevate Your Experience with Version 3.5

Fine-Tuning LLMs with a Focus on Privacy

GDPR in Germany: Challenges of German Data Privacy (Part 2)

Comply with US Executive Order on Safe, Secure, and Trustworthy Artificial Intelligence using Private AI

How to Comply with EU AI Act using PrivateGPT