Privacy and Compliance Considerations for ChatGPT Applications

Jul 17, 2023
Share this post
Sharing to FacebookSharing to LinkedInSharing to XSharing to Email

With OpenAI’s and Azure OpenAI’s API offerings, businesses are enabled to develop their own applications on top of the powerful large language models (LLMs) underlying ChatGPT, Whisper, and OpenAI’s other models. Close to a thousand commercial applications already exist that make use of OpenAI’s foundation models, including our own PrivateGPT which acts as the privacy layer for ChatGPT by removing any personally identifiable information from prompts before they get shared with the third party.With the incredible boost for innovative capabilities come certain drawbacks as well. If OpenAI gets things wrong in their development of the LLMs, the applications built upon the foundation model will likely suffer from the same flaws. This is an issue for responsible AI development in general, but we will only focus on data privacy compliance in this blog post.

OpenAI’s Data Protection in General

OpenAI’s Data Processing Addendum (DPA), not their Privacy Policy, governs the data collected from organizations using OpenAI’s API services for businesses in the absence of any other individually negotiated agreements. The DPA says that all parties agree to comply with applicable data privacy and data protection laws, which may include certain listed US privacy laws, including the CCPA, and the GDPR as well as subordinate legislation and regulation that implement those laws.This language is not particularly comforting if your business is offering services built on ChatGPT outside of these jurisdictions, e.g., in Canada or the UK. OpenAI also states that the DPA cannot be customized on a case-by-case basis, hence it may be advisable to obtain legal counsel to assess whether your or your customers’ data would be appropriately protected under the DPA or whether an individual agreement with OpenAI may be necessary to ensure data protection in accordance with the data privacy laws applicable to your organization.OpenAI’s SOC2 Type 2 certification and the fact that it has been audited against the 2017 Trust Services Criteria for Security by an independent auditor may provide some assurance as to the company’s data protection practices. However, prudent business practice would advise a review of these audit reports.

Location of Data

OpenAI represents that all customer data is processed and stored in the US. No data centres are located in the EU or elsewhere, and no capability currently exists to self-host.

Disclosure of Customer Data

Subservice providers used by OpenAI are, at the time of writing, Microsoft for providing cloud infrastructure; OpenAI affiliates for services and support; Snowflake for data warehousing; and TaskUS for user support and human annotation of data for service improvement. Microsoft and TaskUS are located ‘worldwide’ and the other two are in the US. In light of the fact that OpenAI says all customer data is processed and stored in the US, it seems that the Microsoft servers hosting OpenAI customer data are located in the US as well. It may be possible, however, to arrange storage in a jurisdiction more appropriate for an organization’s needs as Microsoft Azure’s data centres are located in many different geographies.For purposes of European businesses wishing to build an application based on OpenAI’s models, it makes little difference in which US state the data is stored, as no US state has currently received an adequacy decision by the EU Commission which would allow the data to be transferred across borders without further due diligence. In order to be able to still transfer personal data to the US, Art. 46 of the GDPR requires, among some other alternatives, that prescriptive contractual clauses be included in an agreement with OpenAI to ensure the protection of EU citizens’ data. Whether the DPA meets the GDPR’s standards may need to be assessed by legal counsel.For businesses intending to use ChatGPT as the basis for their own application which will process personal information of Quebec residents (a province in Canada), the data location information provided by OpenAI is insufficient. Starting September 22, 2023, the data protection law of Quebec requires a privacy impact assessment to be conducted before any personal information is disclosed outside of Quebec, which includes a jurisdiction-specific assessment of the adherence to recognized privacy principles. Hence, an inquiry into the location of the data warehouse where the information will be stored is necessary. Similarly, starting September 1, 2023, businesses to which the new Swiss data protection law applies are required to disclose to individuals the country to which their personal information is transferred as well as certain guarantees in place that ensure adequate data protection.

Data Transmission

According to OpenAI’s FAQ as well as the DPA, data in transmission via the API is encrypted. Transport Layer Security (TLS) ensures that the data cannot be altered or viewed by third parties during the transfer.

Data Retention

OpenAI retains data transmitted by API for 30 days at which point it is either deleted or aggregated or stored in a manner that does not identify individuals or customers.

Data Deletion Requests

OpenAI is committed to responding to reasonable deletion requests by their customers and will delete customer data upon termination of the business relationship. If a deletion request is made by an individual directly to them, OpenAI will contact the business promptly.

Personal Information Used for Product Improvement

The use of identifiable personal information for product improvement purposes will only take place upon explicit opt-in by the business using OpenAI’s API services. However, in aggregated or de-identified form, the data can be retained for longer than 30 days and be used for the purposes of improving OpenAI’s systems and services.

HIPAA Compliance

The US Health Insurance Portability and Accountability Act (HIPAA) requires health service providers to enter into so-called “business associate contracts” with entities that perform functions or activities on behalf of, or provide certain services to them that involve access to protected health information (PHI). This contract ensures that PHI is properly safeguarded, that the data is used for permissible purposes only, and that it is only disclosed further as required under the contract or the law.OpenAI indicates that they are able to enter into business associate contracts if required. Hence, compliance with HIPAA seems to be achievable, allowing businesses to build applications supporting healthcare services based on ChatGPT.

Conclusion

OpenAI has taken important steps towards compliance with data privacy laws. Several of the measures taken were enhancements in reaction to pressure applied by privacy regulators, for example the temporary ban of ChatGPT in Italy. Such measures are the opt-in approach to using data for product improvement purposes as well as limited data retention. Businesses building applications on top of models such as ChatGPT rely on OpenAI’s proper data handling processes. But blind trust in this regard is misplaced. The necessary due diligence should not be skipped in the race to build the next smashing ChatGPT application.The most foolproof measure to protect your customers’ personal information is to not transmit it to OpenAI in the first place. Private AI’s PrivateGPT filters out more than 50 entity types including PHI and Payment Card Industry (PCI) data from your prompt before it is sent to ChatGPT. The generated response is then repopulated with the original personal information before it is displayed to you. This seamless process allows your business to safely use the benefits of OpenAI’s models for your application while maintaining the trust of your customers who may otherwise be skeptical about the proper protection of their personal information. Try PrivateGPT 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