free guide · is it safe? 02

Check your AI‑built app for 4 legal traps

An app built with an AI agent can break four laws on launch day, before it makes a dollar. Each one comes down to a default nobody checked. Here’s what each law asks for, how to check your app, the fix, and a prompt that has your agent check all four. Plus the one popular “fix” you can skip.

up to $53,088 per email$5,000 per violation€100 per visitorcharges → a gift

From the reel on @feruzbuilds · facts checked Oct 7, 2026 · a checklist, not legal advice

01

The four at a glance

The trapThe lawWhat it can cost
A launch email with no unsubscribe link or postal addressCAN-SPAM Act (US)Up to $53,088 per email
Session replay that records what visitors typeCalifornia Invasion of Privacy Act §631$5,000 per violation
Fonts loaded from Google’s serversGDPR (EU visitors)A Munich court: €100 to one visitor
A subscribe button without renewal terms next to itCalifornia Automatic Renewal LawWhat you charged can count as a gift

Which ones apply to you depends on where your users live and what your app does. These are the ones that hide in defaults: a template email, an analytics snippet, a font link, a checkout button. If something here touches real money or real users, talk to a lawyer about your situation.

02

The launch email

The CAN-SPAM Act covers any commercial email: the “we’re live” email to your waitlist, a newsletter, a drip sequence. The FTC’s guide puts the penalty plainly: “Each separate email in violation … is subject to penalties of up to $53,088.” The FTC made no inflation adjustment for 2026, so that figure stands.

How to check: open every email template your app or your email tool sends, including the one you’ll write on launch day. Then check that your export or send list skips people who unsubscribed.

The fix: one footer on every marketing template: why they got it, an unsubscribe link, your postal address. Most email services add a one-click unsubscribe header if you turn it on.

03

Session replay

Session replay records what visitors do on your page (mouse moves, clicks, scrolls, and often what they type) so you can watch it back. Many analytics tools include it, and some turn it on in a default setup. In California, recording what people type without their consent can count as wiretapping under Penal Code §631, and §637.2 sets “five thousand dollars ($5,000) per violation”. That section is behind most session-replay, pixel and chatbot lawsuits.

What changed on Sept 30, 2026: California signed SB 690. From Jan 1, 2027, only the Attorney General can sue businesses under §638.51 (the “pen register” section) over website and app tracking. The wiretap sections, §631 and §632, are untouched, so session-replay suits stay.

How to check: list every script your pages load, and look in each analytics tool’s settings for “session recording” or “replay”. Check chat widgets too: some log what people type before they hit send.

The fix: turn it off, or load it only after the visitor opts in, with every form field masked. Never record passwords, card numbers or messages.

04

Google Fonts

When a page loads a font from Google’s servers, each visitor’s browser sends its IP address to Google. On Jan 20, 2022, the Munich Regional Court (Landgericht München I, file 3 O 17493/20) found that doing this without consent broke the GDPR. It ordered the site to stop and to pay the visitor who sued €100 (about $112). The court said there was no legitimate interest, because the fonts could be hosted on the site’s own server.

It applies when your app has visitors in the EU. Telling people in your privacy policy isn’t enough on its own: the court’s point was that you didn’t need to send the request at all.

How to check: search your code for fonts.googleapis.com and fonts.gstatic.com, then open your site with the browser’s Network tab and look for any request to another company’s server before the visitor has agreed to anything: fonts, scripts, icons, maps, video embeds.

The fix: download the font files and serve them from your own domain with @font-face. Frameworks can do it for you; in Next.js, next/font self-hosts Google fonts at build time.

05

The subscribe button

California’s Automatic Renewal Law (Business and Professions Code §17600 and on) says the renewal terms must be “clear and conspicuous” and shown “in visual proximity” to where the customer agrees, before they pay (§17602). You need their affirmative consent to those terms, an acknowledgment afterwards that repeats them with how to cancel, and an online way to cancel for anyone who signed up online. If you charge without that consent, §17603 says what you sent counts as an “unconditional gift”, theirs to keep without paying.

How to check: look at your checkout the way a customer does. Next to the button, can they see the price, how often it renews, that it keeps renewing until they cancel, and how to cancel?

The fix: one short line right by the button (“$9/month, renews monthly until you cancel. Cancel anytime in Settings.”), a confirmation email with the same terms and the cancel link, and a cancel button that works online.

06

The one you can skip: the age question

Viral lists tell you to add an age question to your signup “because of COPPA”. You don’t need one unless your app is for kids. The FTC’s COPPA FAQ says the rule doesn’t require general-audience sites to ask visitors’ age or investigate it. COPPA applies when your service is aimed at children under 13, or when you actually know a user is under 13. Then you need verifiable parental consent, with penalties up to $53,088 per violation.

If you do ask for age, you have to act on the answers: once a user tells you they’re under 13, the rule applies to them. Ask because your product needs it, not as a legal charm.

07

Two more worth a look

08

Checklist

09

Prompts for your AI agent

Paste these into Claude Code, Cursor, or any agent that can read your project. Run the first one before launch; it changes nothing.

Check my app for all four

Audit this app for 4 legal risks before launch. Read every file: code, email templates, config, the privacy policy. Don't change anything yet.

1. Marketing email: does every promotional email (launch, newsletter, drip) include a working unsubscribe link and a valid physical postal address, and are unsubscribed people kept off every send list? (US CAN-SPAM Act)
2. Session replay: does any tool record what visitors type, click or scroll (session replay, heatmaps, chat widgets that log input)? Is it on before consent, and are form fields masked? (California Invasion of Privacy Act §631)
3. Third-party requests: does anything load from another company's servers on page load (fonts, scripts, images, embeds), sending the visitor's IP address before consent? Start with Google Fonts. (EU GDPR; Munich Regional Court, 3 O 17493/20)
4. Subscriptions: if anything renews automatically, are the price, how often it renews, that it continues until cancelled, and how to cancel shown right next to the subscribe button? Does the user agree to them explicitly, does the confirmation email repeat them, and can they cancel online? (California Automatic Renewal Law, Bus. & Prof. Code §17602)

Also check: can users upload files (then a DMCA agent is needed), and does the privacy policy name every company that gets user data?

For each item answer PASS, FAIL or N/A, with the file and line, and the smallest fix. Don't suggest adding an age question unless the app is aimed at children under 13. End with what to fix first. This is a checklist, not legal advice: flag anything that needs a lawyer.

Fix what failed

Fix the FAILs from your audit one at a time, smallest change first. After each fix, show me the diff and how to test it. Don't touch anything that passed.
- Fonts: download the font files, serve them from my own domain with @font-face, and remove every request to fonts.googleapis.com and fonts.gstatic.com.
- Session replay: turn it off, or load it only after the visitor opts in, with every input masked.
- Emails: add an unsubscribe link and my postal address to every marketing template. Ask me for the address; never invent one.
- Subscriptions: put the renewal terms next to the button, repeat them in the confirmation email, and add a way to cancel online.
10

Sources

Not legal advice. This is a checklist from public sources, checked on Oct 7, 2026. Laws change and depend on where you and your users are; for your own situation, ask a lawyer.

Get the next guide

A free guide with every video, lesson 1 of Made by Agent free, and first access when the course opens. The reel itself was made by an AI agent, like every video on @feruzbuilds.