the-fine-printdeletionfederal-privacydata-brokersprivacy

The Fine Print: When the Record Becomes the Proof

Ben TobinUpdated 5 min read

The Fine Print is a twice-weekly series that reads privacy law from the consumer's side: what a word promises, what the text says, and what is left exposed.

Most of this series reads California law. This week's text is a federal proposal, because one sentence in it answers a question the series keeps asking: when a company says your data is deleted, what counts as proof?

What the word promises

H.R. 8413, the SECURE Data Act, was introduced in the House on 21 April 2026 and referred to the Committee on Energy and Commerce and the Committee on the Judiciary. That referral is the latest action on the official bill-status record (govinfo bill status). It is a proposal. Nothing in it is law.

As introduced, the bill gives a consumer the right "To delete personal data provided by or obtained about the consumer" (§2(a)(3), introduced text). "Obtained about" matters. On its face, it reaches data a company got from someone else, not only what you handed over. The bill would also have the Federal Trade Commission maintain "a searchable, central registry of data brokers" (§5(c)). Both are real promises.

What the text says

The key sentence is §2(d)(5), headed "Personal data obtained from third party." A controller that got your data "from a source other than the consumer is considered to be in compliance with the request of a consumer ... to delete that personal data" by either:

"(A) retaining a record of the deletion request and the minimum data necessary for the purpose of ensuring the personal data of the consumer remains deleted from the records of the controller and not using the retained data for any other purpose under this Act; or (B) opting the consumer out of the processing of that personal data for any purpose other than a purpose that is exempt under the provisions of this Act."

So for data that came from somewhere else, the record of your request counts as compliance. So does an opt-out.

What stays exposed

An opt-out would count as a deletion. Option (B) doesn't require removing anything. The data could stay on file, provided it isn't processed for purposes the bill doesn't exempt. California keeps those two outcomes apart. Under the Delete Act, a request a broker can't verify is processed "as an opt-out of the sale or sharing of the consumer's personal information" (Civ. Code §1798.99.86(c)(1)(B), leginfo), and DROP reports "opted-out" as a status of its own, separate from "deleted" (CalPrivacy, DROP FAQ, 6 October 2026, Question 7). Under §2(d)(5), for data that came from a third party, both outcomes would count as complying with a deletion request. Why that difference matters to a consumer is in Your DROP Status, Decoded.

The record is kept by the party it vouches for. Option (A) makes the controller's own record the proof of the controller's own compliance. Nothing in §2(d)(5) asks anyone else to look at that record, or to test whether the data stayed deleted. The word "audit" doesn't appear in the introduced text. California's statute takes a different route: "Beginning January 1, 2028, and every three years thereafter, a data broker shall undergo an audit by an independent third party to determine compliance with this section" (§1798.99.86(e)(1)). That check has limits of its own. The report goes to the Agency "within five business days of a written request" (§1798.99.86(e)(2)), not as a routine filing. (The Agency's proposed audit rules are covered in an earlier post.) But it is an outside check. §2(d)(5) builds in none.

A request that can't be confirmed can simply stop. "If a controller is unable to authenticate a consumer who submits a request ..., the controller is not required to comply with such request," though it "may request that the consumer provide additional information" (§2(d)(4)). California's DROP section turns an unverifiable deletion request into an opt-out instead of setting it aside (§1798.99.86(c)(1)(B)).

State rules would give way. Section 15 says no State may "prescribe, maintain, or enforce any law ... if such law ... relates to the provisions of this Act." On its face that language is broad. How far it would reach is a question for Congress and the courts, and we don't try to answer it here.

The case the other way

There is a fair case for §2(d)(5)(A).

Staying deleted needs a memory. A company that keeps nothing about you can't recognize your data when it arrives again from a new source. California's law depends on the same idea. After a deletion, a broker "shall delete all personal information of the consumer at least once every 45 days" (§1798.99.86(d)(1)), and CalPrivacy tells consumers that brokers "must continue to check your information against their records as they acquire more data" (DROP FAQ, Question 8). A minimal record, used only for that job, is how a deletion stays in place. Option (A) says exactly that, and it bars any other use of the retained data.

Enforcement is not missing. The bill would treat a violation as an unfair or deceptive practice enforced by the FTC (§12(a)), and §12(b) provides for actions by the States. And option (A) has its own terms: a company that kept the record but went on using the data would not be meeting them.

A registry anyone can search would help. A searchable federal list of data brokers (§5(c)) would tell a consumer where to send a request in the first place.

A fix anyone could carry out

  • For Congress, if the bill moves: keep (A) and (B) apart in what the consumer is told. A response under (B) should say "opted out," not "deleted."
  • For Congress: make the retained record checkable. §2(d)(3)(C) already has controllers "demonstrate, document, and provide to the Commission or a State attorney general, upon request" why a request they charged for or declined was infeasible or unfounded. The same could apply to (A) records, together with a periodic outside test of whether deleted data stays deleted.
  • For state agencies and legislatures: whatever happens federally, keep reporting deletions and opt-outs as separate outcomes, as DROP does now.
  • For you: when a company says it has handled your deletion request, ask whether it deleted the data or opted you out. Keep its answer with the date. The same habit helps with the copies a company already passed on (The Copies Already Sold).

For the wider question of who checks a reported status, see our working paper, Who Verifies the Status?


Sources, read 6 November 2026: H.R. 8413 (119th Congress), introduced text and bill status on govinfo.gov, §§2(a)(3), 2(d)(3)(C), 2(d)(4), 2(d)(5), 5(c), 12 and 15; Cal. Civ. Code §1798.99.86 on leginfo.legislature.ca.gov, subdivisions (c)(1)(B), (d)(1) and (e); CalPrivacy, DROP FAQ: 10 Common Questions about DROP (6 October 2026), Questions 7 and 8.

Follow Sirveil on LinkedIn: https://www.linkedin.com/company/133457181 · Follow @Sirveil_AI on X.

Disclosure: Sirveil builds privacy verification tools, so we have a commercial interest in this subject.

Sirveil for business: sirveil.ai/for-business

NONE OF THIS CONSTITUTES LEGAL ADVICE.

Share this article

PostShare

Get privacy insights delivered

One email a month: privacy-law changes, data-broker news, and what’s new at Sirveil. No spam, unsubscribe in one click.

Start protecting your personal data

Scan, verify, remove: Sirveil finds where brokers list you, you confirm which entries are yours, and your takedown requests are prepared, transmitted, and chased on your behalf — tracked end to end.

Get Sirveil

Available now on the App Store and Google Play.