CCPA Data Scrubber: Protect California Consumer Data

CCPA Data Scrubber: Protect California Consumer Data Before AI

CCPA covers any business that handles California residents' data above its revenue or volume thresholds¹, which includes most mid-size companies operating in the US. Sharing California consumer data with AI tools without a service provider agreement constitutes a "sale" or "share" under CCPA, triggering opt-out rights and potential fines from the California Privacy Protection Agency.

The California Privacy Rights Act amendments added the right to limit use of sensitive personal information, including SSNs, account log-in credentials, and health data². Scrubbing these fields before AI submission satisfies the limitation right technically: the sensitive data never reaches the AI provider, so its use there is not a concern.

CCPA categories the scrubber addresses

CCPA defines specific categories of personal information. The scrubber directly targets: identifiers (email addresses, phone numbers, IP addresses), financial information (credit card numbers, IBAN bank account numbers), internet or network activity (IP addresses in web logs, JWT session tokens), and sensitive personal information (SSNs, account log-in information in the form of API keys and database credentials). Building on this, CCPA's "household" concept means that an IP address associated with a home network is personal information for any California residents at that address³, and IPv4 and IPv6 detection covers this category.

The CCPA category that most frequently triggers AI-related violations is identifiers, because email addresses and IP addresses appear in virtually every log file, support ticket, and config export that teams paste into AI tools. A single customer support log pasted for AI-assisted analysis can contain the customer's email, their IP address from the session record, and an internal API key from the error message, all of which qualify as personal information under CCPA and must be removed before the data reaches an uncertified AI provider.

Service provider agreements and AI tools

Under CCPA, sharing personal information with an AI provider without a qualifying service provider agreement constitutes a "sale" or "share"⁴, even when no money changes hands. OpenAI, Anthropic, Google, and Microsoft offer data processing agreements for their enterprise tiers⁵, but most teams using free or standard API tiers have no qualifying agreement in place. Consequently, sending California consumer data to a standard AI API tier may violate CCPA regardless of the provider's privacy reputation. Scrubbing before transmission removes the personal information, so the shared content does not qualify as personal information under CCPA.

The practical implication for California businesses is significant: every employee who pastes customer data into a free-tier AI tool without a service provider agreement in place creates a potential CCPA violation, and the California Privacy Protection Agency has increased enforcement focus on exactly this kind of AI-related data sharing in 2026. Pre-scrubbing the personal identifiers before the prompt reaches the AI provider eliminates the violation at the source, because the AI provider receives only tokens that do not qualify as personal information under CCPA's definition.

CPRA sensitive personal information

The California Privacy Rights Act added a new category: sensitive personal information. This includes SSNs, driver's license numbers (not yet detected), account log-in credentials, precise geolocation, racial or ethnic origin, and email content (email address detected). Yet the scrubber covers the most commonly digitized sensitive fields, including SSNs, email addresses, and account credentials, which are the categories most frequently embedded in operational text pasted into AI tools.

For regulated documents containing driver's license or passport numbers, manual review is also needed because these identifiers do not follow patterns that regex can reliably detect. The CPRA also gives California consumers the right to limit how businesses use their sensitive personal information⁶, which means that even after scrubbing, organizations should document which data categories were removed and retain that documentation for compliance purposes.

CPRA's right to limit sensitive personal information and what it requires

The California Privacy Rights Act, effective January 1, 2023, added a right for consumers to limit how businesses use and disclose their sensitive personal information. Sensitive personal information under CPRA (Section 1798.121) includes SSNs, driver's license numbers, account log-in credentials combined with security codes, precise geolocation, racial or ethnic origin, religious beliefs, union membership, mail contents, genetic data, biometric information used for identification, and information about a consumer's sex life or sexual orientation.

When a consumer exercises the right to limit, businesses must stop using that consumer's sensitive personal information for purposes beyond providing the requested goods or services. Using a California consumer's SSN, account credentials, or precise location data as input to an AI tool for purposes unrelated to the service contract (such as internal analytics, product development, or model training) likely exceeds the permitted use under CPRA. Scrubbing sensitive personal information from prompts before AI submission ensures compliance with limit-use elections regardless of whether any specific consumer has yet made such an election.

Responding to a right-to-limit request under CPRA

When a California consumer submits a right-to-limit request for their sensitive personal information, your response must identify all processing of that consumer's SPI and stop using it for unauthorized purposes within 15 business days⁷. For AI workflows that have involved the consumer's SPI in previous prompts, you cannot remove that data from an external AI provider's systems retroactively. Scrubbing SPI before submission prevents this retroactive problem from arising: if the AI provider never received the SPI, no retroactive deletion request is needed and the right-to-limit obligation is satisfied by the technical control rather than by vendor negotiation.

CCPA service provider agreements and AI tool requirements

Under CCPA Section 1798.100(d), sharing personal information with a service provider requires a written contract prohibiting the service provider from retaining, using, or disclosing personal information for any purpose other than the specified business purpose⁸. Most standard-tier AI API agreements do not satisfy this requirement. OpenAI's standard API terms, Google's Gemini API terms, and Anthropic's standard Claude API terms permit the provider to use submitted data for model improvement by default. Only enterprise agreements with explicit prohibition clauses and zero-data-retention commitments qualify as service provider agreements under CCPA.

Businesses using AI APIs without a qualifying service provider agreement risk treating the data transmission as a "sale" or "share" under CCPA, which triggers consumer opt-out rights under Section 1798.120 and potential enforcement by the California Privacy Protection Agency. The CPPA increased its enforcement focus on AI-related data practices in 2026⁹. Scrubbing California consumer personal information before AI submission eliminates the sale-or-share classification for the AI interaction, because the AI provider receives only tokens that contain no personal information as defined by CCPA.

Identifying which AI provider agreements qualify as CCPA service provider agreements

Review your AI provider's Data Processing Addendum before classifying an AI tool as a CCPA service provider. The qualifying DPA must include: a prohibition on retaining personal information beyond the service period, a prohibition on using personal information for any purpose other than performing the contracted services, a prohibition on combining personal information from your business with personal information from other sources, and a certification that the provider understands and will comply with CCPA. OpenAI's Enterprise Data Processing Agreement, Google's Cloud Data Processing Addendum (for Workspace and Cloud), and Anthropic's Enterprise Privacy Agreement each address these requirements for their respective enterprise tiers.

California consumer data in marketing AI workflows

Marketing teams use AI tools heavily for campaign copy generation, audience segmentation analysis, and customer communication drafting. These tasks frequently involve California consumer data in the form of email campaign lists, contact engagement histories, and CRM segments. Uploading a campaign list to an AI tool for segmentation analysis, or using customer engagement data as prompt context for copy personalization, constitutes sharing personal information with a third-party AI provider for a marketing purpose, which CCPA Section 1798.120 covers as a consumer opt-out right.

For marketing workflows involving California consumers, apply the scrubber to email addresses, phone numbers, and any other personal identifiers in the prompt before submitting to the AI. An AI writing assistant can generate personalized campaign copy from a tokenized customer profile (customer segment, purchase history category, geographic region without street address) just as effectively as from a record with the real email and phone. Replace customer identifiers with segment descriptors before the prompt ever reaches the AI.

Filtering opted-out California consumers before AI-assisted campaigns

California consumers who have submitted opt-out requests under CCPA Section 1798.120 must be excluded from data sharing with third parties for marketing purposes. Before using a contact list in any AI tool for campaign purposes, filter out opted-out California consumers based on their declared California residence or IP geolocation. The remaining list may still require scrubbing of personal identifiers for CCPA compliance with AI providers that lack qualifying service provider agreements. Maintaining a current opt-out list in your CRM and applying it as a filter at the list export step, before scrubbing, ensures both the opt-out and data-minimization obligations are satisfied simultaneously.

Filtering and scrubbing together satisfy both the opt-out and data-minimization obligations before the prompt leaves your system. Because CapyToolkit processes the list locally in your browser, no California consumer record is uploaded to a server during scrubbing, and the tokens that result are not personal information under CCPA, which keeps the AI interaction outside the sale-or-share definition.

When to use this

Use this before sending any prompt about California residents, including customers, employees, or prospects, to an AI tool when a qualifying service provider agreement with that AI provider is not in place.

Examples

Help draft a response to Maria Garcia ([email protected], SSN 321-54-9876) who filed a DSAR under CCPA.

Help draft a response to Maria Garcia ([EMAIL_1], SSN [SSN_1]) who filed a DSAR under CCPA.

Analyze engagement patterns: user 203.0.113.5 clicked 3 times, user 198.51.100.2 bounced immediately.

Analyze engagement patterns: user [IP_1] clicked 3 times, user [IP_2] bounced immediately.