Skip to content

DROP deadlines and how the clock counts

Until 31 December 2026 a data broker must download from DROP at least every 45 calendar days and report every work item within 45 days of the download. The download day is day 0, so a batch downloaded on 1 October is due by 15 November. From 1 January 2027, AB 883 moves downloads to every 30 days.

Last reviewed 22 November 2026

Two clocks, not one

DROP puts two separate time limits on a broker, and they are easy to blur:

  1. The access clock. You must access DROP and download your lists at least once every 45 calendar days (Civil Code § 1798.99.86(c)(1); 11 CCR § 7612(a)). This started on 1 August 2026.
  2. The reporting clock. For each batch you download, CalPrivacy asks you to process every work item and report its status within 45 days of the download.

The two are tied together by one rule in the regulations: you report a batch's statuses before you download the next one (11 CCR § 7614(c)). DROP enforces this. While any work item in the open batch has no accepted status, the next download is refused. So a batch you have not finished blocks the access clock too.

In practice the safe plan is simple: finish and report each batch well inside 45 days, then download the next one straight away. You may download as often as you like; CalPrivacy says there is no limit on the number of batches in a cycle.

How the days count

CalPrivacy's processing page says the clock starts the day after you finish downloading a batch. Put another way, the download day is day 0 and the next day is day 1. CalPrivacy's June 2026 webinar gave a worked example: a batch downloaded on 1 October can be reported on 15 November, and 16 November is late.

  • The days are calendar days. Weekends and public holidays count.
  • “Completely download” matters. Through the API, the first call only asks DROP to build the package; the clock starts when the ZIP has actually arrived.
  • Use one time zone for your records. DROP is a California system, so keeping dates in Pacific time avoids an off-by-one when a download happens late in the evening.

One caution on the very first deadline. Counting from 1 August 2026 as day 0 gives 15 September, but a CalPrivacy webinar slide reportedly put the first download date at 14 September. Where two official readings differ by a day, plan to the earlier one.

Worked dates

These use day 0 as the download day. The last column shows the conservative date our tools use once a 45-day window would end in 2027; the reasons are in the next section.

DownloadedDay 45Day 30Date we plan to
1 October 202615 November 202631 October 202615 November 2026
16 November 202631 December 202616 December 202631 December 2026
20 November 20264 January 202720 December 202620 December 2026
15 December 202629 January 202714 January 202714 January 2027
10 January 2027(not used)9 February 20279 February 2027

The deadline calculator does this for any date, including both the report-by date and the latest next download.

The change on 1 January 2027

AB 883 was signed in September 2026. CalPrivacy's own pages state that, beginning 1 January 2027, data brokers must download their lists at least once every 30 days. Proposed regulations published on 13 November 2026 would also set 30 days to process and report a batch, but those are not final.

Two questions are not answered by anything CalPrivacy has published so far:

  • Whether the reporting window, and not only the download interval, becomes 30 days on 1 January 2027.
  • How a batch downloaded in late 2026, whose 45-day window would end in 2027, is treated.

Until CalPrivacy says otherwise, the cautious reading is to treat any window that would end on or after 1 January 2027 as 30 days. That is what our tools do: with it, a batch downloaded from 17 November 2026 onwards gets a 30-day date. If the 45-day reading turns out to be right, you will simply have finished early. The detail is in AB 883 and the 30-day cycle.

Other dates to diary

WhenWhatBasis
Next access after a changeReport a changed status (for example 5 to 3 after you acquire new data) through the amend route.11 CCR § 7614(a)(1)
Within 45 days of last accessIf your API connection fails through no fault of yours, notify CalPrivacy in writing and download manually.11 CCR § 7612(b)(1)
1 to 31 JanuaryAnnual data broker registration and fee.Civ. Code § 1798.99.82
By 1 JulyPublish the previous year's request metrics, including median and mean days to respond.Civ. Code § 1798.99.85
From 1 January 2028Independent audit, then every three years; report handed over within 5 business days of a request.Civ. Code § 1798.99.86(e)

Amending a status does not restart the clock on the original batch.

If you miss a date

The Delete Act sets an administrative fine of $200 for each deletion request for each day the broker fails to comply, plus the costs of the investigation. Because the fine counts requests, not batches, a late batch of a few thousand work items is a large figure within days. Report what you have as soon as you can; every day counts separately. The penalty calculator shows the arithmetic, and Delete Act penalties covers how enforcement has worked so far.

Planning a cycle

  • Pick a fixed download day well inside the window, for example every 21 days, so a bad week does not become a late batch.
  • Set reminders for day 0, the halfway point and a week before the report-by date, sent to more than one person.
  • Leave room for DROP's row validation. Rejected rows must be fixed and uploaded again before the batch is complete.
  • Record the exact download time, not just the date. The evidence log is what shows an auditor you were on time.

CalDrop Compliance counts both clocks for every batch and emails the team before each date. See it in the demo.

Questions

When does the DROP 45-day clock start?

On the day after you finish downloading the batch. The download day is day 0, so a batch downloaded on 1 October 2026 must be reported by 15 November 2026; 16 November is late.

How often must a data broker download from DROP?

At least once every 45 calendar days from 1 August 2026, and at least once every 30 days from 1 January 2027 under AB 883. You can download more often.

Do weekends count towards DROP deadlines?

Yes. The deadlines are in calendar days, so weekends and public holidays count.

Can I download a new batch before I finish the last one?

No. DROP refuses a new download while the open batch still has work items without an accepted status, and the regulations ask you to report before downloading a new list.

What happens to a batch downloaded in December 2026?

CalPrivacy has not said. The cautious reading is to finish it within 30 days if a 45-day window would end in 2027. Our tools use that reading.

Does amending a status restart the deadline?

No. Amending a status already accepted by DROP does not restart the clock on the original batch.

Sources

  1. CalPrivacy: Processing DROP requests
  2. CalPrivacy: DROP for data brokers
  3. DROP regulations, 11 CCR §§ 7600–7622 (PDF)
  4. California Civil Code § 1798.99.86
  5. CalPrivacy: Data brokers (penalties)
  6. CalPrivacy: DROP audits

Written by the CalDrop Compliance team at Preptics LLC and last reviewed 22 November 2026. This guide explains the rules; it is not legal advice. CalDrop Compliance is an independent product of Preptics LLC. It is not affiliated with, endorsed by or operated by the State of California or the California Privacy Protection Agency (CalPrivacy).