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.
CCPA/CPRA. Sensitive personal information.
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
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.
How a reviewer labels values from one retail and delivery company. A value is sensitive only when it fits a category the statute lists.
| Value | Detected type | Label | Reason | Kept or rejected |
|---|---|---|---|---|
| 900-55-0142 in hr.employees | Social Security number | Sensitive: § 1798.140(ae)(1)(A) | An employee record; area 900 is never issued | Kept |
| D1234567 in drivers.license_no | Driver’s license number | Sensitive: (ae)(1)(A) | Delivery driver onboarding; a placeholder | Kept |
| jdoe@example.com with its password column | Account log-in and password | Sensitive: (ae)(1)(B) | The users table pairs each log-in with the password that opens it | Kept |
| 4111 1111 1111 1111 with a CVV column | Card number and security code | Sensitive: (ae)(1)(B) | A processor test card stored beside its code | Kept |
| 37.7793, -122.4192 in trips.pickup | Precise geolocation | Sensitive: (ae)(1)(C) | From the driver’s phone; locates a person well inside 1,850 feet | Kept |
| Type 2 diabetes in wellness.notes | Health information | Sensitive: (ae)(2)(B) | Collected and analyzed in an employer wellness program outside HIPAA | Kept |
| 94103 in leads.zip | ZIP code | Personal information, not sensitive | Typed into a form, not derived from a device, and covers a whole area | Rejected |
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.
| Section | What it requires | Time limit or amount | Record 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 collection | The notice at collection, matched to a dated scan of the categories each system holds |
| §§ 1798.110 and 1798.115: right to know | Disclose 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 correct | Delete 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 days | Receipt and confirmation dates, the systems changed, and who confirmed each change |
| § 1798.120 and § 1798.121 | Honor 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.150 | Reasonable 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 assessments | Assess 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, 2028 | The dated assessment, naming the categories, the systems it covers and who approved it |
| 11 CCR §§ 7120–7124 cybersecurity audits | An 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.90 | Administrative 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 |
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 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.
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.
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)).
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.
| Item | Status | Instrument |
|---|---|---|
| Regulators | California Privacy Protection Agency (CalPrivacy) and the Attorney General | Civil Code § 1798.155 and § 1798.199.90 |
| CPRA amendments | In force; operative since January 1, 2023 | Proposition 24 (2020) |
| Audit, risk assessment and ADMT regulations | In force since January 1, 2026; compliance dates run to 2030 | OAL approval of September 22, 2025 (11 CCR) |
| Next scheduled changes | January 1, 2027: ADMT duties apply (§ 7200(b)); browsers must offer an opt-out preference signal | § 1798.136(f) |
| SB 923, signed September 27, 2026 | From January 1, 2027: deletion covers data collected about a consumer, and online-only firms need an online request form | SB 923, amending §§ 1798.105 and 1798.130 |
| Amounts | CPI-adjusted from January 1, 2025; the next adjustment is due in an odd year, January 1, 2027 | § 1798.199.95(d) |
| Review | Editorial review by Sylox; not reviewed by a lawyer | Last reviewed November 8, 2026 |
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 evidenceA 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.
Search every database for one person, and keep the record of what you searched.
How US, UK, EU, Gulf and Indian laws define personal data, and which term to use.
Evidence on sensitive data that traces to a source, table and scan date.
Yes. IRIS maps findings to CCPA/CPRA controls and shows where evidence for each is present, missing or deferred. Your auditor decides whether a control is met.
Yes, it logs them and runs the search. IRIS searches connected databases for the consumer; your team makes the deletion or correction in the source system. Capabilities vary by edition.
No. Opt-out and preference-signal handling sit in your consent or web stack. IRIS can show which systems hold the data an opt-out has to reach.
IRIS maps its evidence to other US state privacy law controls through its unified compliance framework, and it supports your own assessment. A scored readiness view for other state laws isn’t in v1; ask us if you need one.
Find the sensitive categories in one system: a free assessment scans one database with a read-only login you create.