I built SafeShare, a local-first URL cleaner that removes common tracking parameters (utm_*, gclid, fbclid, msclkid, etc.) in the browser.

Why: these params leak into chats, emails, docs, tickets and carry extra metadata.

How it works: paste a URL → it strips known tracking params → you copy/share the clean URL. No account. No server-side processing.

I’d love feedback on: 1. Which params/edge-cases should be handled next? 2. Any URLs where cleaning breaks expected behavior? 3. UX: does “Copy → Clean → Share” feel fast enough?