Tools like Lovable, Bolt, Cursor or Replit can take you from idea to live app in a weekend. What they don’t do is ask the boring questions: what your sign-up form collects, where your fonts load from, what your analytics records, what your emails are missing.
None of this depends on revenue. The penalties in these laws are counted per violation, per visitor, per session or per email. That is how an app with zero sales can still carry real exposure.
#The six gaps at a glance
| Gap | Law | What’s at stake | Fix |
|---|---|---|---|
| Kids’ data | COPPA (US) | Up to $53,088 per violation | Decide your audience, set an age rule, handle under-13s |
| Google Fonts | GDPR (EU) | €100 per visitor in one 2022 German case | Self-host your fonts |
| Session recording | CIPA (California) | $5,000 per violation claimed in lawsuits | Mask inputs, ask for consent |
| Marketing email | CAN-SPAM (US) | Up to $53,088 per email | Unsubscribe link and postal address |
| Subscriptions | California Automatic Renewal Law | Customer refunds, class actions | Clear terms, separate “yes”, easy cancel |
| User uploads | DMCA (US) | Losing your safe harbor | Register an agent: $6 |
#1. Kids’ data: COPPA

Still from our reel “Sued before your first sale”.
What the law says. The Children’s Online Privacy Protection Act applies if your app is aimed at children under 13, or if you actually know you are collecting personal data from a child under 13. In either case you need verifiable parental consent first. The FTC can seek civil penalties of up to $53,088 per violation. That is the 2025 level, which still applies in 2026.
What it doesn’t say. COPPA does not require you to ask users their age. The FTC’s own FAQ says so. The risk comes from building something kids use, or from learning a user is under 13 and doing nothing. Asking for age can actually give you that knowledge. The rule was updated in 2025, and companies had to comply by April 22, 2026.
The fix:
- Decide who the app is for, and write it in your Terms: “13+ only”, or 16+ or 18+ if that fits.
- Avoid kid-oriented design, characters or marketing if the app isn’t for kids.
- If you add an age check, make it neutral: let users type their birth month and year, with no “I’m over 13” box, and don’t let a blocked user simply go back and change the answer.
- Write down what you do when you learn a user is under 13: delete their data and close the account.
- If the app is for kids, stop and talk to a lawyer before launch.
#2. Google Fonts: an IP address sent to Google

Still from our reel “Sued before your first sale”.
What happened. In January 2022 the Munich Regional Court (LG München I, case 3 O 17493/20) ordered a website to pay a visitor €100 under the GDPR, and to stop sending his IP address to Google. The site loaded Google Fonts from Google’s servers, which passes every visitor’s IP address to Google, with no consent and no other legal basis. The court noted the fonts could simply be hosted on the site’s own server.
The context. The ruling set off a wave of mass demand letters in Germany, generated with crawlers. Berlin prosecutors raided the sender in December 2022, and later courts threw out these claims as abusive. The EU’s top court has since said a breach alone isn’t enough: the person has to show actual harm. And the GDPR only reaches apps outside the EU if they offer services to people in the EU or monitor them. So this is not “one German visitor, one lawsuit”. But the fix costs nothing.
The fix:
- Self-host your fonts. In Next.js,
next/font/googledownloads them at build time and serves them from your own domain. Otherwise use Fontsource, or put the files in yourpublicfolder. - Delete any
fonts.googleapis.comandfonts.gstatic.comlinks. - Open your browser’s Network tab and check that nothing still loads from Google.
#3. Session recording: California’s wiretap law

Still from our reel “Sued before your first sale”.
What the lawsuits say. Session-replay tools record what visitors do on your site: clicks, scrolling, sometimes every keystroke typed into a form. In California, plaintiffs’ lawyers have filed many suits under a 1967 wiretap law, the California Invasion of Privacy Act (Penal Code §631). They argue the replay vendor “listens in” on the visitor’s conversation with your site, and that you helped. The law allows $5,000 in statutory damages per violation (§637.2).
The context. Results are mixed. Many cases are dismissed, and courts disagree on what counts as a violation. But defending one is expensive. A 2026 reform, SB 690, only limits a different kind of claim (pen registers). It leaves wiretap claims like these untouched.
The fix:
- In your replay tool, mask all text inputs, not just passwords.
- Exclude sensitive pages entirely: checkout, account, and anything about health or money.
- Load the replay tool only after the visitor opts in, or drop replay and keep aggregate analytics.
- Name the tool and vendor in your privacy policy.
#4. Marketing email: CAN-SPAM

Still from our reel “Sued before your first sale”.
What the law says. Under the US CAN-SPAM Act, every commercial email needs a working unsubscribe option and your valid postal address. A registered PO box or virtual mailbox is fine. Opt-outs must be honored within 10 business days. There is no exception for B2B email, and a “We launched!” email is commercial. The FTC can seek up to $53,088 for each email that breaks the rules. State attorneys general and internet providers can also sue; individual recipients cannot.
The fix:
- Use your email provider’s standard footer (Resend, Postmark, Loops, Mailchimp…) with an unsubscribe link and a postal address.
- Connect unsubscribes to a suppression list, so nobody gets mailed again by mistake.
- Keep receipts and password resets separate from marketing.
- For people in the EU or UK, you generally need their consent before emailing them, not just an unsubscribe link.
#5. Subscriptions: California’s Automatic Renewal Law

Still from our reel “Sued before your first sale”.
What the law says. If you sell subscriptions to Californians, the renewal terms must be clear before the purchase and next to the buy button. Since July 1, 2025, customers must give a separate “yes” to auto-renewal, cancelling online must be as easy as signing up, and you must send an annual reminder and notice before price changes. Under §17603, goods shipped under a renewal the customer never properly agreed to count as an unconditional gift they can keep.
The context. Whether the “gift” rule covers software subscriptions is not settled in the courts. But refunds, regulators and class actions under California’s consumer laws are real risks either way. At the federal level, the FTC’s “click-to-cancel” rule was struck down in July 2025, but the FTC still pursues subscription traps under an older law (ROSCA).
The fix:
- Next to the buy button, show the price, how often you charge, “renews automatically until you cancel”, and how to cancel.
- Add a separate, unchecked checkbox: “I agree this subscription renews automatically”.
- Send a confirmation email with the terms and how to cancel.
- Add a self-serve cancel button. Stripe’s Customer Portal does this.
- Turn on renewal reminders: once a year, and before any price change.
#6. User uploads: the $6 DMCA agent

Still from our reel “Sued before your first sale”.
What the law says. If users can upload content (images, files, posts), the US DMCA offers you a “safe harbor”: you’re not liable for what they upload if you take it down when notified. To use it, you must register a DMCA agent with the US Copyright Office. It costs $6 and has to be renewed every 3 years.
The context. No agent doesn’t make you automatically liable. It means you can’t rely on the safe harbor, so a rightsholder can sue you directly and you’d have to win on the merits.
The fix:
- Register an agent at dmca.copyright.gov.
- Add a
/copyrightpage with the agent’s details and how to send a takedown notice. - Add a repeat-infringer clause to your Terms.
- Put a reminder in your calendar to renew in 3 years.
#Four more gaps worth checking
- A privacy policy that matches reality. California requires one if you collect personal data from Californians (CalOPPA). A template that doesn’t mention the analytics, pixels or replay tools you added can be a deceptive practice in the eyes of the FTC.
- Cookie consent for EU visitors. Non-essential cookies and trackers, analytics and ads included, need consent before they load.
- Accessibility. Website accessibility lawsuits are common in the US: over 3,000 federal suits in 2025, and California’s Unruh Act sets a $4,000 minimum per offense. Run Lighthouse or axe, add alt text and labels, and check keyboard navigation and contrast.
- An open database. In 2025, a flaw in Lovable-built apps (CVE-2025-48757) left Supabase tables readable and writable by anyone, because Row-Level Security wasn’t set up. Turn on RLS for every table, never ship the
service_rolekey to the browser, and test with the anon key.
#The checklist
Copy this and work through it this week:
- Terms say who the app is for (13+, 16+ or 18+), and you have a plan for under-13 users
- Fonts are self-hosted; nothing loads from
fonts.googleapis.com - Session replay masks all inputs and skips checkout and account pages, or only loads after consent
- Every marketing email has an unsubscribe link and a postal address
- Checkout shows renewal terms next to the button, with a separate checkbox and a self-serve cancel
- DMCA agent registered ($6) and a
/copyrightpage, if users can upload - Privacy policy names every tracking tool you actually use
- Cookie banner blocks trackers until consent, if you have EU visitors
- Lighthouse accessibility check passes
- Row-Level Security on every database table; no secret keys in the browser
#Why “per violation” matters
Each of these laws counts per violation, per visitor, per session or per email. None of the risks depends on revenue. Each fix takes minutes; finding them is the hard part, because the code was written fast and nobody read every line.
#How Altamar can help
If you built your app with AI and want a second pair of eyes, one of our engineers can go through your app with you: what it collects, what it loads, what it sends and who can reach your data. Book a free call.
#References
All checked on November 9, 2026.
- FTC, Complying with COPPA: Frequently Asked Questions: ftc.gov
- Amended COPPA Rule, 90 FR (Apr 22, 2025): federalregister.gov and 16 CFR Part 312: ecfr.gov
- FTC civil penalty amounts, 16 CFR 1.98: ecfr.gov; 2025 adjustment: federalregister.gov; 2026 notice (no change): govinfo.gov
- LG München I, judgment of 20.01.2022, 3 O 17493/20 (in German): gesetze-bayern.de
- LTO on the Google Fonts letter raids (in German): lto.de
- CJEU, C-300/21 Österreichische Post (May 4, 2023): curia.europa.eu
- California Penal Code §631 and §637.2: leginfo.legislature.ca.gov · §637.2
- SB 690 (2025–26): leginfo.legislature.ca.gov; Baker Donelson summary: bakerdonelson.com
- FTC, CAN-SPAM Act: A Compliance Guide for Business: ftc.gov
- California Business and Professions Code §17603: leginfo.legislature.ca.gov; AB 2863: leginfo.legislature.ca.gov
- WilmerHale on the 8th Circuit vacating the FTC click-to-cancel rule: wilmerhale.com
- US Copyright Office, DMCA Designated Agent Directory and FAQ: copyright.gov · FAQ
- California AG on privacy policies (CalOPPA): oag.ca.gov
- Seyfarth Shaw, website accessibility lawsuit filings in 2025: adatitleiii.com
- CVE-2025-48757: tenable.com






