California's privacy regulator fined Hertz $1.55 million for failing to honor opt-out requests and complicating the process for customers to protect their data. The same day, the agency announced a separate $218,000 settlement with CC Filson Co. These questions arise in security and privacy channels after such actions. The answers are for those who need to fix the issues, not just explain them.
Q1: What exactly did Hertz get fined for? Was it a breach?
No breach occurred. This was a failure to listen. The California Privacy Protection Agency (CPPA) alleged that Hertz didn't process opt-out preference signals, which are automated signals a browser or device sends to tell a website not to sell or share a consumer's data. Hertz also failed to inform consumers about how it handled these signals and added unnecessary obstacles to the opt-out process.
This is serious because no attacker was involved. The issue arose from ordinary web infrastructure acting in a way the law didn't allow. Under CCPA/CPRA, honoring these signals is a legal requirement. The regulator's acting deputy director of enforcement stated businesses "have been on notice for years." Don't expect sympathy for "we didn't realize."
Q2: What's an opt-out preference signal, and why would we miss one?
It's a machine-readable instruction from the consumer's browser or device saying, "don't sell or share my data." The consumer sets it once, and it travels with every request. Your site must read it and act on it without asking the person to repeat themselves.
Teams miss it for common reasons:
- Consent banners and cookie tools only read what the user clicks, not the signal in the request.
- Tag managers fire advertising and analytics tags before any signal check runs.
- Marketing adds a new pixel or SDK without testing if it respects the signal.
- The signal is honored on the main domain but not on subdomains, booking flows, or mobile web views.
The pattern is a gap between what the privacy notice promises and what the page does when it loads. This is a technical-control problem and should be on your testing calendar, not just your legal team's reading list.
Q3: What does "friction" mean in practice, and are we doing it?
The agency used "friction" to describe added obstacles in the opt-out process. You can audit yourself against it. Count the clicks and fields between a consumer deciding to opt out and the opt-out taking effect. Then ask:
- Does the opt-out require more steps than the opt-in?
- Does it demand an account login, extra identity details, or a form buried in a footer?
- Does the interface use wording or design that nudges people toward staying in?
- Can someone complete it on mobile without hunting for it?
If the opt-in path takes one tap and the opt-out path takes six screens, you have a problem. Walk through your flow as a customer would, on a phone, and note what you see. Then compare it to what your privacy notice says is available.
Q4: What did Hertz agree to do going forward? Is that a template for us?
Hertz agreed to change its business practices and conduct quarterly testing and monitoring. This includes reviewing all new tracking technologies, testing opt-out compliance, and ensuring correct information is submitted to the CPPA.
Treat this as a design spec for your own program, as it's what the regulator considers adequate:
- Test on a schedule. Run opt-out and signal tests regularly, not just at launch. Quarterly is the cadence the agency imposed.
- Gate new trackers. No new pixel, SDK, or tag goes live without a privacy review confirming it respects opt-out status.
- Keep evidence. Retain test results, screenshots, and sign-offs. If asked to prove compliance, a dated record is invaluable.
Building this voluntarily costs far less than doing it under a settlement.
Q5: Who owns this? Privacy, legal, marketing, or security?
All of them touch it, which is why it often falls through gaps. Here's a workable split:
- Legal and privacy define the obligation and approve the notice language.
- Marketing and web teams own the tags and tools that collect data.
- Security and GRC own the control: the test, the monitoring, and the evidence.
Security leaders are well-placed to run this because you already manage change control, vendor review, and continuous testing. Treat opt-out handling as a control with an owner, a test procedure, and a failure threshold, just like access reviews. The NIST Privacy Framework gives you a structure for mapping data-processing activities to controls, and ISO/IEC 27701 extends an ISO/IEC 27001 program to cover privacy management if you already run an ISMS.
Q6: Our vendors and ad-tech partners handle the tags. Doesn't that shift the risk?
Not much. The CC Filson settlement is a useful comparison: the agency required the company to stop all device-based sales and sharing of consumers' Personally Identifiable Information to advertising technology companies within 30 days, in addition to a $218,000 fine. The remedy reached into the ad-tech relationships, not just the website.
Outsourcing the tag doesn't outsource the obligation. Practical steps:
- Inventory every third-party script and SDK on your properties, and who receives data from each.
- Require contract language that obliges partners to honor opt-out status and signals you pass along.
- Verify with testing rather than relying on a vendor's attestation alone.
- Make removal of a non-compliant partner a real option, not a theoretical one.
If a partner can't demonstrate it honors the signal downstream, that's a vendor risk to log and escalate like any other.
Where to go for more
Start with the CPPA's published enforcement materials and the text of CCPA/CPRA to confirm which obligations apply to your business and how the agency interprets them. For program structure, the NIST Privacy Framework and ISO/IEC 27701 provide controls you can map to. For testing discipline, borrow from how you already handle control validation: define the control, test it on a schedule, and keep the evidence.
The Hertz action is a short lesson with a long tail. The fix isn't exotic. It's a signal check that works, an opt-out path that doesn't punish the user, and a test that runs every quarter whether or not anyone's watching.





