Guide
Cookie policy generator from a site scan
Draft a cookie policy grouped by the trackers, chat widgets, and payment scripts on your URL.
Cookies are not the whole stack
PostHog, Google Analytics, Hotjar, Clarity, and the Meta Pixel set cookies or similar storage. Plausible and Fathom are built to avoid an advertising cookie, and they still belong on the page because they receive the URL. Resend and a server-side database often set nothing in the browser. A cookie policy that only says 'we use cookies' hides that difference.
What the scan records
The scanner writes down cookie names it sees and the storage keys in the browser, then attaches the documented names from the signature file. The draft groups them into payments, auth, analytics, session replay, advertising, and support chat. You can block cookies in the browser; the policy says that, and it says sign-in may break if you block the auth cookie.
TermsPack generates templates from what we detect on your site. This is not legal advice and does not create an attorney–client relationship. Have a lawyer review documents for your situation.