California Consumer Privacy Act (CCPA)
Why it matters
For AI, any consumer data flowing into training sets, embeddings, or automated decisions tied to California consumers triggers CCPA obligations. Most US-based AI products treat CCPA as the de facto baseline because it is the strictest state law actually being enforced, with fines and consent decrees on the public record. Other states have followed (Colorado, Virginia, Texas, and more), but CCPA still sets the bar. If a US AI vendor claims “state privacy compliant” without naming CCPA, I read that as a tell.
Where you’ll encounter it
Three contexts. A California customer submits a “do not sell or share my personal information” request and the AI pipeline has to honour it end to end, embeddings and retraining included. A vendor risk review asks how deletion propagates; “we retrained without the record” is not “the model forgot.” A privacy notice update is required when sensitive personal information (geolocation, biometrics, health, race, sexual orientation) enters the training set, often by accident through enriched features. The pitfall: teams treat CCPA’s right to delete as GDPR’s right to erasure. Carve-outs and verification differ. Map them side by side.
Part of the 7wData AI Glossary. Tracking how concepts like this move in the expert conversation: daily signals at ins7ghts.com.