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

Real proof. Real protection.

Stop faking testimonials, start collecting real ones, and run four checks before your app goes live.

Last week we covered cookies and accessibility. This week: the testimonials AI quietly made up for you, how to build a system that collects real ones, and four more things that protect your visitors and your users' data.

Part 1
Fake testimonials

"Sarah J., Marketing Director ★★★★★"

Ask AI to build a landing page and it will happily fill the testimonial section with glowing reviews from people who don't exist. Placeholder names, five stars, a stock photo. A lot of people launch without ever deleting them.

Oct 2024
The FTC's rule banning fake reviews and testimonials took effect, including AI-generated ones
$50,000+
possible fine per violation

What the rule bans

Paste this into Claude Code
Search my entire web app, every page, component, and data file, for testimonials, reviews, star ratings, customer counts, and customer logos. Remove anything that didn't come from a real customer, and show me what you removed. Then add this as a permanent rule to my project's rules file (like AGENTS.md or CLAUDE.md): Never create or keep fake or placeholder testimonials, reviews, star ratings, customer counts, or customer logos. Only use reviews I provide from real customers. If a section needs reviews and I haven't given any, leave it empty and tell me.
An empty section is better than a fake one. So let's fill it with real ones.
Part 2
Collect real testimonials

I built my own testimonial system.

I was paying for Senja to collect and display testimonials. So I built my own inside my website, using Claude, Supabase, and Vercel. Now I own the testimonials and the system that collects them.

For your clients

📝 Share your story

A simple form: star rating, written or video story, optional photo, and permission to publish. No account needed.

Just for you

🔐 Private dashboard

Nothing goes public until you approve it. Choose where each story shows up.

For everyone

⭐ Wall of Love

A public page showing only approved stories. Emails are never shown.

Per workshop

🔗 One link per offer

Each workshop gets its own link, so its stories land on that workshop's page.

How to build yours

  1. Save what you already have. If you use a testimonial tool now, export every story, photo, and video before you cancel anything. The testimonials are the valuable part. The tool is just the container.
  2. Open your project in Claude Code and describe what you want (prompt below). Ask it to match your branding and build on your computer first.
  3. Set up the database in Supabase, with Row Level Security on, so people's emails and permissions stay private.
  4. Build the "Share your story" form: rating, story, photo, and a permission checkbox.
  5. Build your private approval dashboard, protected by a login only you can use.
  6. Build the public wall that only shows approved stories.
  7. Test the whole journey: submit a test story, approve it, see it go live, then hide it and make sure it disappears.
Paste this into Claude Code
Build a testimonial system into my existing website. Match my current branding. Build it locally first. 1. A public "Share your story" page with a 1 to 5 star rating, a written or video testimonial, name, email, role or business, an optional photo, and a required checkbox giving me permission to publish it. Show a thank-you screen after submitting. 2. Store submissions in Supabase with Row Level Security turned on, so names, emails, and permissions can never be read from the browser. Add a limit on how many times someone can submit, to stop spam. 3. A private dashboard, protected by a login only I can use, where I approve, hide, or feature each story and choose where it appears. 4. A public testimonials page that only shows approved stories and never shows anyone's email. 5. Let me create a separate link for each workshop or offer, so stories are tagged automatically. Explain each step in plain language before you build it, and walk me through testing the whole journey at the end.

Start collecting now. Everywhere.

You don't need something to sell yet. Every time you help someone, ask for their story. You'll want them later.

Example email signature
Dr. Erin Jacques · Leveraging AI
Worked with me? I'd love to hear how it went → drerinjacques.com/share-your-story

See mine

My Wall of Love → My "Share your story" form →

I used Senja as my example, but it doesn't have to be Senja. It could be any testimonial tool you're paying for, or one you like that does a good job. Study what it does well, then build your own version.

Part 3
4 checks before launch

Protect your visitors and your users' data.

Check A · Google Fonts

Your font is phoning Google.

Most AI-built sites get their fonts from Google with one line of code, hidden in the page:

<link href="https://fonts.googleapis.com/css2?family=DM+Sans" rel="stylesheet">

That line tells every visitor's browser: "Go to Google and get this font."

What it looks like (from my own site, which I'm fixing)

When someone opens the page, their browser quietly makes two trips to Google before they've clicked anything:

RequestWhat it is
fonts.googleapis.com/css2?family=DM+Sans…Asks Google for the font instructions
fonts.gstatic.com/s/dmsans/…woff2Downloads the font file from Google

What Google receives with each trip

Why that's a problem

Your visitor never agreed to share any of that with Google. In 2022, a German court ruled a website broke Europe's privacy law by doing exactly this, and ordered it to pay the visitor €100. That started a wave of demand letters across Europe. It's the same issue as the pixel: a third party gets your visitor's data without asking.

What about the US?

See it yourself

  1. Open your site, right-click, choose Inspect, and open the Network tab.
  2. Type fonts.g in the filter box, then reload.
  3. See fonts.googleapis.com or fonts.gstatic.com? Your site is doing this.

The fix: host the font yourself

Download the font and serve it from your own site. Same look, no trip to Google, and it often loads faster.

Paste this into Claude Code
Find every place my site loads fonts from Google Fonts (fonts.googleapis.com or fonts.gstatic.com). Download those fonts, save them in my project, and load them from my own site instead. Keep the same fonts and weights so nothing looks different. Then show me how to confirm in the Network tab that nothing loads from Google anymore.
Same font. Zero trips to Google.
Check B · Row Level Security

How a stranger reads your database.

Supabase has Row Level Security (RLS), but it's a switch, and it isn't on for every table. Tables made in Supabase's Table Editor usually have it on. Tables your AI creates with code often don't.

How someone gets in

  1. Every Supabase project gets a web address for each table. Ask that address for the "users" table and it answers.
  2. Your site's code contains your project address and public key, so your app can talk to the database. Anyone can find them: right-click, Inspect, Network tab.
  3. With RLS off, a stranger pastes that address and key into a simple request and gets every row: names, emails, phone numbers. They can also add, change, or delete rows.
  4. With RLS on, the same request comes back empty, unless a rule allows it, like "users can only see their own rows."
Without RLS

🔓 Everything

The stranger's request returns every user's information.

With RLS

🔐 Nothing

The same request returns an empty list, and adding fake data is blocked.

👉 I tested this on my own testimonial system. Using only my site's public key, reading the testimonials came back empty, and trying to add a fake testimonial was blocked: "new row violates row-level security policy."
170+
apps built with Lovable were found leaking user data in 2025 because RLS wasn't set up right
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. Then test it: using only my public key, try to read and add rows the way a stranger would, and show me the results. 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.
Check C · Rate limiting

Stop bots without locking out people.

Rate limiting is a cap on how many times someone can try something in a set amount of time, like 5 login attempts per minute.

Why you need it

Supabase limits some things automatically, like login emails. Your own forms and AI features need their own limit. My testimonial form has one.

Nobody has to wait hours

You choose the rules. The common options:

OptionHow it works
Short window"5 tries per minute." After that, wait 60 seconds. Most people never notice.
Gradual slowdownEach failed try adds a longer wait: 1 second, then 5, then 30. People barely feel it. Bots slow to a crawl.
Prove you're humanAfter a few failed tries, show a "Verify you're human" checkbox instead of blocking.
Reset by emailOffer "Send me a login link" so a real person is never stuck.

Limits reset on their own once the time window passes. Nothing to do manually.

Paste this into Claude Code
Add rate limiting to my web app. Cover login, sign-up, password reset, every form, and any feature that calls an AI or other paid service. Use short time windows (like 5 tries per minute) so real people are never locked out for long. After repeated failed logins, show a "verify you're human" check and offer a login link by email. Explain the limits you chose in plain language, then show me how to test that they work.
Small enough that people never hit it. Strict enough that bots hit it right away.

What's next: one tool that checks it all.

I'm building a tool that checks your site for all of these at once: tracking that fires too early, Google Fonts, missing accessibility basics, and more. As I build it and fix my own platform, I'll keep you in the loop.

Your homework this week.

  1. Run the fake testimonials prompt and add the rule to your CLAUDE.md or AGENTS.md.
  2. Start collecting real testimonials: add a link to your email signature today.
  3. Do the Network tab check for fonts.g on your site.
  4. Run the RLS prompt and confirm a stranger gets nothing.
  5. Bonus: add rate limiting and consent records.
This is context to help you build responsibly, not legal advice. If you're collecting sensitive data or running paid ads, talk to a lawyer.
Join the community →

Missed a week? See all past live sessions →