Cookie Banners and Privacy Policies: What a Small Business Website Actually Needs

A person sits at a desk filling out a form near an open laptop with floating tags, while a second figure stands in an open doorway. The office has a plant, window, shelves, and a lamp.

Every site you visit has a cookie banner now, your own site has a privacy policy you copied from somewhere in 2021, and you have no idea whether either one is keeping you legal or just decorating the page.

Every small business website needs a privacy policy, and almost no small business website is legally required to show a cookie banner. The policy is mandatory because California’s website law applies to any commercial site that collects personal information from a Californian, with no size threshold, and because Google Analytics and Meta both require one in their terms.

The banner is optional for most owners because the state privacy laws that call for consent and opt outs mostly start at 100,000 residents’ data a year, which a local business never touches.

And yet the banner is worth thinking about, because a lawsuit, not a law, decides whether you should add one. And the banner you copied from a bigger site may be the exact thing that invites it.

This is general information, not legal advice. If you’ve received a demand letter, talk to a lawyer before you reply.

Do the state privacy laws reach a business your size?

Usually not. Twenty states now have comprehensive consumer privacy laws, with Indiana, Kentucky and Rhode Island the newest as of January 2026, and nearly all of them switch on at a volume of data a small business never handles.

The common thresholds:

  • Most states: you process the personal data of 100,000 or more residents of that state in a year, or 25,000 residents plus a meaningful share of revenue from selling data.
  • California: annual revenue over $26,625,000 (the 2025 to 2026 adjusted figure), or 100,000 or more California consumers or households, or half your revenue from selling or sharing personal information.
  • The low outliers: Rhode Island at 35,000 residents, Montana at 50,000.
  • The odd ones: Texas, Nebraska and Minnesota skip the numbers and apply to any business that isn’t a “small business” under the SBA’s definition, which for most service industries means under a few million in revenue or a set employee count.

So a plumber in Scranton with 3,000 customers and a contact form is not a covered business under any of them, and Pennsylvania itself has no comprehensive privacy law yet. The state’s bill, HB 78, passed the House in October 2025 and has been sitting in the Senate through 2026. If it passes as written it follows the same 100,000 resident pattern.

Being under the threshold doesn’t make the data unregulated. The FTC still treats a privacy policy you don’t follow as a deceptive practice, and the wiretap claims further down don’t care about thresholds at all.


Does Europe’s GDPR apply to a local US website?

Only if you’re aiming at Europe. The GDPR reaches a business outside the EU in two cases: you offer goods or services to people in the EU, or you monitor their behavior. The test is intent, not traffic. A landscaper in Wilkes-Barre whose site gets opened by a tourist from Rome is not offering services to Europe.

What does count as aiming at Europe:

  • Prices shown in euros or pounds, or a currency switcher that includes them
  • Shipping physical products to EU addresses
  • Pages written in an EU language for an EU audience, or “.de” and “.fr” style domains
  • Marketing that names EU countries or runs ads targeted there

The monitoring half is the one that catches online sellers. If you run retargeting or behavioral ads and deliberately include EU visitors in the audience, you’re monitoring people in the EU and the rules apply. A local service business with a US only audience doesn’t do this, so for most readers the answer on Europe is no, and it stays no until the day you start selling there.


Why every small business website needs a privacy policy anyway

Three separate things require it, and none of them has a size threshold.

California’s website law. CalOPPA, on the books since 2004, says any commercial website that collects personally identifiable information from California residents has to post a privacy policy conspicuously. You can’t stop Californians from visiting, and a contact form collects a name and an email, so in practice the rule covers every business site in the country.

The tools you already run. Google’s Analytics terms require you to have a privacy policy that discloses your use of Google Analytics and cookies. Meta’s business tools terms require notice to visitors, and consent where the law requires it, before the Pixel sends data. Run either one without the disclosure and you’re out of contract with the platform before any regulator gets involved.

The FTC. A privacy policy is a promise. If it says you never share data and your Pixel is sharing it with Meta every page load, the mismatch is a deceptive practice, and the FTC has enforced exactly that against companies that copied a policy and never read it. A privacy policy that doesn’t match your site is worse than an honest short one.

So write one that’s true. If your site runs Google Analytics 4 and a Meta Pixel, which describes most small business sites, the policy has to cover:

  1. What you collect and how. Contact form fields (name, email, phone, message), plus the automatic stuff: IP address, browser and device, pages visited, the cookies and pixels that collect it.
  2. Why you collect it. Answering enquiries, measuring which pages people use, showing ads to people who visited (say retargeting in plain words).
  3. Who you share it with, by name. Google (Analytics, Ads), Meta (Pixel), your email tool, your form or booking tool, your chat widget if you have one.
  4. How long you keep it and how someone can ask you to delete it.
  5. How to opt out. A link to Google’s opt out add on, Meta’s ad settings, and a line saying your site honors the Global Privacy Control browser signal if it does.
  6. A contact email and an effective date. Update the date every time the tool list changes.
  7. A state rights section only if you’re actually covered by a state law. Copying a CCPA section you don’t fall under promises rights you’re not set up to deliver.

The first step is the easy one: open your site and write down every third party script it loads. Everything else in the policy follows from that list, and that same list is what a stranger is about to pull from your site for a very different reason.


The lawsuit that gets owners to install a cookie banner

The reason ordinary small business sites are adding consent banners in 2026 has little to do with the state privacy laws. A wave of wiretap claims is driving it, mostly under a California statute from 1967 called the California Invasion of Privacy Act, or CIPA.

The theory goes like this. When your site loads a Meta Pixel, a session replay tool like Hotjar or Microsoft Clarity, or a live chat widget, that tool records what a visitor does and sends it to a third party. Do that without the visitor’s consent and, the claim goes, you’ve allowed an illegal wiretap.

The statute lets a private plaintiff sue for $5,000 per violation, with no need to show they lost anything. By the end of July 2026 the trackers counted close to four thousand of these cases in California and more than eight hundred in Florida, which has a similar law. Disclosed settlements had passed $150 million.

The business model is the same one behind the website accessibility demand letters. A small group of repeat claimants runs a scanner across business websites, records which tools each site hands data to, and mails a formal package threatening a California suit unless you settle. It doesn’t matter that you’re in Pennsylvania and have never sold anything in California. The visitor was there, or says they were.

Whether these claims should win is still being argued, and courts have gone both ways on whether a routine pixel is a “wiretap.” But the letters arrive either way, and defending one costs more than the settlement they ask for. That’s the pressure that put consent banners on sites that no statute requires them on.

Three things make a site a target: session replay tools, a chat widget that logs conversations, and the Meta Pixel on pages where people type things. Analytics alone shows up in the claims too, but far less often. If you run none of those, your exposure is low. If you run any of them, a banner that actually blocks the tool until the visitor says yes is the defense, and that word “actually” is where most banners fail.


Why a bad cookie banner is worse than no banner

A cookie banner is a legal statement that you know consent matters. Put one up that doesn’t get real consent, and you’ve written the other side’s exhibit for them. Three versions do this, and one very common setting turns the banner into proof against you.

No reject option. A banner with only “Accept” or “Got it” gives the visitor no choice, so it doesn’t count as consent. In Europe this is settled: a banner needs a reject button as easy to click as the accept one, and the French regulator fined Google and Facebook a combined 210 million euros in 2022 for hiding it. California’s privacy regulations name the same design a dark pattern, and consent obtained through a dark pattern doesn’t count.

Pre ticked boxes. The EU’s top court ruled in 2019 (the Planet49 case) that a pre checked “I agree” box is not consent. The visitor has to do something. California’s rules read the same way.

Promises the site doesn’t keep. A banner that offers “Manage preferences” and then loads every tool regardless of what the visitor picks is a false statement about your data practices, which is the FTC’s territory and the plaintiff lawyer’s favorite screenshot.

And the setting that does the most damage: the banner appears, but the Pixel fires before anyone clicks. Most drag and drop banner plugins default to this. They show the notice and load the scripts at the same time, so the “consent” is cosmetic.

Now the record shows you knew consent was needed (you built a banner), you asked for it, and you collected the data before the answer came. That’s a worse position than having no banner and a truthful policy that says what you run.

If you install a banner, it has to do one specific job: hold the Pixel, the replay tool and the chat widget until the visitor accepts, and keep them off if the visitor rejects. Test it yourself in a private browser window with the network tab open. If a request to facebook.com fires before you click, the banner isn’t working.


What your website actually needs, by situation

  • Just a contact form, no analytics, no pixel, no chat. A short, truthful privacy policy. No banner. You’re done.
  • Google Analytics 4 only. A privacy policy that names Google Analytics and explains the opt out. A banner is optional. If you add one, make it a real one.
  • A Pixel, chat widget or session replay tool on the site. A privacy policy that names each tool, plus a consent banner that blocks those tools until the visitor accepts, with a reject button as visible as the accept button. Test that nothing fires before the click.
  • You sell to Europe, or run ads there. All of the above, and the banner has to default to “off” for EU visitors with the reject option front and center, because in Europe consent comes first, not after.

Whichever line you’re on, do the one step that costs nothing first: list every third party script on your site today, then make the policy say exactly that list and nothing more. Reopen the list every time you add a tool.


Frequently asked questions

Do I need a privacy policy for my small business website?

Yes. California’s CalOPPA requires any commercial website that collects personal information from California residents to post one, and there’s no revenue or size threshold. Google Analytics and Meta’s business tools also require a privacy policy in their terms of service. A contact form alone is enough to trigger the requirement.

Is it illegal to not have a cookie banner in the US?

No federal or state law makes a typical small business website show a cookie banner. The state privacy laws that require opt outs and consent for certain data mostly apply above 100,000 residents’ data a year. The pressure to add one comes from private wiretap lawsuits over tracking pixels, chat widgets and session replay tools, not from a statute that names small sites.

Does GDPR apply to my US business if I have European visitors?

Not from visitors alone. GDPR applies to a US business that offers goods or services to people in the EU (euro pricing, EU shipping, EU language pages) or deliberately monitors their behavior, such as retargeting an audience that includes EU users. A local US service site with an occasional European visitor is outside it.

Can I use a free privacy policy template?

You can start from one, but only if you edit it to match what your site really does. A copied policy that promises you never share data while your Meta Pixel shares it every page load is a deceptive practice, and a copied state rights section you aren’t covered by promises rights you can’t deliver. The template is a skeleton; the tool list is yours.

What is a CIPA demand letter?

A letter, usually from a law firm representing a repeat claimant, saying your website recorded a California visitor without consent through a tracking pixel, chat widget or session replay tool, in violation of the California Invasion of Privacy Act, and offering to settle before filing suit. The statute allows $5,000 per violation. Don’t reply or pay without a lawyer, and don’t rip the tools out in a panic before documenting what the site was running.

Does Pennsylvania have a privacy law?

Not a comprehensive one yet. Pennsylvania’s HB 78, the Consumer Data Privacy Act, passed the House in October 2025 and is still moving through the Senate in 2026. Pennsylvania does have a data breach notification law, which applies to every business that holds residents’ personal information regardless of size.

Ready to take the first step?

A group of people in business attire collaborate in a modern office, standing by a large whiteboard covered with diagrams, notes, and sticky notes, while others sit at a table with laptops and papers.