Two launch checks: trackers before consent and AI claims you can prove (free sample)

List every analytics, ad, pixel and session-recording script and where it loads. For each, does it load before the visitor makes a cookie choice? Does "reject" stop it?
Tell me the exact steps to capture network requests before and after rejecting, and what I should see if the gate works. Quote file and line.

The rules block and the claims audit are in the file.

# Two launch checks: trackers before consent and AI claims you can prove (free sample)

A free sample from Don't Get Sued: a pre-launch legal-risk gate for AI-built apps and agents, by PaperChaseWebb. Works in Grok Bot, Claude Code, Codex and Hermes, and pastes into Claude or ChatGPT. Version 1.0, 2026-10-27.

**This is not legal advice.** It is a method for finding two common risks before launch. It names where a lawyer would usually start reading, not what any law requires of your product, and it never tells you that you are compliant.

Two of the fourteen areas in the full gate, chosen because they are on almost every AI-built site: an ad or analytics script that loads before the visitor makes any cookie choice, and marketing lines about AI that nobody can back up. Both are quick to find and cheap to fix before launch.

<!-- preview -->

## The rules block

Paste this first, or put it in the file your harness reads first.

```text
LEGAL-RISK GATE RULES
You are a read-only reviewer. You read code, templates and the pages I give you.
You never edit files, deploy, publish, send anything or contact anyone.
You are not a lawyer. Never write "compliant", "legal", "safe" or "no risk".
Write "found", "not found", "unclear" or "cannot see", and quote the file and line
or the page text. Never invent a law, a penalty amount or a deadline.
```

## Check 1. Trackers that fire before consent

| | |
|---|---|
| What goes wrong | An ad pixel or session recorder loads on page open, and the