Double opt-in feels like good hygiene. Someone submits a form, you email a link, they click it, and only then do you act. It is how most teams build newsletter sign-ups, so it is how many teams build the privacy request page. California's privacy regulator fined Ford Motor Company $375,703 in 2026 for doing exactly that to opt-outs of sale and sharing. The screen that cost them said "One More Step!"
The California Privacy Protection Agency (CPPA, which now brands itself CalPrivacy) found that Ford's confirmation step turned an opt-out into something the regulations forbid: a verifiable consumer request. Ford did not intend that, and the order says so. It did not matter. This post reads the order as a build spec for anyone who ships a request form to California users. It is a builder's read, not legal advice, and counsel decides what applies to you.
What did California find in the Ford order?
The case is In the Matter of Ford Motor Company, Case No. ENF23-V-FO-3. Ford and the CPPA Enforcement Division signed a stipulated final order on 17 February 2026, the Board adopted it on 27 February 2026, and CalPrivacy announced it on 5 March 2026. The order says the case grew out of a general inquiry into vehicle manufacturers' privacy practices, and the relevant period is 1 July 2023 to 1 March 2024.
Ford ran a consumer privacy rights form on ford.com. A consumer chose a request type, filled in name, address, phone number and relationship to Ford, passed a reCAPTCHA, and clicked submit. Then, in the order's words, the page said "One More Step! Please confirm your request!" and told them to check their email and "click confirm and we will start your request."
The email repeated the request details and said: "For us to complete this request, you must confirm your email and identity by clicking on the button below." The order then records what happened to everyone who did not click. Ford "deemed as 'expired' all requests to opt-out of sale/sharing submitted by consumers who did not click 'Confirm Email.'" That left dozens of opt-outs unprocessed within the time the CCPA requires, and Ford kept selling or sharing those consumers' personal information. It processed them only after the investigation.
Why is an email confirmation a verifiable request?
Section 7026(d) of the CCPA regulations says a business may not require a verifiable consumer request for an opt-out of sale or sharing. It may ask for information necessary to identify whose data should stop being sold or shared, but "to the extent that the business can comply with a request to opt-out of sale/sharing without additional information, it shall do so." The order is explicit that delete, know and correct requests are different. For those, a business may require verification.
Ford's argument, in effect, was that a click on an emailed link is not an identity check. The Board disagreed. Paragraph 37 says Ford's practice "of requiring consumers to confirm their access and control over their email address before processing a request to opt-out of sale/sharing impermissibly required consumers to submit a verifiable consumer request." Proving you control an inbox is verification, even if you never use the word.
The order records two violations from the same fact pattern:
| Violation | Law | What the order says |
|---|---|---|
| Required a verifiable request to opt out | Regulation section 7026(d) | A violation each time Ford required one |
| Kept selling or sharing after the opt-out was submitted | Civil Code section 1798.120(d) | A violation each time it later sold or shared that consumer's data |
The second row is the one engineers should sit with. Ford could have processed those requests from what the form already collected, and the order says so (paragraph 30). The delay was a design decision, so the continued sale was a consequence of the design.
What does this look like in a real request flow?
Picture a 25-person SaaS company with a privacy page built for deletion requests two years ago. Every request type goes through the same pipeline: form, confirmation email, then a ticket created in the support tool when the user clicks. A background job closes tickets still unconfirmed after seven days, to keep the queue clean. Nobody thinks of it as a policy. It is a tidy workflow.
For delete, know and correct requests that pipeline is defensible. For an opt-out it contains the Ford defect twice: the confirmation gate, and the silent expiry. The expiry job is the part to find first, because it is what turns a delay into an unprocessed opt-out that nobody will ever look at again.
Run the audit by request type:
| Request type | Confirmation gate before acting? | Silent expiry of unconfirmed requests? |
|---|---|---|
| Opt out of sale or sharing | No (section 7026(d)) | No: every submission is an instruction |
| Delete, know, correct | Allowed, if bounded by data minimization | Allowed, but tell the person what happened |
What should you build instead?
The order's remedy reads as a short list (paragraphs 50 to 52). Ford had to provide opt-out methods that are "easy and require minimal steps," stop requiring verifiable requests for opt-outs, and honor each opt-out to the extent it can within the CCPA's time limit. It also had to audit the tracking technologies on ford.com, such as cookies, web beacons and pixels, to confirm each honors opt-out preference signals like the Global Privacy Control where section 7025 requires it. Ford had 90 days to complete that and confirm in writing, and 30 days to pay.
Translated into a flow:
- 1.Branch on request type at submit. The opt-out branch acts on the form data it already has. No second step.
- 2.If you send an email, make it a receipt. The order faults gating, not email. A message that says "we received your opt-out and have applied it" is a different thing from one that says "confirm to proceed." That is our reading of paragraph 37, so have counsel confirm it for your case.
- 3.Delete the expiry for opt-outs. There is no valid "unconfirmed" state. Every submitted opt-out ends as applied, or as a documented reason it could not be, such as no matching record.
- 4.Log submitted, applied and downstream-notified timestamps. If you cannot show the gap between the first two, you cannot show you honored the request in time.
- 5.Test the browser signal separately. Ford's audit order covers the signal path, not just the form. Send a Global Privacy Control header and check that each tracker actually stops. The Honda and Todd Snyder orders are about buttons that quietly failed, which is the same family of bug.
The form-field side of the same rule is in the LocateSmarter order, where the problem was what the form asked for rather than a step after it. And the PlayOn Sports order shows what a tracker inventory looks like when a regulator asks for one.
Does this carry over to the ADMT opt-out?
Not automatically, and that is worth saying plainly. The ADMT opt-out that applies from 1 January 2027 sits in a different set of sections (7221 and following) with its own clock, a 15 business day stop. The ADMT opt-out guide covers what that handler has to do. Building one intake service that serves both is cheaper than two, but read each section for its own verification rule rather than copying Ford's fix across.
When this is not your problem, and when it is
If you do not sell or share personal information and never will, the Ford opt-out rule has little to bite on, and a deletion-only pipeline with confirmation emails is fine. Ford itself was in scope because, the order recites, it earned over $26.625 million a year and sold or shared the data of 100,000 or more consumers or households. Whether you cross that line is a question for counsel.
If you do sell or share, the fix is a day of work for a team that owns its intake: remove a state, delete a cron job, add two timestamps. Do that yourself and keep a dated screenshot of the flow.
Outside help starts to make sense when the intake is spread across a consent platform, a support desk and a homegrown form, and nobody can say which system holds the step that waits. That is the build behind our ADMT compliance engineering work, and the free ADMT checker will tell you whether the 1 January 2027 rules reach you at all. If you want a second pair of eyes on a request flow, send us the scope.