Cookie settings

Necessary, always on: they keep the site working and remember your cookie choice.

Skip to content
Skip to content

CCPA/CPRA. Sensitive personal information.

CCPA sensitive personal information, mapped to where it sits

A CCPA inventory matches the notice at collection to what your systems hold, one sensitive category at a time under § 1798.140(ae).

By Dipal Panchal, co-founder and CEO · Last reviewed: November 8, 2026

Overview

Which businesses the CCPA covers

The California Consumer Privacy Act covers for-profit businesses that do business in California and meet one threshold in § 1798.140(d). The revenue threshold is $26,625,000 in the preceding year, as adjusted from January 1, 2025 under § 1798.199.95(d).

The other thresholds: buying, selling or sharing the personal information of 100,000 or more consumers or households a year, or earning half of annual revenue from selling or sharing it. The California Privacy Rights Act amendments have applied since January 1, 2023.

The California Privacy Protection Agency, which now calls itself CalPrivacy, and the Attorney General bring enforcement actions. This page is general information, not legal advice.

  • California residents count as consumers, employees included
  • HIPAA and CMIA medical data are exempt (§ 1798.145(c))
  • GLBA-covered financial data is exempt (§ 1798.145(e))
  • Other US state privacy laws aren’t covered here

Seven values, read against § 1798.140(ae)

How a reviewer labels values from one retail and delivery company. A value is sensitive only when it fits a category the statute lists.

Records
ValueDetected typeLabelReasonKept or rejected
900-55-0142 in hr.employeesSocial Security numberSensitive: § 1798.140(ae)(1)(A)An employee record; area 900 is never issuedKept
D1234567 in drivers.license_noDriver’s license numberSensitive: (ae)(1)(A)Delivery driver onboarding; a placeholderKept
jdoe@example.com with its password columnAccount log-in and passwordSensitive: (ae)(1)(B)The users table pairs each log-in with the password that opens itKept
4111 1111 1111 1111 with a CVV columnCard number and security codeSensitive: (ae)(1)(B)A processor test card stored beside its codeKept
37.7793, -122.4192 in trips.pickupPrecise geolocationSensitive: (ae)(1)(C)From the driver’s phone; locates a person well inside 1,850 feetKept
Type 2 diabetes in wellness.notesHealth informationSensitive: (ae)(2)(B)Collected and analyzed in an employer wellness program outside HIPAAKept
94103 in leads.zipZIP codePersonal information, not sensitiveTyped into a form, not derived from a device, and covers a whole areaRejected
Requirements

Each duty, its time limit and its record

The first three columns are the statute and agency regulations, pinpointed. The last is our advice on the record to keep: date, owner and source system.

Each duty, its time limit and its record
SectionWhat it requiresTime limit or amountRecord that shows it
§ 1798.100(a) and (c)At collection, say which categories you collect, why and for how long; keep use necessary and proportionate.At or before the point of collectionThe notice at collection, matched to a dated scan of the categories each system holds
§§ 1798.110 and 1798.115: right to knowDisclose the categories and the specific pieces of personal information collected about the consumer.Forty-five days from receipt, extendable once by forty-five more with notice (§ 1798.130(a)(2))A search record per request: received and answered dates, systems searched, what was found
§ 1798.105 delete and § 1798.106 correctDelete or correct on a verifiable request, and pass the request to service providers and contractors.Confirm receipt within ten business days (11 CCR § 7021); answer within the same forty-five daysReceipt and confirmation dates, the systems changed, and who confirmed each change
§ 1798.120 and § 1798.121Honor requests to opt out of sale or sharing, and to limit the use of sensitive personal information.No later than fifteen business days from receipt (11 CCR §§ 7026 and 7027)A dated log per consumer, and the systems each request reached
§ 1798.100(e) and § 1798.150Reasonable security for personal information; consumers can sue over breaches of nonencrypted, nonredacted data.Statutory damages of $107 to $799 per consumer per incident (§ 1798.150(a)(1)(A))Dated, scoped checks of each store’s protection state, repeated through the year
11 CCR §§ 7150–7157 risk assessmentsAssess processing that presents significant risk, including processing sensitive personal information (§ 7150(b)(2)).Before processing starts (§ 7150(a)); processing begun before 2026: by December 31, 2027; submit by April 1, 2028The dated assessment, naming the categories, the systems it covers and who approved it
11 CCR §§ 7120–7124 cybersecurity auditsAn audit where § 7120(b) applies, such as revenue over the threshold plus 50,000 or more consumers’ sensitive data.First report April 1, 2028, 2029 or 2030, set by revenue (§ 7121)The dated audit report, naming the auditor, and the asset inventory it relies on
§ 1798.155 and § 1798.199.90Administrative fines from the agency, or civil penalties in an Attorney General action.Up to $2,663 per violation, or $7,988 if intentional or involving known minors under 16 (§ 1798.155(a))Not a record: the amount applies to each violation
Questions

Four calls the statute settles

Is a ZIP code precise geolocation?

No. Precise geolocation is device-derived data that locates a consumer within a circle of 1,850-foot radius (§ 1798.140(w)). A typed ZIP code isn’t; phone GPS coordinates are.

When is a password field sensitive?

When it sits with the log-in it opens (§ 1798.140(ae)(1)(B)). A users table holding both counts; a password column with no log-in beside it isn’t that combination.

Does payroll need a risk assessment?

No, when employee sensitive data is used only for pay, benefits, work authorization, accommodation or wage reporting (11 CCR § 7150(b)(2)(A)). Any other use of it does.

What should a first review ask?

Two yes-or-no questions, as I put them: is there an inventory of your data, and do you hold children’s data? Under 16, selling or sharing needs opt-in consent (§ 1798.120(c)).

Timeline

Status on November 8, 2026

Checked on cppa.ca.gov, privacy.ca.gov and leginfo.legislature.ca.gov on November 8, 2026. Next review on January 2, 2027, after the January 1 changes.

Status on November 8, 2026
ItemStatusInstrument
RegulatorsCalifornia Privacy Protection Agency (CalPrivacy) and the Attorney GeneralCivil Code § 1798.155 and § 1798.199.90
CPRA amendmentsIn force; operative since January 1, 2023Proposition 24 (2020)
Audit, risk assessment and ADMT regulationsIn force since January 1, 2026; compliance dates run to 2030OAL approval of September 22, 2025 (11 CCR)
Next scheduled changesJanuary 1, 2027: ADMT duties apply (§ 7200(b)); browsers must offer an opt-out preference signal§ 1798.136(f)
SB 923, signed September 27, 2026From January 1, 2027: deletion covers data collected about a consumer, and online-only firms need an online request formSB 923, amending §§ 1798.105 and 1798.130
AmountsCPI-adjusted from January 1, 2025; the next adjustment is due in an odd year, January 1, 2027§ 1798.199.95(d)
ReviewEditorial review by Sylox; not reviewed by a lawyerLast reviewed November 8, 2026
With IRIS

CCPA/CPRA is one of the frameworks IRIS scores, and IRIS doesn’t certify compliance. Mapping shows relevance; your auditors judge whether a control is met.

§ 1798.140(ae): where each sensitive category sits: IRIS produces part of this, for the sources you connect and the data types IRIS detects, such as SSNs and card numbers.

§§ 1798.110 and 1798.105: the search behind a request: IRIS produces part of this, connected databases only, not files or mailboxes; the change happens in the source system.

§ 1798.100(e): how stored sensitive values are protected: IRIS produces part of this, checks sampled values for encryption, masking or hashing, once activated on your install.

§ 1798.100(e): who can reach each sensitive dataset: IRIS produces part of this, where the source exposes permission data.

§ 7120 audits: which sources a scan covered and couldn’t read: IRIS produces this.

CCPA/CPRA controls: where evidence is present, missing or deferred: IRIS produces this.

Explore evidence

Match your notice to your systems

A check we recommend; the statute sets no method for it. Then use the guide to requests across databases to test whether you can answer one.

1. List the sensitive categories your notice names

Owner
Privacy lead
Tool or path
Your notice at collection and privacy policy
Expected output
Each § 1798.140(ae) category you say you collect, with the purpose and retention period.
How to verify
Every category in the notice has a named business owner.

2. Find those categories in each system

Owner
Data platform lead
Tool or path
A discovery scan, or column and value queries run by each system’s administrator
Expected output
Tables and files holding each category, with the date found.
How to verify
The search covered your asset inventory and cloud accounts, not only the systems on the list.

3. Compare the two lists

Owner
Privacy lead, working with each system owner
Tool or path
Your data inventory spreadsheet
Expected output
Categories found but not in the notice, and categories in the notice found nowhere.
How to verify
Each mismatch has a decision: update the notice, delete the data or record why it stays.

4. Search again after the changes

Owner
Data platform lead
Tool or path
The step 2 method, run again
Expected output
A second dated search showing each mismatch closed or still open.
How to verify
The new search postdates every change, and open items carry an owner and a date.

The official texts behind each cell

  1. Civil Code § 1798.140, definitions, including (ae) sensitive personal information and (w) precise geolocation, California Legislative Information. Opened November 7, 2026.
  2. Civil Code § 1798.130, response time limits, California Legislative Information. Opened November 7, 2026.
  3. Civil Code § 1798.155, administrative enforcement, California Legislative Information. Opened November 7, 2026.
  4. SB 923 (2025–2026), deletion request records and request submission methods, Chapter 482, California Legislative Information. Opened November 8, 2026.
  5. Updated monetary thresholds in the CCPA, effective January 1, 2025, California Privacy Protection Agency. Opened November 7, 2026.
  6. CCPA updates, cybersecurity audits, risk assessments and ADMT regulations, effective January 1, 2026, California Privacy Protection Agency. Opened November 7, 2026.
FAQ

IRIS and the CCPA, in four answers

Protect your brand. Start with your data.

Find the sensitive categories in one system: a free assessment scans one database with a read-only login you create.