Handbook

1) What SafeShare Pro is

SafeShare Pro is a local tool for clean, explainable link cleaning. The app runs in the browser, processes links directly on your device, and shows not only the result but also the path that led to it.

What SafeShare Pro actually does

• removes common tracking and campaign parameters such as utm_*, fbclid, or gclid
• detects redirects and intermediate links and first tries to extract the actual target link
• handles known platform patterns in a targeted way, for example Google, Facebook/Meta, Instagram, LinkedIn, Reddit, X/Twitter, TikTok, Amazon, and YouTube links
• treats file, image, media, and preview links more carefully than normal web links, including technically sensitive cases such as signed file or media URLs, proxy previews, and Google image wrappers
• shows for each link what was detected, removed, or kept
• creates a copyable support report when needed

What SafeShare Pro is not

Why Pro is more than just a URL cleaner

SafeShare Pro does not only show a cleaned link. It also explains the structure of the original link: where it comes from, which parts it contains, which parts were recognized as target link, context, tracking, partner marker, or function, and why something was removed or deliberately kept.

When SafeShare Pro is especially useful

• when you want to share links more cleanly
• when you want to understand what is actually inside a long link
• when you want to remove tracking ballast but keep functionality
• when you want to make conscious decisions around partner, shop, social, or redirect links
• when you want to document exactly what the app did in a support case

Platform status

SafeShare Pro currently runs as a local browser app. The shared cleaning logic is cross-platform, but not every platform is already worked out to the same degree as its own product path.

• Apple devices: currently tested and documented most deeply
• Android: the shared core logic is browser-based and platform-neutral. In this state, however, Android has not been checked separately to the same depth as Apple devices. The current focus is stable shared core logic, not platform-specific polish.
• Desktop: generally usable in the browser; the current focus is stable shared core logic rather than platform-specific fine-tuning

2) Quick start

This is how to use SafeShare Pro in daily practice: paste a link, choose the mode, check the result, and copy or document it if needed.

Step 1: Paste one link or multiple links

Paste one or multiple links into the input field. If you want to check multiple links at once, the rule is: one link per line.

Step 2: Choose the mode

SafeShare Pro currently works with two clear modes:

• Clean link + partner = common tracking and measurement extras are removed, tag and ref stay
• Clean link = common tracking and measurement extras are removed, and tag and ref are removed as well

Step 3: Set toggles if needed

SafeShare Pro currently has two additional toggles:

• Keep coupon = only decides about coupon
• Remove ambiguous codes = affects extra parameters that are not clearly recognizable as tracking and not clearly necessary for functionality

Step 3.1: Keep coupon

The Keep coupon toggle only decides about coupon:

• off = coupon is removed
• on = coupon stays

Step 3.2: Remove ambiguous codes

This toggle affects extra parameters that are not clearly recognizable as tracking and not clearly necessary for functionality.

• off = such extra parameters are more likely to stay
• on = such extra parameters are additionally removed

Step 4: Clean

Click Clean. SafeShare then analyzes each link individually:

• recognize link type and context
• extract a possible target link from redirects or intermediate links
• distinguish tracking, context, and functional parts
• produce a cleaned result

Step 5: Check the result

After cleaning, you first see the collected output and below that the individual result cards. There you can check per link:

• what was originally pasted
• what the cleaned link looks like
• where the original link came from
• which parts were recognized
• what was removed and what was kept

Step 6: Copy or document the result

If the result looks right, you can copy the cleaned link directly. If you want to trace or share a case, you can also open and copy the Support report.

3) How SafeShare decides

SafeShare Pro does not work by the simple rule “remove everything”. The app currently follows a fixed, traceable rule logic: remove clear ballast, preserve functional parts where possible, and resolve intermediate links first before cleaning the actual target link.

How a link is structured in general

Before SafeShare decides, the link is first broken down into its basic parts. This helps explain what is actually the base, a parameter, or an anchor.

https://example.com/page?utm_source=newsletter&x=1#start

• https://example.com/page = the base of the link
• ? starts the parameter section
• utm_source=newsletter = one single parameter
• & separates parameters from one another
• x=1 = another single parameter
• #start = an anchor within the target page

3.1 What SafeShare safely removes

These parts are typically not needed to open the target page normally. They often only serve campaign analysis, click attribution, or platform tracking.

• campaign parameters such as utm_*
• click IDs such as fbclid, gclid, msclkid
• share and platform extras that do not belong to the actual target page
• redirect context such as technical outer fields in intermediate links

3.2 What SafeShare can deliberately keep

Not every parameter is ballast. Some things belong to the function of the link or are deliberately wanted. Those are therefore not removed blindly.

• functional video parameters such as v, list, t, start
• shop or content parameters such as lang, variant, sku, id
• partner and reference markers such as tag and ref when the matching mode is active
• coupon when the Keep coupon toggle is active
• anchors such as #start when they belong to the function of the link

3.3 What SafeShare unwraps first

Some links do not directly contain the target page, but first an outer intermediate link. In such cases SafeShare does not blindly clean the outer link, but first tries to extract the actual target link.

Typical cases are:

• Google intermediate links with a target in q=...
• Facebook/Meta intermediate links with a target in u=...
• Instagram, LinkedIn, or Reddit redirects with known target fields
• other redirects with fields such as url, target, redirect, or similar

3.4 What SafeShare handles depending on context

Not everything is clear. Some parts can have different meanings depending on platform, link type, or use case. That is why SafeShare deliberately handles some things depending on context.

• tag can be partner attribution
• ref can carry reference, attribution, or origin
• coupon can be a deliberately wanted discount code
• id or source can be functional or only context
• an outer redirect can carry tracking and still contain an important target link

What this means in practice

So SafeShare does not simply “remove everything after the question mark”. Instead the link is split into individual parts. Each part is classified as target link, tracking, platform context, partner marker, coupon, functional parameter, or anchor. That is what produces the actions extracted, removed, or kept.

4) Cleaning modes and toggles

SafeShare Pro currently works with two clear cleaning modes and two additional toggles. The most important difference between the modes is not classic tracking parameters — those are removed in both modes — but whether partner and reference markers should stay.

4.1 Clean link + partner

This mode is meant for cases where a link should be cleaned without destroying deliberately wanted partner or reference markers.

• kept: tag, ref
• removed: typical tracking and campaign parameters such as utm_*, fbclid, gclid, and so on
• coupon only stays if the coupon toggle is active

4.2 Clean link

This mode is for cases where a link should be cleaned not only from tracking ballast, but also from partner and reference markers.

• removed: tag, ref
• also removed: typical tracking and campaign parameters such as utm_*, fbclid, gclid, and so on
• coupon only stays if the coupon toggle is active

4.3 Keep coupon, if active

The coupon toggle only affects coupon. It does not decide about tag or ref, but only whether a discount or offer code remains in the link.

• toggle off = coupon is removed
• toggle on = coupon stays

4.4 Remove ambiguous codes

This toggle affects extra parameters that are not clearly recognizable as tracking and not clearly necessary for functionality. It is meant for edge cases — not for classic tracking.

• not a clear tracking case: not as obvious as utm_*, fbclid, or gclid
• not a clear functional case: not as obvious as v, list, t, w, or format
• typical examples: ref_code or similarly named extra fields whose role is not clearly recognizable in the concrete link

• toggle off = such extra parameters are more likely to stay
• toggle on = such extra parameters are additionally removed

4.5 The four most important combinations at a glance

What stays the same in both modes

SafeShare removes clear tracking ballast in both modes and tries to preserve functional parts of the link. The difference is not the general tracking logic, but the deliberate handling of partner and reference markers.

5) Recognizing link types

SafeShare Pro does not only try to remove parameters. It first tries to understand what kind of link it is dealing with. That matters because a normal web link, a Google intermediate link, a Facebook redirect, an Amazon shop link, or a YouTube link do not have the same structure.

5.1 General web link

A general web link is a normal direct link that points directly to the target page and does not contain a recognizable outer intermediate link.

https://example.com/page?utm_source=newsletter&x=1

In this case SafeShare works directly on the visible link: tracking is removed, and functional parts such as x=1 may stay.

5.2 Google / search redirect

With Google or search intermediate links, the visible original link is often not yet the actual target page. Instead, the real target link is inside a parameter such as q.

https://www.google.com/url?q=https%3A%2F%2Fexample.org%2Fpage%3Futm_source%3Dgoogle%26x%3D1&sa=D&source=hangouts&ust=158

SafeShare first recognizes the outer wrapper https://www.google.com/url, extracts the target link from q=..., and only then cleans the actual target link. Extras such as sa, source, or ust belong only to the redirect context and not to the target page itself.

5.3 Facebook / social redirect

Social platforms also often use intermediate links. With Facebook or Meta, the actual target link is typically stored in u=..., while other fields only carry platform context or redirect extras.

https://l.facebook.com/l.php?u=https%3A%2F%2Fexample.net%2Fpage%3Ffbclid%3DXYZ%26x%3D1&h=AT0

SafeShare first recognizes the outer wrapper https://l.facebook.com/l.php, extracts the target link from u=..., and then removes platform-typical extras such as fbclid or h=... if they do not belong to the actual target page.

5.4 Amazon / shop link

Amazon links are usually not redirect wrappers, but direct shop links. Even so, they often contain tracking, partner markers, references, coupon fields, or other shop extras.

https://amazon.de/dp/B0ABCDE123?tag=partner-21&ref=abc&utm_source=whatever&coupon=SAVE10

SafeShare does not treat such links like search redirects, but as shop links with product, partner, and offer logic. Clear tracking extras are removed, while tag, ref, and coupon are kept or removed depending on settings.

5.5 YouTube / video link

YouTube links are also direct target links, but with video-specific parts. The main issue here is not redirect resolution, but removing unnecessary share context without breaking the actual function of the video link.

https://www.youtube.com/watch?v=abc12345678&list=PL123&t=45s&si=XYZ#start

SafeShare recognizes typical video parts here:

• v = video ID
• list = playlist
• t = start point
• si = share context
• #start = anchor

This allows the app to remove unnecessary share context while preserving video function and playback context.

5.6 File link

File links point directly to files such as PDFs, ZIPs, or similar formats. SafeShare treats these more carefully than normal web links so technically important parts are not removed unnecessarily.

https://example.com/files/report.pdf?utm_source=mail&id=42

Typical tracking extras such as utm_source are removed. Potentially functional or technical parts such as id=42 are more likely to stay.

5.7 Image link

Image links point directly to image files or image-like resources. SafeShare works more carefully here because parameters such as size, format, or quality can matter for rendering.

https://example.com/images/photo.jpg?utm_source=mail&w=1200&format=webp

Tracking is removed, while technical image parameters such as w or format may stay.

5.8 Media link

Media links point directly to audio or video files. Here too, SafeShare treats the link more carefully so technically important information is not lost unnecessarily.

https://media.example.com/audio/podcast.mp3?utm_source=feed&quality=high

Typical tracking is removed, while functional parts such as quality=high may stay.

5.9 Preview link

Preview links are often technically sensitive thumbnail, proxy, or preview links. These are not treated like normal web links because aggressive cleaning can break them more easily.

https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9Gc...&s=10

In such cases SafeShare may show a warning state and leave the link unchanged or only treat it very carefully.

Why link type recognition matters

Link type recognition does not only provide a label. It changes how individual parts are read and explained. A field such as q can be the actual target link in a Google intermediate link, while in a normal web link it would only be a general parameter. A field such as h can be platform context in Facebook, but something entirely different on another site.

6) Parameter categories in detail

SafeShare Pro does not only decide by link type, but also by the category of an individual part. Two parameters can look similar and still play completely different roles. That is why parameters should not be treated as all the same, but according to function, context, and meaning.

6.1 Campaign and measurement parameters

These parameters typically serve campaign analysis, origin tracking, or marketing performance. They are usually not needed for the target page itself and are therefore removed.

• utm_source
• utm_medium
• utm_campaign
• utm_term
• utm_content
• and generally everything with utm_*

https://example.com/page?utm_source=newsletter&utm_medium=email&x=1

6.2 Click IDs

Click IDs are attribution markers from platforms or ad systems. They often show through which click, ad, or source an opening happened. They are usually not needed for the target page itself.

• fbclid
• gclid
• msclkid
• dclid
• twclid
• ttclid

6.3 Target-link parameters

These parameters do not only contain extra information, but often the actual target link itself. In such cases they are not read as normal parameters, but extracted first.

• q
• u
• url
• target
• redirect
• destination

https://www.google.com/url?q=https%3A%2F%2Fexample.org%2Fpage%3Futm_source%3Dgoogle%26x%3D1&sa=D

6.4 Platform and redirect context

These parts often do not belong to the target page itself, but to the outer wrapper, the platform, or the redirect system. They are therefore usually removed.

• sa
• source
• ust
• usg
• ved
• h in social/Facebook context

https://l.facebook.com/l.php?u=https%3A%2F%2Fexample.net%2Fpage%3Fx%3D1&h=AT0

6.5 Partner and reference markers

These parameters can carry deliberately wanted attribution. They are not automatically “good” or “bad”, but depend on whether you want to keep that attribution.

• tag
• ref

6.6 Coupon

coupon is a special case. It is not a classic tracking parameter, but can be a deliberately wanted discount or offer code.

That means:

• toggle off = coupon is removed
• toggle on = coupon stays

6.7 Functional parameters

Functional parameters do not control tracking, but the actual function or view of a link. That is why they often stay.

• v = video ID
• list = playlist
• t or start = start point
• lang = language
• variant = variant
• sku = product identifier
• id = identifier when functionally relevant

6.8 Ambiguous or not clearly classifiable extra parameters

Some parts are neither clearly tracking nor clearly functional. SafeShare deliberately handles such cases cautiously.

• not clearly tracking: not as obvious as utm_*, fbclid, or gclid
• not clearly functional: not as obvious as v, list, t, w, or format
• why it matters: such extra parameters can stay depending on the link, or be additionally removed with the Remove ambiguous codes toggle

6.9 Anchors

An anchor begins with # and is no longer part of the normal parameter section of the link. It points to a specific section within the target page.

https://www.youtube.com/watch?v=abc12345678&t=45s#start

SafeShare does not treat such parts as normal campaign or measurement parameters, but as their own functional part of the link.

Why this distinction matters

If all parts were treated the same, many links would become shorter, but also more broken. That is exactly why SafeShare separates tracking, click attribution, target link, platform context, partner marker, coupon, function, and anchor.

7) Understanding the result card

After cleaning, SafeShare Pro does not only show a collected output, but also an individual result card for each link. This card exists to make the cleaning traceable: What went in, what came out, where did the link come from, which parts were recognized, and why was something removed or kept?

7.1 Original link

The original link shows exactly the link you pasted. It is the starting point of the analysis. That way you can always check what actually went into the app.

7.2 Cleaned link

The cleaned link is the result after analysis. That is the link you ultimately want to share, copy, or document.

7.3 Where the original link comes from

This section shows the first outer part of the original link, the wrapper from which the visible link comes. That is especially important with redirects and intermediate links.

This section helps you distinguish: Is the original link already the actual target page — or only an outer wrapper?

7.4 How SafeShare reads the link

This section explains the basic structure of a link. SafeShare first splits the link into base, parameters, and anchor.

7.5 Link parts

The most important part of the result card is the table of individual link parts. There SafeShare breaks the link into traceable units.

This allows you to see not only that something was removed, but also why SafeShare read it as target link, tracking, context, function, or partner marker.

7.5.1 How to read the table in practice

The best way to read the table is from left to right:

This way you can see not only what was ultimately removed or kept, but also how SafeShare understood the component in the first place.

7.6 Summary

At the end of the result card there is a short summary. It is the most compact reading layer of the card and shows the most important groups at a glance depending on the case.

• Removed = clearly removed tracking or context extras
• Functional parameters kept = deliberately preserved functional parts
• Partner markers kept = deliberately preserved partner or reference markers
• Extra parameters removed by toggle = unclear edge cases additionally removed
• Extra parameters kept by toggle = unclear edge cases deliberately not additionally removed

This summary does not replace the table, but is the quick short view of the result. If you only want to know what happened in the end, this section is often enough. If you want to understand it more deeply, the table above is decisive.

How to read the card best

In practice this order makes the most sense:

1. look at the original link
2. look at the cleaned link
3. check where the original link comes from
4. read the table from left to right
5. use the summary at the end as a short view

8) Practical examples

The following examples show how SafeShare Pro handles typical link types. The goal is not only a shorter link, but a traceably cleaned one: tracking out, function preserved where possible, intermediate links unwrapped first.

8.1 Normal UTM link

A normal web link with classic campaign parameters.

• recognized type: Normal web link
• removed: utm_source, utm_medium, utm_campaign
• kept: x=1

The utm_* parameters are typical campaign and measurement values. x=1 is not a clear tracking standard case here and stays in this example.

8.2 Google intermediate link

Here the visible original link is not yet the actual target page. The real target link is inside q=....

• recognized type: Intermediate link with extracted target
• extracted: target link from q=...
• removed: sa, source, ust, and inside the target link utm_source
• kept: x=1

SafeShare does not simply remove parameters from the outer Google link here. It first extracts the target link. Only after that is the actual target link itself cleaned.

8.3 Facebook redirect

Here too, the visible link is first only a platform wrapper. The actual target link is inside u=....

• recognized type: Intermediate link with extracted target
• extracted: target link from u=...
• removed: h=AT0 as platform context and fbclid=XYZ inside the target link
• kept: x=1

The outer Facebook link is recognized as a platform wrapper. SafeShare therefore separates target link, platform context, and actual ballast in the inner link.

8.4 Amazon link with partner markers

Amazon is not a classic redirect case, but a shop link with product, partner, and offer logic.

• Clean link + partner + coupon off: tag and ref stay, utm_source and coupon go out
• Clean link + partner + coupon on: tag, ref, and coupon stay, utm_source goes out
• Clean link + coupon off: tag, ref, utm_source, and coupon go out
• Clean link + coupon on: tag, ref, and utm_source go out, coupon stays

This example shows the core of the current Pro app logic: tag and ref depend on the mode, coupon depends on the coupon toggle, and classic tracking is removed in all variants.

8.5 Edge case with an ambiguous code

Some parameters are neither clearly tracking nor clearly functionally necessary. That is what the Remove ambiguous codes toggle is for.

• clearly removed: utm_source
• edge case: ref_code
• toggle off: ref_code is more likely to stay
• toggle on: ref_code is additionally removed

This example shows the difference between clear tracking and an unclear extra parameter: utm_source is removed in both cases, while ref_code depends on the toggle.

8.6 YouTube link with playlist and start time

YouTube links often contain a mix of functional parts and unnecessary share context.

• recognized type: Video link
• functionally kept: v as video ID, list as playlist, t as start point, #start as anchor
• removed: si=XYZ as share context

SafeShare does not try to shorten the video link as much as possible here. It tries to preserve the function of the link: the right video, the playlist, the start point, and the anchor stay, while unnecessary share context goes away.

8.7 File link

File links are treated more carefully than normal web links.

• recognized type: File link
• removed: utm_source
• kept: id=42

8.8 Image link

Image links are more likely to keep technical display or format information.

• recognized type: Image link
• removed: utm_source
• kept: w, format

8.9 Media link

Media links are treated similarly carefully as image and file links.

• recognized type: Media link
• removed: utm_source
• kept: quality=high

8.10 Preview link

Preview links may deliberately stay unchanged when aggressive cleaning would be risky.

• recognized type: Preview link
• typical reaction: warning state or no unnecessary change
• possible functional parts: q, s

In such cases SafeShare can recognize the link as a Preview link, show a warning state, and leave the link unchanged or only treat it very carefully.

What these examples show

The practical examples show the actual strength of SafeShare Pro: The app does not treat every link the same, but decides based on link type, component, and edge case. An intermediate link can be unwrapped first, a shop link is evaluated differently from a video link, and an unclear extra parameter is not treated the same way as classic tracking.

9) Support report

The support report is the compact, copyable text version of an analysis. It is not needed for normal daily use, but for cases where you want to document a result, compare it, or pass it on to support.

What the support report is useful for

• when you want to trace a cleaning result or check it again later
• when you want to document what SafeShare did with an unusual link
• when you want to send a problem or question to support
• when you processed multiple links in one run and want the most important decisions collected in one place

What the support report contains

The report does not contain a nice table view like the result card, but a compact text version. It typically includes:

• the version of the Pro app used
• the recognized runtime environment, for example Apple mobile device, Android, or desktop
• the selected cleaning mode
• whether Keep coupon was active or not
• whether Remove ambiguous codes was active or not
• for each link the recognized type, for example Video link, Preview link, or Intermediate link with extracted target
• the original link
• the cleaned result
• which parts were removed
• which functional parts were kept
• which extra parameters were removed or kept by toggle
• technical context such as Risk Mode, Clean Strategy, and Link Kind

When you should open it

For normal use, the result card is usually enough. You mainly need the support report when something is unclear, unexpected, or needs explanation.

• when a link was cleaned differently than you expected
• when you want to check an unusual redirect, ad, or intermediate link
• when you send a support request
• when you want to trace a concrete analysis again later

How to use it

1. clean links as usual
2. open the Support report section
3. check the summary
4. if needed, click Copy report

What you should send to support

If you need help, a short description plus the copied support report is usually enough. If needed, you can also include the affected link or a safe example link.

What the support report is not

• not its own cleaning mode
• not an additional cleaner
• not a second result card
• not a replacement for looking at the actual analysis

10) Limits of SafeShare Pro

SafeShare Pro can make links cleaner, shorter, and more understandable. But the app is not magic. It changes the link, not the world behind the link. That is exactly why it is important to understand what SafeShare can do — and what it cannot.

SafeShare does not make you anonymous

A cleaned link is not automatically an anonymous link. SafeShare removes parameters and intermediate-link ballast, but the target page itself can still track, set cookies, use fingerprinting, or use other methods.

Not every parameter in the world is known or unambiguous

Many tracking, redirect, partner, and functional parameters are known, but not all systems use the same names. Some platforms use their own, changing, or ambiguous names. A field can clearly be tracking on one website, but functionally important on another.

• not every unknown parameter is automatically tracking
• not every known parameter should be judged the same way in every context
• there is realistically no eternal complete list of all cases

Redirects cannot always be unpacked perfectly

SafeShare can recognize many typical intermediate links and extract the target link from them. But that only works if the target link is visible and technically accessible inside the link.

• if a redirect target clearly sits in q, u, or similar fields, the chances are good
• if a platform uses more complicated, nested, or unusual mechanisms, SafeShare cannot always extract the target link completely
• not every intermediate link is fully readable from the outside
• with shortlinks whose target is not locally visible, SafeShare deliberately does not change the link blindly

More reduction can cost function

The shortest possible link is not automatically the best link. Some parts are relevant for view, language, product variant, playlist, start time, coupon, or other functions. Removing them can make the link cleaner, but also less functional.

SafeShare decides sensibly, but not infallibly

SafeShare tries to decide in a traceable and careful way. Even so, there are edge cases where a parameter can be removed unexpectedly or kept unexpectedly.

• a parameter can have a different role depending on the website
• a field can look neutral at first glance, but still carry a special function
• a link can contain multiple layers or special logics

Unknown parameter? Please let us know.

SafeShare knows many typical tracking, redirect, partner, and functional parameters — but not automatically every special case of every website. If you notice an unusual, unclear, or apparently important parameter that SafeShare does not yet recognize or treat sensibly, feedback is very helpful.

Feedback is not a “complaint about the tool”, but a valuable hint about a real special case. With link hygiene, the world changes constantly, and good feedback helps more than pretending to have a perfect endless list from the start.

SafeShare expands step by step

The cases that are already well recognizable today — for example Google, Facebook/Meta, Instagram, LinkedIn, Reddit, X/Twitter, TikTok, Amazon, and YouTube links — are an important beginning, but not the whole world of link hygiene. On top of that there are file, image, media, and preview edge cases, signed or technically sensitive attachments, new redirect patterns, new tracking extras, and website-specific quirks.

SafeShare does not replace your own judgment

The Pro app helps you understand and clean links. But it does not make every decision for you. Especially with attribution, coupons, redirects, or unusual parameters, your own look at the result still makes sense.

What SafeShare does very well

These limits do not mean SafeShare is weak — quite the opposite. SafeShare is strong at transparently and locally cleaning typical tracking and redirect cases without becoming unnecessarily aggressive.

• remove clear campaign parameters
• remove typical click IDs
• resolve Google and social intermediate links more understandably
• reduce visible tracking ballast even in ad or intermediate links without automatically promising a direct target link
• handle partner, coupon, and function logic deliberately
• treat file, image, media, and preview links more carefully
• make the decision visible for each link

11) Troubleshooting

If something looks unusual or does not work as expected, that is usually not a total failure, but a concrete individual case: an unusual link, the wrong mode, a deliberately removed coupon, a clipboard restriction in the browser, or a redirect that is structured differently than usual.

A link was cleaned differently than expected

First check the result card. There you can see:

• which link type was recognized
• where the original link comes from
• which parts were extracted, removed, or kept
• why SafeShare made that decision

tag or ref suddenly disappeared

That is almost always due to the chosen mode.

• Clean link + partner = tag and ref stay
• Clean link = tag and ref are removed

coupon is gone even though it should stay

Then the Keep coupon toggle is very likely not active.

• toggle off = coupon is removed
• toggle on = coupon stays

An unclear extra parameter suddenly disappeared or stayed

Then it is usually because of the Remove ambiguous codes toggle.

• toggle off = unclear extra parameters are more likely to stay
• toggle on = unclear extra parameters are additionally removed

The link is cleaner, but a function is missing

Then a part was probably removed that was in fact functionally relevant, or the link was more context-dependent than it first looked.

Typical examples:

• a start time or playlist on YouTube
• a variant, language, or product identifier in a shop link
• a coupon that was not deliberately kept
• a deliberately wanted partner or reference marker
• technical parts in file, image, or media links

A redirect was not resolved as expected

SafeShare can unwrap many typical intermediate links, but not every redirect is built the same way. If a target link was not extracted, there can be several reasons:

• the actual target link is not clearly stored in a known field such as q or u
• the redirect uses unusual or nested structures
• the target is not directly present as a readable URL inside the link

Device, browser, and runtime environment

SafeShare Pro technically recognizes the current runtime environment, for example whether the app is running on an Apple mobile device, an Android device, or more of a desktop environment.

This information mainly helps classify behavior around copying, pasting, and support cases. The actual link cleaning follows the same core logic, but clipboard behavior, browser permissions, or mobile interfaces can differ depending on the environment.

Copying does not work

Some browsers or environments block direct clipboard writing. In that case the function is not broken, but the environment currently does not allow copying.

• first try Copy
• if that does not work: use Select and copy the text manually

The page behaves strangely or shows old states

Then it is often not the link logic, but an old state in the browser.

• reload the page
• open the tab again
• if behavior stays stubborn, open the page completely fresh

When the support report is useful

If a case remains unclear, the support report is the fastest way to capture or pass on a concrete analysis.

• with unusual shop, intermediate, social, file, or preview links
• when a parameter was unexpectedly removed or kept
• when an unclear edge case was removed or preserved by toggle
• when you want to send a support request

If you are unsure

If a link matters and you are not sure whether the result is exactly right, the simplest rule still applies: check briefly instead of trusting blindly or rejecting blindly.

12) FAQ