Tracker check
Paste the address of a page on your site. We read the page the way a first-time visitor gets it and list the outside companies it talks to: analytics, ad pixels, session recording, chat, maps, videos and fonts, and which of them load before anyone clicks Accept.
Ad pixels and analytics are the evidence
Letters under California's wiretap law (CIPA) quote screenshots of a site sending visits to Google Analytics, the Meta Pixel or a chat tool before the visitor agreed. Small shops get them too.
You may not know they are there
Themes, ad apps, booking widgets and Google Tag Manager add tags without anyone editing the site.
Your policy has to name them
A cookie policy lists each outside service, what it is for and its cookies. The check gives you those rows to paste.
How the check works
We open the page once in a real browser on our server, as a first-time visitor, and click nothing for a few seconds. Every outside address it calls in that time is matched against about 55 known services, so tags that Google Tag Manager, a theme or an app adds while the page runs are seen too. Anything seen loading counts as loading before consent. A service that is in the page's code but didn't load counts as waiting for consent when a consent tool (Cookiebot, OneTrust, CookieYes and others) is on the page. When the browser is busy we read the page's code instead, and the result says so.
“Make my policy” puts a row and a line for each service into our cookie policy and privacy policy templates. Signed in, you can save both as drafts, fill in your company details and publish them.
The result describes what the page loads. It isn't legal advice and doesn't say whether a site complies with any law. Only public pages can be checked; nothing you paste is kept except the site's name and the services found, for counting.