The US Privacy Picture
Transcript
Made automatically from the video's sound, so it may contain mistakes. Click a line to play from there.
Welcome back to The Explainer. Okay, so after episode three mapped out the intricacies of EU cookies and consent, today we are crossing the Atlantic. We're decoding the US privacy landscape, specifically for you, the product managers, founders, marketers, and devs out there.
Just a quick heads up before we dive in. This is general information, current as of November 2026, and absolutely not legal advice. Right, grab your notes and let's get into it.
We've got a packed agenda today. First, the US privacy patchwork. Second, unpacking California's CCPA. Third, navigating the sale versus sharing trap.
Fourth, surveying other state laws, and finally, unifying your strategy. The US privacy patchwork, federal versus state systems. So, unlike the European Union, which has that neat single comprehensive umbrella under the GDPR, the US operates on a much more fragmented two-layer system.
There is literally no single overarching federal consumer privacy statute. Instead, you're dealing with specific sector-based federal rules layered right on top of roughly 20 very different comprehensive state-by-state laws. It's like a giant puzzle.
At the federal level, you're navigating specific sectors. For instance, you've got Copper, that's specifically 16 CFR Part 312, guarding online privacy for kids under 13. You've got HIPAA for traditional healthcare providers, but a crucial word of warning here.
If you're building a consumer wellness or fertility app, you actually fall under the FTC Health Breach Notification Rule instead. And let's not forget GLBA for financial institutions. Overarching all of this is the FTC Act Section 5, which aggressively targets unfair or deceptive practices.
Basically, if your privacy policy makes a promise and your code secretly breaks it, the FTC is going to come knocking. Unpacking California's CCPA, the heavyweight standard. So does California's flagship law actually apply to you?
Well, under the California Civil Code, specifically section 17.98.140 D, the statutory business threshold kicks in if your company has over $25 million in gross annual revenue. But revenue isn't the only trigger.
If you buy, sell or share the personal info of 100,000 or more California consumers or households, or if you derive 50% of your revenue from selling or sharing that data, you are fully on the hook for California's rules. And if you hit those thresholds, you have to provide some incredibly robust consumer rights.
We're talking notice at collection, the right to know, the right to delete, and the right to correct. Under section 1798.120, they have the absolute right to opt out of the sale or sharing of their data.
And remember, that requires an affirmative opt-in for kids under 16. Plus, under section 1798.121, they can limit your use of sensitive personal info like precise geolocation. And fundamentally, you absolutely cannot discriminate against users or hike up your prices just because they exercised these rights.
Now, if you are in the data broker space, meaning you knowingly collect and sell info of consumers you don't have a direct relationship with, this timeline is literally make or break. Thanks to California's DELETE Act, you now have to process bulk deletion requests through the drop platform.
Consumers have been able to submit these single universal deletion requests since January 2026, and as of August 2026, data brokers are legally required to access drop and process them. Miss a request?
You're looking at a frankly terrifying penalty of $200 per day for each missedeletion. It adds up ridiculously fast. The sale versus sharing trap, the number one product minefield.
What exactly is the difference here? Well, a sale doesn't just mean cash changing hands, it means exchanging personal info for any valuable consideration. Sharing means disclosing it for cross-context behavioural advertising.
This is where devs get caught out. If you just fire a standard third-party ad or retargeting pixel, you are almost certainly triggering sections 1798.120 and 1798.135. Unless you've locked that third party down under a strict service provider or contractor agreement, you are legally selling or sharing data.
So the big question for your product team is how do you actually handle these opt-outs? According to CPPA advisories 2024 01 and 2024 02, regulators are aggressively hunting down manipulative UI and dark patterns.
You cannot force users to jump through endless hoops, create an account, or go through excessive identity verification just to say, stop selling my data. It has to be frictionless. The modern solution to this is the W3C Global Privacy Control, or GPC.
On your back end, this looks like a header saying sec GPC1. On your front end, it's the navigator.globalPrivacyControl property. When a browser fires this signal at you, you must treat it as a valid, binding request to stop data sharing immediately.
No forms, no footer links required. It just has to work. Surveying other state laws. Looking at the rest of the map.
The tricky bit? You can't just copy and paste California's rules across the whole country. If you check the IAPP state tracker or attorney general guides, you'll see that Virginia's VCDPA dictates very specific controller and processor templates.
Colorado and Connecticut enforce strict universal opt-out mandates, opt-ins for sensitive data, and their cure periods have entirely expired. Oregon triggers at 100,000 consumers, includes specific motor vehicle exceptions, and even covers nonprofits.
Meanwhile, Texas completely dropped its revenue cap to sweep in almost all non-small businesses. It is a wildly complex terrain. Unifying your privacy strategy, your operational playbook.
Because things are so fragmented, your dev team needs to base your core architecture on established standards, like the NIST privacy framework. Next, do a roofless audit to map out every single third-party pixel or tracker. Automate your support for those global privacy control headers we just talked about, and finally, set up clear internal triggers so you know exactly when to escalate those tricky grey areas to specialized US privacy council.
Navigating this US patchwork isn't just about dodging fines or FTC enforcement. It really demands a paradigm shift. It's about treating data privacy as a fundamental human right built right into your product's DNA.
When users actually trust that you aren't secretly monetizing their behavioural data behind their backs, well, that trust becomes a massive competitive advantage for you. And that wraps up our map of the US privacy landscape.
Make sure you join us next time for episode 5, where we're crossing back over the Atlantic to decode the highly anticipated EU AI Act and what it means for your dev pipelines. Until then, I'll leave you with this.
If privacy really is a human right, are your current analytics tools treating your users like actual humans, or just data points waiting to be stripmined?