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.