Safeshare

I’ve been building SafeShare — a small tool that removes tracking parameters from links directly in the browser.

The goal is simple: make links easier to share without extra tracking junk attached.

Example:

Before:

https://example.com/article?utm_source=newsletter&utm_medium=email&fbclid=abc123&id=42

After:

https://example.com/article?id=42

It’s live now as a web app, with shortcuts, bookmarklets, and a Pro version.

I’m at the stage where I want honest feedback from outside my own bubble: is the value clear, and does this feel useful enough to become part of people’s workflow?

https://safesharepro.com/en/

I’m building SafeShare: a small web tool that removes tracking parameters from URLs (utm_*, fbclid, gclid, msclkid, etc.). It runs local-first in the browser — no uploads.

Use case: you copy links from Messenger / YouTube / newsletters / news sites and want to share them without extra tracking “ballast”.

What I’d love feedback on:

1. UX: Is “Copy → Clean → Share” fast/intuitive enough on mobile?

2. Edge cases: which parameters should never be removed?

3. Integrations: do you prefer a simple web app, or shortcuts/share-sheet style flows (iOS/Android)?

Link: https://safesharepro.com/app/en/

SafeShare started as a simple “paste link → remove tracking params → share clean.”

People kept asking for a paid version that’s still privacy-respecting (no accounts, no analytics fingerprinting, no server-side rewriting). So Pro is my answer.

What Pro adds (vs. the free web app):

• more powerful cleaning rules + safer defaults (less “oops, link broke”)

• domain/profile style workflows (so different sites can behave differently)

• a Pro app + a short handbook (so users don’t need to guess what’s safe to remove)

• sold as a download/license (Payhip), not a subscription

I’m trying to make a sustainable indie product without turning user data into the business model.

Free app: https://j-ai-71.github.io/Supersystem/

Pro (Payhip):

• Pro Person: https://payhip.com/b/djqDz

• Pro Team: https://payhip.com/b/oXFsk

Question for other builders:

If you’d pay for a URL cleaner, what would make Pro actually worth it for you: bulk cleaning, saved profiles, export/audit log, “explain what was removed,” or something else?

Hey Indie Hackers,

I’ve been working on a small privacy-focused tool called SafeShare and just put the first public version online.

What it does

– You paste a URL into the web app.

– SafeShare removes common tracking parameters (utm_*, gclid, fbclid, etc.).

– It tries to unwrap obvious redirect parameters like url=, u=, redirect=, so you see the actual destination.

– It returns a “cleaner” link you can copy or open and then share in mail, messengers, social, newsletters, etc.

What it deliberately doesn’t do

– It’s not a malware or deep security scanner.

– It doesn’t try to follow every network redirect hop.

– It doesn’t create accounts, user profiles or tracking cookies.

I wanted something that focuses on link hygiene and digital self-determination, not on maximising data extraction.

How it’s built

– Plain browser-based web app, hosted on GitHub Pages

– Links are processed locally in the browser

– No backend database, no login, no external analytics

App: https://j-ai-71.github.io/Supersystem/app.html

Code: https://github.com/j-ai-71/Supersystem

Monetisation (early idea)

I’m experimenting with a small SafeShare Pro offering for people and small teams who handle links daily (newsletter writers, bloggers, small orgs). The idea is:

– keep the core app free and simple

– offer paid extras around workflows, templates, team usage and education

– avoid dark patterns and heavy-handed DRM, rely on clear communication instead

What I’d love feedback on

– From a user perspective: what would make you actually adopt a tool like this in your own workflow?

– From a builder perspective: does the positioning (privacy / link hygiene, not “yet another SEO tool”) make sense?

– For a small paid version: what kind of “pro” features or assets would you expect (or be willing to pay for)?

Happy to hear any thoughts, critiques, or “I’d use it if it did X instead of Y” comments. Thanks for reading.

SafeShare removes tracking params (utm_, gclid, fbclid, etc.) and unwraps common redirects (google.com/url, t.co) entirely in the browser. No accounts, no logs. Works as a small PWA + bookmarklets; a Pro add-on adds bulk cleaning and CSV export. Demo + details: https://j-ai-71.github.io/Supersystem/ (DE). If preferred, I can add an EN page—feedback welcome.

Ich habe SafeShare gebaut, weil mich UTM-Ballast & Weiterleitungs-Ketten nerven. Ein Klick, sauberer Link, alles lokal. Würde gern hören: Was fehlt für Publisher/NGOs?

Link: https://j-ai-71.github.io/Supersystem/index.html?utm_source=ih&utm_medium=post&utm_campaign=launch