LATEST ARTICLES Breaking archive
Tuesday, November 10, 2026 · Your local date
Wade Bush
Apps, plugins & creator toolsPractical digital products, instant access. Built by WadeBush.
Visit marketplace

California data broker delete requests are live — what marketers must change now

Original editorial image for California data broker delete requests are live — what marketers must change now

California data broker delete requests are now live and flowing through the state’s Delete Request and Opt-out Platform, known as DROP. If your growth stack relies on purchased audiences, enrichment, or lookalike modeling, this change touches your targeting, suppression, and vendor management immediately.

What changed — and why it matters to marketers

DROP lets a California resident send one deletion request that lands with every registered data broker. When a broker finds a match, it must delete the person’s data, including inferences, and keep it deleted going forward except where a legal exemption applies. That means records your team bought last quarter can become non‑compliant overnight, and any repopulation by a broker after a valid delete can expose your company to risk. Treat these requests like hard bounces for privacy: they must propagate across your tools, partners, and backups.

Key dates and operational obligations

The agency launched DROP at the start of the year. By August 1, 2026, data brokers were required to check the platform on a set cadence and process new deletion files. After a match, they must complete deletion within 45 days, and they must send the order downstream to any service providers or contractors holding the same data. For marketers, the practical takeaway is timing: your suppression and audience refresh cycles should not reintroduce deleted profiles within that 45‑day window or after.

Who is a “data broker” — and who is not

Under California law, a data broker is a business that knowingly collects and sells or shares personal information about consumers with whom it does not have a direct relationship. Consumer reporting agencies covered by the Fair Credit Reporting Act, entities processing data only from their direct customers, and certain nonprofits fall outside the definition. Many marketing vendors do qualify, though, including list providers, third‑party enrichment services, and cross‑device graph vendors. If you buy audience segments or license identity data, expect your suppliers to be on the registry and in scope for DROP.

How California data broker delete requests flow through DROP

DROP uses hashed identifiers (like emails or phone numbers transformed using a one‑way function) to help brokers match records without overexposing raw data. When a person signs up, the system packages their identifiers into deletion instructions visible to registered brokers. A broker that finds a match must remove the linked profile, inferences, and associated IDs; stop future collection from third parties for that consumer; and instruct its service providers to do the same. If no match is found, the broker documents the outcome but cannot keep extra data simply because a request arrived.

Five immediate adjustments for growth and CRM teams

  • Refresh suppression logic. Build a dedicated, non‑overwritable suppression table for DROP‑driven deletes. Treat it as authoritative across CRM, ESP, CDP, ad platforms, and warehoused audience exports.
  • Shorten audience recency. Pull smaller, fresher extracts from brokers so deletions are less likely to slip back in. Avoid “evergreen” audience files that persist across quarters.
  • Re‑score lookalikes. If a meaningful share of seed data disappears due to deletes, rebuild lookalike models and move evaluation to post‑privacy performance metrics, not only lift on the original seed.
  • Harden identity joins. Prefer consented, first‑party identifiers for stitching. Where third‑party IDs remain, require brokers to publish their DROP compliance cadence and provide deletion confirmation logs.
  • Tighten incident playbooks. If a deleted profile reappears in a send or campaign, pause sends to the impacted segment, quarantine the source feed, and request broker remediation evidence before resuming.

Contract terms your legal and procurement teams should add

Update broker MSAs and order forms to reflect DROP realities. Require vendors to:

  • Access DROP on the legally required cadence and certify processing within the 45‑day clock.
  • Propagate deletes to all subprocessors and service providers handling your licensed data.
  • Provide machine‑readable deletion receipts and ongoing suppression lists you can import.
  • Disclose the number of consumer requests received and fulfilled, and publish that metric annually in their privacy policy as required by law.
  • Notify you within a set number of days if a deletion failure results in repopulation to your systems, and to remediate at their expense.

How this changes your data acquisition strategy

Expect smaller, more volatile third‑party audiences. Budget for more frequent refreshes and for a shift toward first‑party collection with explicit consent. Where third‑party data still drives value—B2B contact acquisition, for example—pilot vendors that demonstrate high match quality without overcollection. Also, monitor your performance KPIs for signs of silent shrinkage, such as drops in modeled reach or increased audience churn between refreshes.

Exemptions and edge cases you will encounter

Deletes do not apply where keeping data is legally required, such as for security, debugging, or legal claims. Brokers can deny a request when they cannot reasonably authenticate identity. Your team will still feel the impact: even when one broker claims an exemption, another may process a delete for the same consumer, producing uneven audience coverage. Maintain documentation of exemptions from vendors and treat exempted profiles cautiously in sensitive campaigns.

Marketing analytics and attribution implications

Audience sizes will move more than usual around suppression events. Build reporting that marks when bulk DROP files arrive to explain week‑over‑week swings. For multi‑touch attribution based on cross‑device graphs, expect more fragmentation as brokers purge identifiers. Test cohort‑based reporting that relies less on persistent third‑party IDs and more on session‑ or event‑level telemetry from your owned properties.

Governance: the checklist to finish this week

  • Identify every system where broker‑sourced data lands. Map flows into your warehouse, CDP, ESP, retargeting, and enrichment jobs.
  • Create a single import for vendor‑provided deletion receipts, and propagate across systems.
  • Set automated alerts if a vendor file introduces any identifier on your suppression list.
  • Revise privacy notices to describe how you handle third‑party deletes, including how customers can re‑opt‑in when appropriate.
  • Train your media, lifecycle, and data engineering teams on the new obligations and playbooks.

How to evaluate vendors going forward

Ask for proof, not promises. A strong vendor will show registry status, access logs demonstrating timely DROP checks, deletion success rates, explanatory notes on denials, and evidence of downstream propagation to subprocessors. They should also publish required annual request metrics and maintain a named contact for remediation. Pilot using a canary segment and compare lift and complaint rates before full rollout.

Bottom line

DROP compresses the window between a consumer’s decision and the disappearance of their profile from third‑party marketing data. That is good for trust—and a forcing function for better data hygiene. Treat California data broker delete requests as a standing constraint in your growth model, shore up contracts and pipelines, and you can keep acquisition efficient while staying on the right side of the line.

Sources

Featured image: Wade Bush, Original AI-generated editorial image