The disclosure that only looked back 90 days.
Section 1798.110 gives a consumer the right to know the categories and specific pieces of personal information a business holds about them: the categories collected, the sources, the business purposes, and the categories of third parties it discloses personal information to. Section 1798.130 sets how that right is exercised: the response covers the 12-month period preceding the request, at least two designated methods to submit a request (a toll-free number among them; a business that operates exclusively online and deals directly with the consumer may offer just an email address), no account creation required, no charge, and a response within 45 calendar days (one 45-day extension with notice, 90 days total). What the consumer actually receives is whatever the disclosure handler's own query returns, and that query is code with its own window and its own joins.
The shapes the same control failure takes.
The gap is rarely a refused request. It is a disclosure response that quietly covers less than the statute requires. The recurring shapes:
The lookback window is narrowed
The 12-month window the disclosure query filters on is shortened, usually for a performance or pagination reason, so recent data exists but the response understates it.
A required category is dropped from the response
The payload sent back to the consumer stops including one of the required categories, such as sources or third parties disclosed to, while the underlying data is still collected.
Specific pieces collapse into category labels
The response is rewritten to return only the category a field falls into, not the actual value collected, so the consumer sees 'identifiers' instead of the email address itself.
A required intake channel is removed
The toll-free number, the web form, or, for an online-only business, the email address, is removed or quietly disabled, leaving fewer methods than the business is required to offer.
The request is gated behind a new account
A verification step is added that requires creating an account the consumer did not already have, which the statute does not allow as a condition of submitting the request.
A disclosure query's window, shortened for pagination.
The right-to-know handler was slow on accounts with a lot of history, so a change adds pagination and, while rewriting the query, swaps its 12-month filter for a 90-day one to match the new default page. The endpoint still returns 200, just with the most recent three months instead of the full twelve.
function disclosureWindow() {- return subMonths(new Date(), 12);+ return subDays(new Date(), 90);}This narrows the disclosure window from 12 months to 90 days. § 1798.130 sets the disclosure to cover the 12 months preceding the request, across the categories § 1798.110 lists. A pagination fix should not change what window the underlying query covers. Keep the 12-month filter and paginate within it, rather than shrinking the window to fit the page.
What a privacy reviewer would verify
A privacy review compares what the disclosure handler actually returns against the required categories and the 12-month window, and checks that the designated submission methods still work without an account. A diff that changes the query's date filter, collapses a specific value into its category label, or removes an intake channel is the concrete gap behind an incomplete disclosure, and it is visible before the request ever gets submitted.
A review, not a fulfillment desk.
A pull-request review can identify a narrowed window, a dropped response field, or a missing submission method in the handler's own code. It cannot determine whether CCPA applies to the business, whether a request was verifiable, or whether the 45-day clock was met in practice. Select CCPA in org config if you want this duty reviewed. These pages are illustrative.