Handbook

SafeShare Pro is for people who do not want to shorten links blindly, but want to clean them deliberately and transparently.

This handbook explains the current Pro App in depth: decision logic, cleaner grades, coupon toggle, link types, parameter types, the result card, practical examples, support report, limitations, and typical edge cases.

local · no upload transparency instead of a black box batch · result cards · support report
What is new in this handbook?
  • current app logic: focus on Clean with partner, Clean without partner, and Keep coupon
  • less theory, more practice: real link types, real parameter types, real examples
  • clear result explanation: original link, cleaned link, source, components, and summary
  • honest limitations section: including unknown parameters and planned expansion

Handbook version: 2026-03-15

Contents

1) What SafeShare Pro is

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

In short: SafeShare Pro removes unnecessary tracking data from links, tries to preserve functional parts, and makes the decision visible for each link.

What SafeShare Pro actually does

  • removes typical tracking and campaign parameters such as utm_*, fbclid, or gclid
  • recognizes redirects and intermediate links and first tries to extract the actual target URL
  • distinguishes between clearly removable ballast, functional parameters, and deliberately wanted attribution
  • shows for each link what was recognized, removed, or kept
  • creates a copyable support report when needed

What SafeShare Pro is not

  • not an anonymization tool
  • not a promise that the destination site itself will not keep tracking
  • not a blind “remove everything” tool
  • not a magic filter that automatically knows every edge case in the world perfectly

Why Pro is more than just a URL cleaner

SafeShare Pro does not just 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 URL, context, tracking, partner marker, or function, and why something is removed or deliberately kept.

Rule of thumb: SafeShare Pro should not make links “mysteriously disappear”, but clean them up in a way you can follow.

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 function
  • when you want to make deliberate decisions with affiliate, shop, social, or redirect links
  • when you want to document exactly what the app did in a support case

2) Quick start

This is how you use SafeShare Pro in everyday use: paste a link, choose the kind of cleaning you want, review the result, and copy or document it if needed.

The short version: Paste link → choose cleaner grade → enable coupon toggle if needed → clean → review result.

Step 1: Paste one link or multiple links

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

Important: SafeShare processes the list line by line. One invalid line does not block the remaining links.

Step 2: Choose a cleaner grade

SafeShare Pro currently works with two clear variants:

  • Clean with partner = typical tracking and measurement extras are removed, while tag and ref stay
  • Clean without partner = typical tracking and measurement extras are removed, and tag and ref are removed as well
Rule of thumb: The difference between these two cleaner grades is mainly whether partner and reference markers should deliberately stay.

Step 3: Enable the coupon toggle if needed

The Keep coupon toggle only controls coupon:

  • off = coupon is removed
  • on = coupon stays
Important: The coupon toggle works independently of partner mode. So you can remove partner markers and still keep a coupon.

Step 4: Clean

Click Clean. SafeShare then analyzes each link individually:

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

Step 5: Review the result

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

  • what was originally pasted
  • what the cleaned link looks like
  • where the original link comes from
  • which components 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 document or share the case, you can also open and copy the support report.

Always check briefly: SafeShare removes clear ballast very reliably, but not every parameter is universally unambiguous. Especially with shop, affiliate, or special links, it is worth taking a quick look at the result card.

3) How SafeShare decides

SafeShare Pro does not follow the simple principle of “remove everything”. The app tries to clean links in a way you can follow: remove clear ballast, preserve functional parts where possible, and resolve intermediate links before cleaning the actual target URL.

The basic rule: For each component, SafeShare decides whether it is clearly removable, functionally important, deliberately wanted, or just context from an intermediate link.

How a link is roughly structured

Before SafeShare decides anything, it first breaks the link into its rough parts. This helps explain what is base, parameter, or fragment.

Example: 
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 = a single parameter
  • & separates individual parameters
  • x=1 = another single parameter
  • #start = a fragment within the destination page
Rule of thumb: ? starts parameters, & separates them, and # marks a fragment.

3.1 What SafeShare removes with confidence

These things are typically not needed to open the destination page normally. They often only serve campaign measurement, 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 destination page
  • redirect context such as technical helper fields in intermediate links
Rule of thumb: If a component only measures, marks, or describes the outer redirect shell, it is usually removable.

3.2 What SafeShare can deliberately keep

Not every parameter is ballast. Some parts belong to the function of the link or are deliberately wanted. That is why these things are 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, if the matching cleaner grade is active
  • coupon, if the Keep coupon toggle is active
  • fragments such as #start, if they belong to the function of the link
Important: SafeShare does not try to make every link as empty as possible, but as sensible as possible.

3.3 What SafeShare unpacks first

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

Typical cases are:

  • Google intermediate links with a target in q=...
  • Facebook/Meta intermediate links with a target in u=...
  • other redirects with fields such as url, target, redirect, or similar
The principle: First extract the actual target URL, then clean that target URL itself.

3.4 What SafeShare treats depending on context

Not everything is clear-cut. Some parts can be judged differently depending on the platform, link type, or use case. That is why SafeShare deliberately treats some things based on context.

  • tag can be partner attribution
  • ref can carry reference, attribution, or source information
  • coupon can be a deliberately wanted discount code
  • id or source can be functional or just context
  • an outer redirect can contain tracking while still carrying an important target URL
This is why it matters: Not every unknown or ambiguous parameter is automatically tracking. SafeShare tries to decide carefully and transparently instead of deleting blindly.

What this means in practice

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

Short version: SafeShare thinks in three steps: recognize target URL → classify components → clean in a transparent way.

4) Cleaner grades and coupon toggle

SafeShare Pro currently works with two clear cleaning modes and one additional coupon toggle. The most important difference is not the handling of classic tracking parameters — those are removed in both variants — but whether partner and reference markers should remain.

The basic idea: Both cleaner grades remove unnecessary tracking ballast. The actual difference is whether tag and ref are deliberately kept or not.

4.1 Clean with partner

This cleaner grade 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 similar
  • coupon only remains if the coupon toggle is active
When this makes sense: When you want to share a clean link, but partner attribution or reference markers should deliberately remain.

4.2 Clean without partner

This cleaner grade is meant for cases where a link should be cleaned not only of tracking ballast, but also of partner and reference markers.

  • removed: tag, ref
  • also removed: typical tracking and campaign parameters such as utm_*, fbclid, gclid, and similar
  • coupon only remains if the coupon toggle is active
When this makes sense: When you want to share a link as neutrally as possible and no partner or reference attribution should remain.

4.3 Keep coupon, when active

The coupon toggle only applies to coupon. It does not control tag or ref, only whether a discount or offer code remains in the link.

  • toggle off = coupon is removed
  • toggle on = coupon remains
Important: The coupon toggle works independently of partner mode. So you can remove partner markers while still keeping a coupon.

4.4 The four most important combinations at a glance

1) Clean with partner + coupon off

  • tag remains
  • ref remains
  • coupon is removed
  • tracking such as utm_* is removed

2) Clean with partner + coupon on

  • tag remains
  • ref remains
  • coupon remains
  • tracking such as utm_* is removed

3) Clean without partner + coupon off

  • tag is removed
  • ref is removed
  • coupon is removed
  • tracking such as utm_* is removed

4) Clean without partner + coupon on

  • tag is removed
  • ref is removed
  • coupon remains
  • tracking such as utm_* is removed

What stays the same in both cleaner grades

In both variants, SafeShare removes clear tracking ballast 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.

Short version: tag and ref depend on the cleaner grade. coupon depends on the coupon toggle. Classic tracking is removed in both cases.

5) Recognizing link types

SafeShare Pro does not just 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.

The basic idea: First recognize the link type, then classify the individual parts accordingly.

5.1 General web link

A general web link is a normal direct link that points straight to the destination page and does not contain any recognizable outer intermediate shell.

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

In this case, SafeShare works directly on the visible link: tracking is removed, while functional parts such as x=1 can remain.

5.2 Google / search redirect

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

Example: 
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 shell https://www.google.com/url, extracts the target URL from q=..., and only then cleans the actual destination URL. Extras such as sa, source, or ust belong only to the redirect context and not to the destination page itself.

Rule of thumb: With Google redirects, the real target URL is extracted first, then that target URL is cleaned.

5.3 Facebook / social redirect

Social platforms often use intermediate links as well. With Facebook or Meta, the actual target URL is typically inside u=..., while other fields only carry platform context or redirect extras.

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

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

Rule of thumb: The visible Facebook link is often only the shell. The target URL inside it is what matters.

5.4 Amazon / shop link

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

Example: 
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 possible product, partner, and offer logic. Clear tracking extras are removed, while tag, ref, and coupon are kept or removed depending on the chosen settings.

Important: Amazon is not a typical intermediate-link case, but a case of product logic, attribution, and coupon decisions.

5.5 YouTube / video link

YouTube links are also direct destination links, but with video-specific components. Here it is less about resolving redirects and more about removing unnecessary share context without breaking the actual function of the video link.

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

Here SafeShare recognizes typical video components:

  • v = video ID
  • list = playlist
  • t = start time
  • si = share context
  • #start = fragment

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

Rule of thumb: With video links, function stays and unnecessary share junk goes out.

Why link type recognition matters

Link type recognition does not just assign a label. It affects how individual components are read and explained. A field like q can be the actual target URL in a Google intermediate link, while in a normal web link it might only be a general parameter. A field like h can be platform context on Facebook, but something completely different elsewhere.

That is why this rule matters: SafeShare does not decide only by parameter name, but always also by the recognized link type and the overall context.

6) Parameter types in detail

SafeShare Pro decides not only by link type, but also by the type of each individual component. Two parameters may look similar but play completely different roles. That is exactly why parameters should not be treated as a flat list, but according to function, context, and meaning.

The basic idea: A parameter name alone is not always enough. What matters is whether a component is tracking, a target URL, platform context, a partner marker, a coupon, a function, or a fragment.

6.1 Campaign and measurement parameters

These parameters typically serve campaign analytics, source attribution, or marketing measurement. They are usually not needed for the actual destination page and are therefore removed.

  • utm_source
  • utm_medium
  • utm_campaign
  • utm_term
  • utm_content
  • and in general everything with utm_*
Example: 
https://example.com/page?utm_source=newsletter&utm_medium=email&x=1
Expected: utm_source and utm_medium are removed, while x=1 is more likely to remain.

6.2 Click IDs

Click IDs are attribution markers used by platforms or ad systems. They often indicate which click, ad, or source led to a visit. They are usually not needed for the destination page itself.

  • fbclid
  • gclid
  • msclkid
  • dclid
  • twclid
  • ttclid
Rule of thumb: Click IDs measure origin and attribution, not the actual content of the link.

6.3 Target-URL parameters

These parameters do not just contain extra information, but often the actual target URL itself. In such cases they are not treated as ordinary parameters, but extracted first.

  • q
  • u
  • url
  • target
  • redirect
  • destination
Example: 
https://www.google.com/url?q=https%3A%2F%2Fexample.org%2Fpage%3Futm_source%3Dgoogle%26x%3D1&sa=D
Here, q is not just a normal parameter, but the actual target URL.

6.4 Platform and redirect context

These components often do not belong to the destination page itself, but to the outer shell, meaning the intermediate link, the platform, or the redirect system. That is why they are usually removed.

  • sa
  • source
  • ust
  • usg
  • ved
  • h in a social/Facebook context
Example: 
https://l.facebook.com/l.php?u=https%3A%2F%2Fexample.net%2Fpage%3Fx%3D1&h=AT0
u is the target URL here, while h is platform context and is removed.

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 that attribution to remain or not.

  • tag
  • ref
Important: tag and ref depend on the cleaner grade: Clean with partner keeps them, while Clean without partner removes them.

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.

The rule: coupon only stays if the Keep coupon toggle is active.

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 are often kept.

  • v = video ID
  • list = playlist
  • t or start = start point
  • lang = language
  • variant = variant
  • sku = product ID
  • id = identifier, if it is functionally relevant
Rule of thumb: Functional parameters often determine what you see or how the link opens.

6.8 Fragments

A fragment begins with # and is no longer part of the actual parameter section of the link. It points to a specific section within the destination page.

Example: 
https://www.youtube.com/watch?v=abc12345678&t=45s#start
#start is a fragment here and may be functionally relevant.

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

Why this distinction matters

If every component were treated the same way, many links would become shorter, but also more broken. That is exactly why SafeShare separates tracking, click attribution, target URL, platform context, partner markers, coupon, function, and fragments.

That is why this rule matters: A short link is not automatically a better link. A sensibly cleaned link is better.

7) Understanding the result card

After cleaning, SafeShare Pro not only shows a combined output, but also an individual result card for each link. This card is there to make the cleaning understandable: what went in, what came out, where the link came from, which parts were recognized, and why something was removed or kept.

The basic idea: The result card is not a technical gimmick. It is the explanation of the decision for each link.

7.1 Original link

The original link shows exactly the link you pasted. It is the starting point of the analysis. This lets you check what actually went into the app.

Why this matters: If a link is very long, nested, or built around an intermediate link, the original link helps keep the starting state clearly in view.

7.2 Cleaned link

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

Important: The cleaned link is not just “shorter”, but the result of a decision: tracking out, functional parts preserved where possible.

7.3 Where the original link comes from

This area shows the first outer part of the original link, meaning the link shell the visible link came from. This matters especially with redirects and intermediate links.

Examples:
  • https://www.google.com/url = Google intermediate link
  • https://l.facebook.com/l.php = Facebook/Meta intermediate link
  • https://amazon.de/dp/B0ABCDE123 = direct shop link
  • https://www.youtube.com/watch = direct video link

This helps you tell the difference: is the original link already the actual destination page — or just an outer shell?

7.4 How SafeShare reads the link

This section explains the rough structure of a link. SafeShare first breaks the link into base, parameters, and fragment.

The three most important characters:
  • ? starts the parameter section
  • & separates individual parameters
  • # starts a fragment within the destination page
Example:
https://example.com/page?utm_source=newsletter&x=1#start
Base: https://example.com/page
Parameters: utm_source=newsletter and x=1
Fragment: #start

7.5 Link components

The most important part of the result card is the table with the individual link components. That is where SafeShare breaks the link into understandable units.

The four columns mean:
  • Part = the concrete component of the link, for example utm_source=newsletter or v=abc12345678
  • Meaning = how SafeShare classifies that component, for example campaign parameter, video ID, or platform context
  • Action = what SafeShare does with it: extracted, removed, or kept
  • Reason = why SafeShare made exactly that decision

This lets you see not only that something was removed, but also why SafeShare understood it as a target URL, 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:

  • Part = the concrete link component, meaning what is actually in the link
  • Meaning = how SafeShare understands and classifies that component
  • Action = what SafeShare does with it
  • Reason = why SafeShare decided that way

That way you can see not only what was removed or kept in the end, but also how SafeShare understood the component itself.

The three most important actions:
  • extracted = the component contains the actual target URL and is extracted first
  • removed = the component does not belong to the actual destination page or is unnecessary ballast
  • kept = the component is functionally important or deliberately wanted
Practical rule: Do not read the table only as a list of parameters, but as a small decision chain: What is this? What does SafeShare do with it? Why?

7.6 Summary

At the end of the result card there is a short summary. It is the most compact reading level of the card and shows only:

  • Removed = which components were taken out
  • Kept = which components deliberately or functionally remained
Example:
Removed: utm_source, coupon
Kept: tag, ref

This summary does not replace the table. It 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 in more detail, the table above is the key.

How to read the card most effectively

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 the quick view
Important: The result card is not a purely technical output. It exists precisely to reduce uncertainty and make the decision behind the cleaned link understandable.

8) Practical examples

The following examples show how SafeShare Pro handles typical link types. The goal is not just a shorter link, but a cleanly understandable result: tracking removed, function preserved where possible, intermediate links unpacked first.

Note: These examples are intentionally simple. Real links may contain additional parameters that SafeShare classifies depending on link type and context.

8.1 Normal UTM link

A normal web link with classic campaign parameters.

Original link
https://example.com/page?utm_source=newsletter&utm_medium=email&utm_campaign=launch&x=1
Cleaned result
https://example.com/page?x=1
  • recognized type: General web link
  • removed: utm_source, utm_medium, utm_campaign
  • kept: x=1

The utm_* parameters are typical campaign and measurement values. x=1 is treated as more functional or neutral and therefore remains.

8.2 Google intermediate link

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

Original link
https://www.google.com/url?q=https%3A%2F%2Fexample.org%2Fpage%3Futm_source%3Dgoogle%26x%3D1&sa=D&source=hangouts&ust=158
Cleaned result
https://example.org/page?x=1
  • recognized type: Google / Search / Redirect
  • extracted: target URL from q=...
  • removed: sa, source, ust, and inside the target URL utm_source
  • kept: x=1

SafeShare does not simply remove parameters from the outer Google link here. It first extracts the target URL. Only then does it clean the actual destination link itself.

8.3 Facebook redirect

Here too, the visible link is initially only a platform shell. The actual target URL is inside u=....

Original link
https://l.facebook.com/l.php?u=https%3A%2F%2Fexample.net%2Fpage%3Ffbclid%3DXYZ%26x%3D1&h=AT0
Cleaned result
https://example.net/page?x=1
  • recognized type: Facebook / Meta / Social
  • extracted: target URL from u=...
  • removed: h=AT0 as platform context and fbclid=XYZ inside the target URL
  • kept: x=1

The outer Facebook link is recognized here as a platform shell. That is why SafeShare distinguishes between target URL, 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 possible product, partner, and offer logic.

Original link
https://amazon.de/dp/B0ABCDE123?tag=partner-21&ref=abc&utm_source=whatever&coupon=SAVE10
Variants at a glance
  • Clean with partner + coupon off: tag and ref stay, utm_source and coupon are removed
  • Clean with partner + coupon on: tag, ref, and coupon stay, utm_source is removed
  • Clean without partner + coupon off: tag, ref, utm_source, and coupon are removed
  • Clean without partner + coupon on: tag, ref, and utm_source are removed, coupon stays
Example result: with partner + coupon off
https://amazon.de/dp/B0ABCDE123?tag=partner-21&ref=abc
Example result: without partner + coupon on
https://amazon.de/dp/B0ABCDE123?coupon=SAVE10

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

8.5 YouTube link with playlist and start time

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

Original link
https://www.youtube.com/watch?v=abc12345678&list=PL123&t=45s&si=XYZ#start
Cleaned result
https://www.youtube.com/watch?v=abc12345678&list=PL123&t=45s#start
  • recognized type: YouTube / Video
  • kept: v as video ID, list as playlist, t as start time, #start as fragment
  • removed: si=XYZ as share context

Here SafeShare does not try to shorten the video link as much as possible, but to preserve the function of the link: the correct video, playlist, start time, and fragment remain, while unnecessary share context goes out.

What these examples show

The practical examples show the real strength of SafeShare Pro: The app does not treat every link the same way, but decides according to link type and component. A redirect is unpacked first, a shop link is judged differently from a video link, and a coupon is not treated the same way as a campaign parameter.

Important: These examples show typical cases. Real links can contain additional or unusual fields. That is exactly why the Pro App includes the result card and the support report.

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 later, or send it to support.

In short: The support report summarizes the most important information from a run in text form: input, result, recognized type, removed components, and kept components.

What the support report is useful for

  • when you want to document a cleaning result or review it later
  • when you want to record 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 key decisions collected in one place

What the support report contains

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

  • the version of the Pro App that was used
  • the selected cleaner grade
  • whether Keep coupon was active or not
  • for each link, the recognized type
  • the original link
  • the cleaned result
  • which components were removed
  • which components were kept
Important: The support report does not replace the result card. It is the concise text version for documentation and support.

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 or special case
  • when you want to send a support request
  • when you want to review a specific analysis later

How to use it

  1. clean links as usual
  2. open the Support report section
  3. review the summary
  4. click Copy report if needed
Practical rule: Look at the result card first. Only if you want to document, compare, or share the case, open the support report as well.

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.

Note: Before sending anything, check whether the link or report contains information you do not want to share. SafeShare works locally, but anything you send by email is something you choose to share.

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
Rule of thumb: The result card is for understanding. The support report is for copying and sharing.

10) Limitations of SafeShare Pro

SafeShare Pro can make links cleaner, shorter, and easier to follow. But the app is not a magic tool. It changes the link, not the entire world behind the link. That is why it is important to understand what SafeShare can do — and what it cannot do.

In short: SafeShare Pro can remove link ballast, make redirects more understandable, and show decisions transparently. But it cannot fully resolve every kind of tracking, every site logic, or every special case.

SafeShare does not make you anonymous

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

Important: SafeShare reduces data ballast in the link. It does not replace browser protection, a content blocker, or a full privacy setup.

Not every parameter in the world is known or unambiguous

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

  • not every unknown parameter is automatically tracking
  • not every known parameter has the same meaning in every context
  • a complete endless list of all cases is not realistic
That is why SafeShare does not work blindly: The app combines link type, parameter type, and context instead of deleting everything as a flat rule.

Redirects cannot always be unpacked perfectly

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

  • if the target URL is clearly inside q, u, or similar fields, the chances are good
  • if a platform uses more unusual, nested, or uncommon mechanisms, SafeShare cannot always extract the target URL completely
  • not every intermediate link is fully readable from the outside

More reduction can cost function

The shortest possible link is not automatically the best link. Some components are relevant for display, language, product variant, playlist, start time, coupon, or other functions. If you remove them, the link may become cleaner, but also functionally poorer.

Typical examples:
  • list or t on YouTube
  • variant, sku, or lang in shops or content links
  • coupon in discount links
  • tag and ref in deliberate attribution cases
  • #start or other fragments

SafeShare decides sensibly, but not infallibly

SafeShare tries to decide carefully and transparently. Still, there are edge cases where a parameter may be removed unexpectedly or kept unexpectedly.

  • a parameter can play 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 logic
Practical rule: If a link matters, take a quick look at the result card — especially with shop, redirect, social, or special links.

Unknown parameters? Please let us know.

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

Why this matters: Exactly that kind of feedback helps make SafeShare more robust and more precise over time — especially with new platforms, unusual redirects, or website-specific quirks.

Feedback is not a “complaint about the tool”, but a valuable signal about a real edge case. Link hygiene changes constantly, and good feedback helps more than pretending from the start that there is some perfect endless list.

SafeShare is expanded step by step

The clearly supported cases today — for example Google, Facebook, Amazon, or YouTube links — are an important beginning, but not the whole world of link hygiene. New platforms, new redirect patterns, new tracking extras, and website-specific edge cases keep appearing.

What can be expanded step by step:
  • more supported link sources and redirect types
  • better recognition of unusual platform and tracking parameters
  • finer classification of partner, reference, and coupon logic
  • more local rules: deliberately keep, deliberately remove, domain-specific behavior
  • a stronger explanation layer: not just remove, but classify in understandable language
  • later extensions such as Attribution/Advanced, QR-related features, or more structured reports
Important: SafeShare does not claim to know every edge case perfectly today. The goal is not artificial completeness, but honest, understandable, and steadily improving link hygiene.

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 in cases involving attribution, coupons, redirects, or unusual parameters, your own quick review still matters.

That is exactly why there are:
  • the result card for understanding
  • the summary for quick checking
  • the support report for documenting and sharing

What SafeShare is very good at

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

  • remove clear campaign parameters
  • remove typical click IDs
  • resolve Google and Facebook intermediate links in an understandable way
  • handle partner, coupon, and functional logic deliberately
  • make the decision visible for each link
Rule of thumb: SafeShare Pro is strong at transparent link cleaning — not at magical promises.

11) Troubleshooting

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

The good news: In most cases, it is quick to see whether the issue comes from the link structure, a setting, or browser behavior.

A link was cleaned differently than expected

Check the result card first. There you can see:

  • which link type was recognized
  • where the original link comes from
  • which components were extracted, removed, or kept
  • why SafeShare made that decision
Practical rule: Do not look only at the final result. Also look at the table with meaning, action, and reason.

tag or ref suddenly disappeared

That is almost always caused by the selected cleaner grade.

  • Clean with partner = tag and ref stay
  • Clean without partner = tag and ref are removed
Check this first: If partner or reference markers disappeared, verify the cleaner grade first.

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
Important: The coupon toggle works independently of partner mode.

The link is cleaner, but a function is missing

Then a component was probably removed even though it turned out to be functionally relevant, or the link was more context-dependent than it first seemed.

Typical examples:

  • a start time or playlist on YouTube
  • a variant, language, or product ID in a shop link
  • a coupon that was not actively kept
  • a deliberately wanted partner or reference marker
Practical rule: If link function matters, check the result card briefly instead of looking only at the link length.

A redirect was not resolved as expected

SafeShare can unpack many typical intermediate links, but not every redirect is structured the same way. If a target URL was not extracted, that can have several reasons:

  • the actual target URL is not clearly inside a known field such as q or u
  • the redirect uses unusual or nested structures
  • the target is not directly available as a readable URL inside the link
Check this: Look at the result card to see whether a component was marked as extracted. If not, SafeShare could not clearly extract the target URL in this case.

Copying does not work

Some browsers or environments block direct writing to the clipboard. In that case, the function is not broken — the environment simply does not allow direct copying right now.

  • try Copy first
  • if that does not work: use Select and copy manually
Note: Especially on mobile devices or in special browser contexts, behavior can differ.

The page behaves oddly or shows old states

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

  • reload the page
  • open the tab again
  • if it persists, open the page fresh from scratch
Typical signs: A toggle behaves strangely, a page looks different from what you expected, or a change is visibly not there yet.

When the support report is useful

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

  • for unusual shop, redirect, or social links
  • when a parameter was unexpectedly removed or kept
  • when you want to send a support request
Most helpful for support: short problem description + affected link or safe example link + copied support report

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.

Rule of thumb: SafeShare is meant to reduce uncertainty — but for important links, a final quick check still makes sense.

12) FAQ

Does SafeShare simply remove everything after the question mark?
No. SafeShare does not blindly remove everything after ?. The app breaks the link into individual components and then decides for each part whether it is tracking, a target URL, platform context, a partner marker, a coupon, a function, or a fragment.
Why does tag sometimes remain?
tag is deliberately kept in the Clean with partner cleaner grade, because it can carry partner or affiliate attribution. In the Clean without partner cleaner grade, tag is removed.
Why does ref sometimes remain?
ref is not automatically just tracking. It can carry reference, source, or deliberate attribution. That is why ref stays with Clean with partner and is removed with Clean without partner.
Why is coupon sometimes gone?
Because coupon only remains if the Keep coupon toggle is active. If the toggle is off, coupon is removed — regardless of which cleaner grade is selected.
Why is a Google or Facebook link unpacked first?
Because in such cases the visible original link is often only an outer shell. The actual target URL is then inside a field such as q or u. That is why SafeShare first tries to extract the real target URL before cleaning it.
Why does #start or another fragment remain?
A fragment begins with # and can be functionally relevant because it points to a specific section of the destination page. That is why SafeShare does not treat it like an ordinary tracking parameter.
Why does YouTube keep not only the video ID, but also list or t?
Because list can define a playlist, and t or start can define a starting point. These parts often belong to the actual function of the video link and are therefore kept, while unnecessary share context such as si is removed.
Does SafeShare make me anonymous?
No. SafeShare cleans the link, but it does not make you anonymous. The destination site itself can still track, set cookies, or use other methods. SafeShare reduces link ballast, but it does not replace a full privacy setup.
Can SafeShare resolve every redirect perfectly?
No. Many typical redirects can be unpacked well, but not every intermediate link is fully readable from the outside. If the actual target URL is not clearly inside an accessible field, SafeShare cannot always extract it completely.
What should I do if a parameter is unclear or handled oddly?
Then it is worth looking at the result card first. If the case still remains unclear, or a parameter seems not yet to be recognized sensibly, feedback is helpful. Exactly this kind of feedback helps make SafeShare more robust and more precise.
Why do I need the support report if I already have the result card?
The result card is for understanding. The support report is the compact text version for copying, documenting, or sharing — for example with support.
What matters more: the shortest possible link or a sensible link?
A sensibly cleaned link matters more than a maximally short link. SafeShare does not try to empty links at any cost, but to remove tracking without unnecessarily breaking useful function.