Fast, clear help on what SafeShare removes, what may stay, and where the limits are.
SafeShare should help in a practical way, not create confusion. Here you will find the most important answers, typical error sources, and the right next step.
If something does not work as expected, it is often caused by small things that are easy to fix.
https://.? part.SafeShare removes typical tracking parameters such as utm_*, gclid, and fbclid. Depending on the chosen logic, partner or affiliate values and coupon codes may also be removed or deliberately kept.
Not every parameter is tracking. Some values are functionally necessary, for example for language, product ID, search, filters, or page state. Others may deliberately stay in the link depending on the chosen logic, such as partner values.
No. Cleaning runs directly locally in the browser. Entered links are not stored by SafeShare and are not uploaded to third parties.
Yes. SafeShare works directly in the browser on smartphone, tablet, and desktop.
No. There is no such thing as being invisible on the web. SafeShare reduces one specific part of the data trail: tracking additions in shared URLs.
Because some links either contain very little tracking or because the existing values are functionally necessary. SafeShare is meant to make links cleaner, but not to simplify them so aggressively that they break.
Depending on the context, different questions matter: email, messenger, or social posts often come with different pitfalls.
Clean links before sending so recipients get cleaner URLs.
Open guideCheck and clean links in chats before passing them on.
Open guideFor posts, profiles, and bios: cleaner and more trustworthy URLs.
Open guideWant to understand more precisely which values are removed, which may stay, and why? Then the rules page is the right next step.
Your question is not listed here or something behaves unexpectedly? Then write directly.