Privacy and terms pages discoverable

What this means

Your home page links to a privacy policy and to terms of service, and both links return 200. A visitor, a payment provider or an ad reviewer can reach each page from the home page without guessing a URL. Failing means one of the links is missing from the home page HTML or the page it points to does not load.

How we test it

We fetch your home page, following at most 3 redirects, and look through its HTML for a link to a privacy page and a link to a terms page, by link text and by href. We then fetch each linked page, again with at most 3 redirects, and require a 200 status. Both links present and both returning 200 passes; a missing link or a non-200 response for either page fails and we say which.

Why it matters

Stripe, app stores and ad platforms require them; users expect them. A checkout, an app listing or an ad account review can stall on a missing policy page, and a visitor deciding whether to sign up looks for one. The Fix Kit treats the privacy page as part of measurement: it must be live and linked from the footer, name Google Analytics and the first-touch cookie it sets, and say how to opt out, and the runbook stops and asks rather than invent legal text.

The fix

Publish a privacy page at /privacy that names Google Analytics, the lp_first_touch cookie (90 days, and what it holds) and how to opt out, publish a terms page, and link both from the footer that every page, including the home page, renders; supply the text yourself or approve adapting a plain template, because the kit does not invent legal claims. Then confirm with curl -sI https://YOUR_DOMAIN/privacy | head -1 and the same for the terms URL that each returns 200. The full runbook is in the Fix Kit, Module 09.

Prompt for your AI

Paste this into the coding agent that built the app. It reproduces the finding and stops before changing anything; the fix steps are in the kit.

Do not change anything yet. This is a verification pass only.
Run: curl -sL --max-redirs 3 https://YOUR_DOMAIN/ -o /tmp/home.html
Run: grep -oiE '<a[^>]*href="[^"]*"[^>]*>[^<]*(privacy|terms)[^<]*</a>' /tmp/home.html
Print every privacy and terms link found, with its href, or say which one is missing.
For each href found, run curl -sIL --max-redirs 3 on the absolute URL and print the final HTTP status line.
Run: curl -sI https://YOUR_DOMAIN/privacy | head -1 and report the status even if no link was found.
Search the repo for the footer component or partial and show me whether it contains both links.
List what it would take to make both pages discoverable and return 200, without editing anything.
Verify: a privacy link and a terms link are both on the home page and both return HTTP 200; if either is missing or not 200, report which and stop.