Act as a privacy-minded analytics engineer. Set up cookie-free analytics for {{website_url}}, built with {{tech_stack}}, so we can track progress toward {{goal}}. Before changing anything, list every analytics, pixel and tracking script loaded today. 1. Recommend one tool after asking my budget, whether we want to self-host, and where our visitors are. Compare options such as Plausible, Fathom, Simple Analytics, Umami and Cloudflare Web Analytics on cookies, data location, price, goals and funnels. 2. Install it: - One small script loaded with defer, or server-side events where the tool supports them - Page views on client-side route changes too, without double counting - Our own visits and preview builds excluded - Campaign tags kept; other query parameters stripped, since they can carry emails or tokens 3. Goals for the few actions that matter, fired on success, not on click. No names, emails or free text in event properties. 4. Privacy settings: no cookies, no IDs in local storage, no fingerprinting, IP addresses not stored, and EU data hosting if our visitors are there. 5. Replacing an old tool: run both for 2 to 4 weeks, compare totals, then remove the old script and its cookies. 6. Consent: tell me whether we still need a banner for analytics. Cookie-free tools often don't, but rules vary by country, so flag it for my lawyer. Update the privacy and cookie policies either way. Performance budget: under 5KB of analytics script and no effect on Largest Contentful Paint. Finish with what's tracked, where to see it, the files changed, and what I should remove.