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.
A cookie is a small note a website saves in your browser so it remembers you.
Keep you logged in, keep items in your cart, and remember your language.
Follow what you do so a company can show you ads or measure results, including companies other than the site you're on.
It's the pop-up you see on almost every website, usually at the bottom of the screen:
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.
Listening to the actual conversation.
An old device that recorded which numbers someone dialed and when, without the conversation.
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.
So did a lot of the businesses that got sued. A banner is a promise. It doesn't block anything on its own.
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.
Show ads to people who visited but didn't buy. They're your warmest audience.
See which ad led to a sign-up or sale, so you stop paying for the ones that don't.
Meta studies the people who bought from you and finds more people like them.
If you plan to run Meta ads, you'll want it.
Your AI has to change how your site loads tracking. Here's what that build looks like:
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 Safari | Yes. Different browser, nothing saved. |
| Open the site on your phone | Yes. Different device, different browser. |
| Open a private / incognito window | Yes. Private windows start with nothing saved. |
| Clear your cookies | Yes. The note was erased. |
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.
| What you see | What it means |
|---|---|
| Requests show up before you click Accept | Still exposed. Run the prompt again. |
| Nothing shows up until you click Accept | Fixed ✅ |
| You click Decline and nothing ever shows up | Fixed ✅ |
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.
A short description of each image, so a screen reader can say what's there. (Example below.)
Can you reach every button and link using only the Tab key?
Is the text dark or light enough against its background to read?
Every field says what it's for, not just a gray hint that disappears.
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 text | What 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.
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.
A short page linked in your footer that says:
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.
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.
Anyone with your public key could read, change, or delete every user's row.
Each user can only open their own rows. Everyone else gets nothing.
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.
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.
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.
"Create a payment link for my $47 course." "How many sales did I make this week?"
"Make me an Instagram post for my new feature," and the design shows up in your Canva.
"What were my best-selling products this month?" "Add this new product to my store."
"Find my notes from Tuesday's call and turn them into a to-do list."
Want the full explanation? Understanding MCP →
Missed a week? See all past live sessions →