Website Care · Starter

See what a site tracks before visitors say yes

You need to know what loads before consent, whether the cookie banner really works, and whether the privacy policy matches.

  • Any
  • Claude Code
  • Grok Build
  • Cursor
  • Codex CLI

For: Owner, Office manager, Tech person, Anyone at work · Updated November 10, 2026

A starting point: fill in the [brackets] with your own details, and check the answer before you use it. Tool screens change often, so yours may look a little different.

The prompts

Copy a quick prompt, or grab the full skill below.

QUICK PROMPT 1
Why this prompt works: Scope: the 'new visitor before consent' moment is where most problems show up.
Open the site I work on as a brand-new visitor. List every outside service that loads before I accept cookies, and what each does. Plain-language report only; not legal advice.
QUICK PROMPT 2
Why this prompt works: Asking for a test, not an opinion, gets evidence.
Test the cookie banner on the site I work on: if I click Reject, does tracking actually stop? Tell me what still loads, before suggesting changes.
QUICK PROMPT 3
Why this prompt works: Give two sources to compare so the assistant finds gaps, not generalities.
Compare the privacy policy of the site I work on with what the site actually loads. List mismatches for someone to review. Don't edit the policy.

What this covers: What loads before consent, whether Reject really blocks tracking, a list of every outside service, and mismatches with the privacy policy. Technical findings only, not legal advice.

For anyone improving a site or app, whether a small-business owner or someone at a larger company practicing better prompts. Visitors and regulators increasingly expect sites to collect only what they say they collect, and many sites load trackers they no longer use. Paste a prompt into any AI assistant that can see the site or repo.

Two ways to use it

  1. Any AI chat (Copilot, ChatGPT, Claude, Grok): copy one of the quick prompts above. Each one asks for a plain-language report first, so nothing changes until you say so.
  2. A coding agent working in the site’s code (Claude Code, Grok Build, Cursor, Codex CLI): save the full skill below as SKILL.md in a folder named privacy-and-tracking-review, for example .claude/skills/privacy-and-tracking-review/SKILL.md (Grok Build also reads that location, or use .grok/skills/). Then ask the agent to use the privacy-and-tracking-review skill. It audits first, makes the smallest safe changes in a review branch, and ends with a report.

Download SKILL.md · All Website Care skills

The full skill (SKILL.md)

Last reviewed Nov 10, 2026. Standards and tools change, so check anything dated before relying on it.

---
name: privacy-and-tracking-review
description: Use when asked what a website collects about visitors, whether its cookie/consent banner actually works, which analytics, ads, pixels, embeds, and fonts load before consent, whether the privacy policy matches reality, or how to switch to lighter, privacy-friendly analytics. Read-only inventory first, fixes as a review PR. Gives practical findings, not legal advice.
---

# Privacy, cookies, and tracking review

Last reviewed: 2026-11-10

## Quick prompts

For anyone improving a site or app, whether a small-business owner or someone at a larger company practicing better prompts. Visitors and regulators increasingly expect sites to collect only what they say they collect, and many sites load trackers they no longer use. Paste a prompt into any AI assistant that can see the site or repo.

1. "Open the site I work on as a brand-new visitor. List every outside service that loads before I accept cookies, and what each does. Plain-language report only; not legal advice."
   *Why this prompt works:* Scope: the 'new visitor before consent' moment is where most problems show up.

2. "Test the cookie banner on the site I work on: if I click Reject, does tracking actually stop? Tell me what still loads, before suggesting changes."
   *Why this prompt works:* Asking for a test, not an opinion, gets evidence.

3. "Compare the privacy policy of the site I work on with what the site actually loads. List mismatches for someone to review. Don't edit the policy."
   *Why this prompt works:* Give two sources to compare so the assistant finds gaps, not generalities.

## Hard limits

- This is a technical inventory, not legal advice. Flag questions for the owner's counsel; do not declare the site "compliant".
- Do not remove or change analytics, ads, or marketing tags without the owner's approval; they may be tied to revenue or contracts. Propose.
- Do not edit the privacy policy text; list mismatches for the owner.
- Do not log in to analytics or ad accounts unless the owner asks and signs in themselves. Review PR only.

## Inputs to gather

1. Target regions/audiences (EU/UK, California, other) and any consent platform in use.
2. List of tools the owner believes are installed (analytics, tag manager, pixels, chat, embeds, A/B testing, error tracking).
3. Privacy policy and cookie policy URLs.
4. Forms and what happens to submissions (email, CRM, newsletter provider).

## Interface-type notes

- **Content sites**: video embeds (YouTube/Vimeo set cookies; use privacy-enhanced modes or click-to-load facades), social share widgets, ad networks, Google Fonts from Google servers.
- **Marketing**: pixels (Meta, LinkedIn, TikTok), tag managers firing everything at once, session replay tools.
- **E-commerce**: payment and fraud scripts (necessary), marketing pixels (consent), abandoned-cart emails.
- **SaaS / app**: product analytics and session replay inside logged-in screens (mask inputs), error tracking that may capture personal data.

## Steps

1. **Fresh-visitor capture**: open key pages in a clean browser profile with no consent given. Record every request to a third-party domain, every cookie and `localStorage` key set, and when (before or after consent).
2. **Consent test**: reject all, then reload and navigate; nothing non-essential should load. Accept all; verify tags then load. Check the banner is keyboard accessible and that rejecting is as easy as accepting.
3. **Inventory**: table of vendor, purpose, cookies/storage set, loads before consent (yes/no), declared in policy (yes/no).
4. **Forms**: what fields are collected, whether they are needed, where data goes, retention, and whether spam protection sends data to a third party.
5. **Signals**: check whether the site honors Global Privacy Control (`Sec-GPC`) where relevant to the audience.
6. **Recommendations**: gate non-essential tags behind consent; replace heavy tools with lighter ones (cookieless analytics, self-hosted fonts, click-to-load embeds); remove unused tags; mask personal data in session replay and error tracking.

## Validation

After any PR change, repeat the fresh-visitor and reject-all capture on the preview and diff the request and cookie lists against the baseline.

## Report format

1. Region assumptions and scope.
2. Vendor inventory table (above), with before-consent loads highlighted.
3. Consent banner behavior (reject/accept/keyboard).
4. Policy mismatches for the owner and their counsel.
5. Proposed changes, split into "in PR" and "needs owner decision". PR link, "not merged".

## References

- MDN Using HTTP cookies: https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Cookies
- MDN Third-party cookies: https://developer.mozilla.org/en-US/docs/Web/Privacy/Guides/Third-party_cookies
- Global Privacy Control: https://globalprivacycontrol.org/
- European Data Protection Board guidelines on consent: https://www.edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-052020-consent-under-regulation-2016679_en
- UK ICO guidance on cookies: https://ico.org.uk/for-organisations/direct-marketing-and-privacy-and-electronic-communications/guide-to-pecr/cookies-and-similar-technologies/
- YouTube privacy-enhanced mode: https://support.google.com/youtube/answer/171780
- web.dev third-party facades: https://developer.chrome.com/docs/lighthouse/performance/third-party-facades

Check before you send

  • It gave a plain-language report before suggesting or making any change
  • Each finding names the exact page or file and why it matters
  • It said what it could not check or verify
  • Nothing was changed, published, or deleted without your OK
  • Fixes are small and keep the existing design and content

Privacy note: what not to paste

Use a fresh browser profile with no logged-in accounts. Don’t paste visitor data, analytics exports with personal details, or cookie values. This is a technical review, not legal advice.