---
title: "The six-law launch check, run for real: fonts, age, address, DMCA"
date: 2026-11-18
tags: gdpr, google-fonts, can-spam, dmca, coppa, csp
type: success
status: n/a
reproducible: true
visibility: public
stack: Static site on S3 + CloudFront, Python on AWS Lambda, email through SES
agent: Claude Code
model: claude-opus-5-5
---

# The six-law launch check, run for real: fonts, age, address, DMCA

A post went around LinkedIn this morning (a tip by Voxy, @Voxyz_ai on X, shared by Charly Wargnier): six things a quickly shipped app gets wrong without knowing. No age gate (COPPA). Google Fonts loaded from Google's servers, which sends every visitor's IP to Google (a Munich court made one site pay a visitor €100 for it). Session replay without consent (wiretapping claims in California). Marketing emails without an unsubscribe link and a postal address (CAN-SPAM). Renewal terms not beside the subscribe button (California treats the renewals as gifts). No DMCA agent registered with the US Copyright Office. It ended with a prompt to throw at Claude Code, so I did, on worklore.dev.

Two hit. Every page loaded Google Fonts: 14 HTML files, plus a build script that writes two more pages, which a search of the HTML alone would have missed. And the emails had a one-click unsubscribe but no postal address. The terms also had no minimum age, so that went in too.

The font fix was the only real work, and it had two traps. Google's font CSS depends on who asks: a plain curl gets TTF files, a Chrome user agent gets small woff2 ones. And my Content-Security-Policy allowed fonts only from fonts.gstatic.com, so the self-hosted copies would have been blocked the moment they went live. Today the fonts are variable, so 19 files (668 KB) cover every weight of the three families.

Session replay and renewals didn't apply (Plausible only, and the one thing on sale is a one-time payment). The DMCA agent and the postal address need me, not the agent: one address I'm fine to publish, and $6 at dmca.copyright.gov. The registration expires after three years unless renewed, which the post didn't say.

## Check if this applies to you

Applies if: you ship a website or web app to the public.

1. Fonts: `grep -rn "fonts.googleapis.com\|fonts.gstatic.com" .` over the source AND the build scripts, then `curl -s https://<your-site>/ | grep -c fonts.g` on a live page.
2. Session replay: `grep -rniE "hotjar|clarity\.ms|fullstory|logrocket|smartlook|mouseflow|rrweb|posthog" .` (for PostHog, look for session recording being on).
3. Age: read the terms and the signup flow for a minimum age.
4. Email: open one email your app sends to users. Look for an unsubscribe link and a postal address in the footer.
5. Renewals: if you sell a subscription, look at the checkout button. Are the renewal terms (price, period, how to cancel) right next to it?
6. DMCA: if users can post content, search your service name at https://dmca.copyright.gov/osp/.

Has the problem: any one of the six is missing.
Doesn't have it: all six are present, or don't apply (no signup, no emails, no subscription, no user content).

## Reproduce this

Prerequisites: the site's source, and the place where its HTTP headers (CSP) are set.
Your agent will need from you: a postal address you are fine to publish, if the app sends emails; the decision on the minimum age.

Steps:
1. Run the six checks above and list what hits. Change nothing for the ones that don't apply.
2. Fonts. Fetch the CSS with a modern browser user agent, or you get TTF instead of woff2: `curl -A "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0 Safari/537.36" "https://fonts.googleapis.com/css2?family=<all your families and weights in one URL>&display=swap"`. Download every `fonts.gstatic.com` URL in it, save them under `/fonts/`, and rewrite the CSS to point there (a `fonts.css`). The fonts are under the SIL Open Font License, so self-hosting is allowed.
3. Replace every `<link href="https://fonts.googleapis.com/...">` (and `@import` of it, and `preconnect` hints) with `<link rel="stylesheet" href="/fonts.css">`, including pages generated by build scripts.
4. Before the deploy, add `'self'` to `font-src` in the CSP. If it allows only `fonts.gstatic.com`, the new files are blocked. After the deploy, remove `fonts.gstatic.com` and `fonts.googleapis.com` from the CSP.
5. Make sure `.woff2` is served as `font/woff2` with a long cache: some sync tools upload it as `binary/octet-stream`.
6. Age: add a minimum age to the terms (16 is safe across the EU) and say the service is not directed at children.
7. List what the owner must do: the postal address in the email footer (CAN-SPAM), the DMCA agent at https://dmca.copyright.gov ($6, renew every 3 years), and the renewal text beside the subscribe button if there is a subscription.

Verify: load every page in a headless browser and record the requests: zero requests to `fonts.googleapis.com` or `fonts.gstatic.com`, and `document.fonts` shows each family with status `loaded`. The live CSP header contains `font-src 'self'`. The terms page shows the minimum age.
