← Previous ☰ All Live Sessions Oct 9 · Friday Live
Dr. Erin Jacques · Friday Live
Friday Live · October 9

Protect the web app you just built.

Two things that get small businesses sued, one thing that protects your users' data, and the build that fixes each one.

AI made it easy to build and launch fast. It did not check whether your tracking pixel fires before someone says yes, or whether a blind person can use your app. Today: what's happening, why it matters, and exactly what to ask your AI to build.

👉 "I'm too small for this to apply to me." Not true. The cookie and accessibility rules have no minimum business size. If your web app is open to the public, they apply to you.
Part 1
Cookies & tracking pixels

First, what's a cookie?

A cookie is a small note a website saves in your browser so it remembers you.

Helpful cookies

🛒 Remember you

Keep you logged in, keep items in your cart, and remember your language.

Tracking cookies

👀 Follow you

Follow what you do so a company can show you ads or measure results, including companies other than the site you're on.

What's a cookie banner?

It's the pop-up you see on almost every website, usually at the bottom of the screen:

We use cookies to improve your experience. Accept Decline Settings

It started with phone calls.

In 1967, California passed the California Invasion of Privacy Act (CIPA) to stop people from secretly tapping phone calls. Someone could literally clip onto the line and listen. The rule: you can't listen in on or record a conversation unless everyone on it agrees.

That's why calls start with "this call may be recorded." That announcement is how they get your consent.

Who has to agree to a recording?
New York (one-party consent)Just one person on the call. That can be you.
California (all-party consent)Everyone on the call.

That stricter California rule is why most of these lawsuits are filed there.

Wiretapping

📞 What was said

Listening to the actual conversation.

"Pen register"

🔢 Who called whom

An old device that recorded which numbers someone dialed and when, without the conversation.

Now replace the phone call with your website.

The conversationSomeone visits your site
What they "say"Clicks, scrolls, searches, types
On the lineMeta Pixel, Google Analytics, chat & recording tools
The problemThey never agreed to it

Lawyers argue that a tracking tool from another company, recording what your visitor does without permission, is a third party listening in. That's the wiretapping argument. Collecting their IP address and device info gets compared to the pen register.

4,300+
digital wiretapping lawsuits since May 2022, about 75% in California
$5,000
per violation. No proof of harm needed.
$10M
Forbes settlement in 2026. The LA Times paid $3.85M.
👉 It's about where your visitor is, not where your business is. Your business can be in New York. A Californian visiting your site is enough.

"But I have a cookie banner."

So did a lot of the businesses that got sued. A banner is a promise. It doesn't block anything on its own.

So what is a Meta Pixel?

Yes, it's the one that retargets you.

A Meta Pixel is a small piece of Meta's code you add to your site. When someone visits, it reports back to Meta: "this person viewed the pricing page," "this person signed up," "this person bought." It's why you look at something and then see an ad for it on Instagram.

Why you want one as a business owner

Retargeting

🎯 Bring them back

Show ads to people who visited but didn't buy. They're your warmest audience.

Tracking results

📊 Know what's working

See which ad led to a sign-up or sale, so you stop paying for the ones that don't.

Lookalikes

👯 Find more buyers

Meta studies the people who bought from you and finds more people like them.

Without it

🙈 Ads run blind

If you plan to run Meta ads, you'll want it.

Build a lookalike audience from your buyers

  1. Go to Meta Ads Manager (this covers Facebook and Instagram ads).
  2. Audiences → Create Audience → Custom Audience → Website.
  3. Choose the Purchase event, not just "all visitors." Your pixel has to be set up to report purchases.
  4. Create a Lookalike Audience from it. You'll need about 100 people to start.
  5. No pixel yet? Upload your buyer email list as a Customer List and build the lookalike from that.
Keep the pixel. Just turn it on after they say yes.
The fix

It's a build, not just a banner.

Your AI has to change how your site loads tracking. Here's what that build looks like:

  1. Take the pixel out of the page. Right now it probably loads for everyone, automatically.
  2. Build a real consent banner that remembers the visitor's choice.
  3. Load the pixel only after they click Accept. If they decline, it never loads.
  4. Add a "Cookie settings" link in the footer so people can change their mind.
  5. Do the same for Google Analytics, TikTok, Hotjar, and chat widgets.

How does the banner remember the choice?

It's connected to your browser. Not your Wi-Fi, and not your IP address (your device's return address on the internet). Your actual browser.

Each browser keeps its own separate storage: your passwords, your history, your logins, and your cookie choices. Chrome on your laptop and Safari on your phone don't share any of it.

When you click Accept, the site saves a small note in that browser, something like consent = accepted. Every page checks that note first. Accepted? The pixel loads. Declined or no note? It doesn't.

If you...Does the banner pop up again?
Take your laptop to a café (same browser, new Wi-Fi)No. Your browser remembers.
Switch from Chrome to SafariYes. Different browser, nothing saved.
Open the site on your phoneYes. Different device, different browser.
Open a private / incognito windowYes. Private windows start with nothing saved.
Clear your cookiesYes. The note was erased.
👉 That one "consent" cookie is allowed without asking, because it's what makes the banner work.
Paste this into Claude Code
Remove the Meta Pixel and any other tracking scripts from loading automatically. Build a cookie consent banner that saves the visitor's choice. Only load tracking scripts after they click Accept. If they decline, never load them. Add a "Cookie settings" link in the footer so they can change their choice. Then tell me how to test it in the browser's Network tab.

Check it yourself

  1. Open your site in a private / incognito window.
  2. Right-click → Inspect → open the Network tab.
  3. Type facebook in the filter box, then reload the page.
What you seeWhat it means
Requests show up before you click AcceptStill exposed. Run the prompt again.
Nothing shows up until you click AcceptFixed ✅
You click Decline and nothing ever shows upFixed ✅
Part 2
Accessibility

Can everyone actually use your app?

Businesses get sued under the ADA (the Americans with Disabilities Act) thousands of times a year when people with disabilities can't use their website. Think of someone who is blind using a screen reader that reads the page out loud, or someone who can't use a mouse.

What gets checked

Images

🖼️ Alt text

A short description of each image, so a screen reader can say what's there. (Example below.)

Keyboard

⌨️ No mouse needed

Can you reach every button and link using only the Tab key?

Color

🎨 Contrast

Is the text dark or light enough against its background to read?

Forms

📝 Labels

Every field says what it's for, not just a gray hint that disappears.

What alt text sounds like

Alt text is a short written description hidden in your site's code. A screen reader (software that reads the page out loud for people who are blind or have low vision) reads it aloud. Picture a photo of you teaching on your laptop:

Alt textWhat the screen reader says
❌ None"Image. IMG_4382.jpg"
❌ Too vague"Photo"
✅ Good"Dr. Erin Jacques teaching a live class on her laptop"

Rule of thumb: describe what someone would miss if they couldn't see it. Purely decorative images should be skipped so the screen reader doesn't read out clutter.

"But I have the accessibility button."

You've seen this little figure in the corner of websites. Click it and a menu opens: bigger text, more contrast, and so on. It adds a menu on top of your site. It doesn't fix the missing alt text, keyboard problems, or labels underneath.

👉 Those accessibility widgets don't protect you. In 2025 the FTC fined accessiBe $1M for claiming its widget made sites compliant.

Your accessibility statement

A short page linked in your footer that says:

Paste this into Claude Code
Audit my web app for accessibility. Check alt text on images, keyboard navigation, color contrast, and form labels. Fix every issue you find, then add an accessibility statement to the footer.
Accessible isn't extra. It's more people who can buy from you.
Part 3
Row Level Security (RLS)

Who can see the data in your app?

Your Supabase database is like one big filing cabinet holding every user's information: names, emails, profiles, what they paid for. Each user's information is a row.

Here's the part most people don't know: your website has a public key in its code so it can talk to that cabinet. Anyone can find that key. That's normal and by design, as long as the cabinet has locks.

Without RLS

🔓 No locks

Anyone with your public key could read, change, or delete every user's row.

With RLS

🔐 A lock on every drawer

Each user can only open their own rows. Everyone else gets nothing.

What RLS prevents

170+
apps built with Lovable were found leaking user data in 2025 because RLS wasn't set up right
👉 In our community, we turn RLS on from day one. It's part of how we set up Supabase. If you've added new tables since, check them too.
Paste this into Claude Code
Using the Supabase connector, check every table in my database. Confirm Row Level Security is turned on for each one, and that users can only see and change their own rows. Run Supabase's security advisor too. Explain anything that's wrong in plain language before you change it.
The public key is the front door. RLS is the lock on every drawer.
Part 4
ChatifyIT + MCP

Meet ChatifyIT.

Your link-in-bio page for everything you sell and share.

We build your free AI lead magnet. You add what you sell. One link grows your email list.

Now connected to Claude, it becomes your AI marketer too.

It turns what you build and the videos you post into LinkedIn posts, release announcements, and newsletter emails, in your voice. Nothing posts without your click.

👉 What's an MCP? It's what lets Claude use another app for you. You connect it once, and then you just ask.

How to connect ChatifyIT (one time)

  1. In Claude, go to Settings → Connectors → Browse connectors.
  2. Search for ChatifyIT and click Connect.
  3. Sign in to ChatifyIT and click Allow.
I built this MCP in a few hours. If your app does something valuable, you can build one for it too.

MCPs real companies have built

Payments

💳 Stripe

"Create a payment link for my $47 course." "How many sales did I make this week?"

Design

🎨 Canva

"Make me an Instagram post for my new feature," and the design shows up in your Canva.

Store

🛍️ Shopify

"What were my best-selling products this month?" "Add this new product to my store."

Notes

📝 Notion

"Find my notes from Tuesday's call and turn them into a to-do list."

Start your free ChatifyIT trial →

Want the full explanation? Understanding MCP →

Your homework this week.

  1. Do the Network tab check on your own site. Does anything fire before Accept?
  2. Run the cookie prompt, then check again.
  3. Run the accessibility prompt and add your statement to the footer.
  4. Try getting around your app using only the Tab key.
  5. Run the RLS prompt and confirm every table is locked.
  6. Bonus: connect ChatifyIT to Claude and ask it to write your first post.
This is context to help you build responsibly, not legal advice. If you're running paid ads or collecting sensitive data, talk to a lawyer.
Join the community →

Missed a week? See all past live sessions →