Handbook

SafeShare Audit helps you avoid cleaning links blindly. It shows what is attached to a link before you share, send, or publish it.

This handbook explains the Audit app: paste a link, recognize the link type, understand its parts, review categories, make conscious decisions at the end, and document the result in a traceable way.

local · no upload Understand · Decide · Share Categories · Decisions · Audit report
What is new in this handbook?
  • product name: SafeShare Audit is the name of this bundle.
  • new red thread: first analyze and explain, then make decisions at the end
  • new language: categories such as campaign tracking, click IDs, partner, coupon, redirect context, and unclear parameters are now central
  • less mode-first thinking: do not start with checkboxes; first understand what is attached to the link
  • audit report: the report documents what was found, removed, and deliberately kept in a traceable way
  • honest limits: SafeShare Audit works on the link itself, does not make you anonymous, and does not replace a full tracker blocker

Handbook state: 2026-06-09

Contents

1) What SafeShare Audit is

SafeShare Audit is a local tool for reviewing outgoing links. It helps you see what is inside a link, what is likely ballast, what may be functional, and what should be decided consciously.

In short: SafeShare Audit shows what is attached to a link, explains its meaning, and documents what was removed or deliberately kept.

What SafeShare Audit actually does

  • reviews visible parts of a link directly in your browser
  • recognizes typical link types such as web link, shop link, social link, redirect wrapper, shortlink, file link, image link, or video link
  • groups link additions into understandable categories
  • explains whether something is more likely measurement, click attribution, partner context, coupon, function, or an unclear extra
  • shows the explanation first and lets you decide consciously afterward
  • creates a cleaned link and an audit report

What SafeShare Audit is not

  • not an anonymization tool
  • not a VPN
  • not a full tracker blocker
  • not a tool for adding tracking parameters
  • not a promise that the target page itself will not track
  • not a magical filter that knows every special case in the world perfectly

Why Audit is more than quick cleaning

A normal link cleaner often gives you only a shorter result. SafeShare Audit also explains what happened: Which parts were recognized? What did they mean? What was removed? What was deliberately kept? Why was SafeShare cautious?

Key idea: Free makes links clean quickly. Audit shows what is inside the link — and why.

When SafeShare Audit is especially useful

  • before you send a newsletter
  • before you publish links or include them in posts
  • when you want to know whether campaign, click, or partner additions are attached to a link
  • when you want to better understand shop, social, redirect, or short links
  • when you want to document a decision
  • when you do not want to manually click through every link and guess what is attached
Guiding line: If you know what is attached to a link, you know what you share.

2) Quick start

SafeShare Audit is designed as a guided review. You should not start by guessing from a list of checkboxes. First, you should see what the link contains.

Short version: Paste link → analyze → see what is attached → review meaning → set decisions → use result and audit report.

Step 1: Paste a link

Paste the link you want to review. The main case for SafeShare Audit is one link at a time, so the analysis stays clear and the decision can be made consciously.

Why one link? A single link can be explained more clearly: target, parameters, categories, meaning, and decision stay understandable.

Step 2: Analyze the link

SafeShare Audit reads the link and first recognizes its basic structure: where the link leads, whether it contains a redirect, and which visible parts are attached.

  • base address
  • parameters after the question mark
  • anchor after #
  • possible redirect or shortlink structure
  • possible shop, social, video, file, or image context

Step 3: Understand the meaning

The detected parts are not only shown technically. SafeShare Audit groups them into understandable categories: campaign tracking, click ID, partner, coupon, function, redirect context, or unclear parameters.

Step 4: Set decisions

Only after the parts have been explained do you decide what should be removed and what should deliberately remain.

Important: The checkboxes belong at the end of the review. Understand first, decide afterward.

Step 5: Use result and audit report

You then get the cleaned link and a traceable documentation. The audit report summarizes what was found, removed, and deliberately kept.

Always check briefly: For important links, it is worth looking at the result card, especially for shop, partner, redirect, file, image, or special links.

3) The audit flow

SafeShare Audit follows a different pattern from a quick cleaner. It is not only about “shorter”, but about “understood and consciously decided”.

The flow: Where does the link lead? → What is attached? → What is it for? → What can go? → What should stay? → What needs a conscious decision?

3.1 Where does the link lead?

First, the target structure is read. With a normal link, this is usually the visible address. With a redirect or intermediate link, the visible address may only be a wrapper.

Example:
https://www.google.com/url?q=https%3A%2F%2Fexample.org%2Fpage%3Futm_source%3Dgoogle

In this example, Google is not the actual target. The real target link is inside the parameter q.

3.2 What is attached to the link?

Then SafeShare Audit reviews the parts that appear after the question mark or inside redirect fields. These parts can play very different roles.

  • measurement and campaigns
  • click attribution
  • social or share context
  • partner or affiliate attribution
  • coupon or discount context
  • functional parameters
  • technical file or image parameters
  • unclear parameters

3.3 What is it for?

SafeShare Audit tries to explain whether a part is likely part of the function or more likely only measurement, origin, click attribution, or context.

Example:
  • utm_source = campaign or source marker
  • fbclid = click ID from Meta/Facebook context
  • tag = possible partner or affiliate marker
  • coupon = possible discount or coupon context
  • variant = possibly functional product context

3.4 What can go?

Typical campaign and click parameters are usually removable, because they are not needed for the target page to open normally.

  • utm_*
  • fbclid
  • gclid
  • msclkid
  • twclid
  • ttclid
  • pure redirect-wrapper context

3.5 What should stay?

Some parts may be functionally important. They can define a video, a playlist, a product variant, an image format, a language, or a section on the page.

  • v on YouTube as video ID
  • list as playlist
  • t or start as start time
  • variant or sku on shop links
  • w, format, or similar technical image parameters
  • anchors such as #start

3.6 What needs a conscious decision?

Partner, coupon, and unclear parameters are not always simply “good” or “bad”. That is why they should be made visible and consciously decided at the end.

Important: SafeShare Audit does not delete silently. It makes the decision visible.

4) Understanding categories

SafeShare Audit no longer starts with modes as the main idea. It starts with categories. A category describes the likely role of a link part.

The main idea: First show what was found. Then explain what it means. Only after that decide.

4.1 Campaign tracking

Campaign parameters often mark source, medium, or campaign. They help analytics tools attribute the click, but are usually not needed for the target page itself.

  • utm_source
  • utm_medium
  • utm_campaign
  • utm_content
  • utm_term
Typical recommendation: usually remove.

4.2 Click IDs

Click IDs often come from ad or social platforms. They mark a specific click or attribution path.

  • fbclid
  • gclid
  • msclkid
  • dclid
  • twclid
  • ttclid
Typical recommendation: usually remove.

4.3 Social and share context

Some parameters are created when links are shared through platforms or apps. They can describe where the link came from or how it was shared.

Examples: igshid, si, platform share extras, or redirect context.
Typical recommendation: usually remove if the actual function of the link is preserved.

4.4 Redirect-wrapper additions

Redirect links often contain an actual target link and additional fields from the platform wrapper. SafeShare first tries to extract the target link.

  • q as target link on Google
  • u as target link on Facebook/Meta
  • url, target, redirect, or destination as target fields
  • sa, source, ust, usg, or h as possible wrapper additions
Typical recommendation: extract the real target link, remove wrapper additions.

4.5 Partner / affiliate

Partner or affiliate additions can be deliberately wanted. They can carry a recommendation, commission, or attribution.

  • tag
  • ref
  • referral
  • affiliate
Typical recommendation: decide consciously. Do not remove silently and do not keep silently.

4.6 Coupon / discount code

A coupon can be a wanted discount. It can also be an extra that you do not want to pass on.

  • coupon
  • coupon_code
  • promo
  • discount
Typical recommendation: decide consciously. Coupon is separate from partner/affiliate.

4.7 Functional parameters

Functional parameters determine what is opened at the target: a variant, a language, a playlist, a start time, an image format, or a file view.

  • v, list, t, start
  • variant, sku, id
  • lang, locale
  • w, h, format, quality
Typical recommendation: usually keep if they may belong to the function of the link.

4.8 Unclear parameters

Unclear parameters are additions that cannot be clearly recognized as tracking, partner, coupon, or functionally necessary.

Example: ref_code may have a role depending on the website, but is not always clearly classifiable.
Important: “Unclear” does not mean “dangerous”. It means: not clearly classifiable.

4.9 Anchors

An anchor begins with # and often points to a specific section within a page.

Example:
https://example.com/page#pricing
Typical recommendation: usually keep if it belongs to the function of the link.

5) Recognizing link types

The link type helps SafeShare Audit read a part correctly. A parameter can mean something different in a Google redirect than in a shop link.

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

5.1 Normal web link

A normal web link points directly to a page and does not contain a recognizable outer redirect wrapper.

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

SafeShare Audit works directly on this link: campaign parameters are recognized, while functional or unclear parts are classified.

5.2 Newsletter or campaign link

Newsletter links often contain campaign parameters. They are useful for marketing analysis, but not always wanted when forwarding or publishing.

Example:
https://example.com/article?utm_source=newsletter&utm_medium=email&utm_campaign=june

5.3 Shop link

Shop links can contain product information, partner attribution, coupons, or technical variants. That is why they are read more carefully than pure campaign links.

Example:
https://amazon.de/dp/B0ABCDE123?tag=partner-21&utm_source=test&coupon=SAVE10&variant=black

5.4 Social or share link

Social links can contain share context, click IDs, or platform additions. Sometimes they are direct links, sometimes redirect wrappers.

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

5.5 Ad or redirect wrapper

A redirect wrapper does not point directly to the target. It contains the target in a parameter. SafeShare Audit tries to extract the real target link first.

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

5.6 Shortlink

A shortlink can hide the target. If the target is not locally visible inside the link, SafeShare Audit cannot reliably unpack it without opening the URL online.

Important: SafeShare Audit does not upload links and does not secretly fetch targets online. Shortlinks without a visible target are therefore handled cautiously.

5.7 Video link

Video links often contain functional parts such as video ID, playlist, or start time. These should not be removed blindly.

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

5.8 File, image, and media link

File, image, and media links often contain technical parameters for access, display, format, or quality. That is why they are treated more carefully than normal web links.

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

Why link type recognition matters

A field such as q can be the target link on Google, but only a search query on another site. A field such as h can be platform context on Facebook, but technical height on an image link.

That is why: SafeShare Audit does not decide only by parameter names, but always also by link type and context.

6) Link parts in detail

A link consists of several parts. SafeShare Audit breaks them down so it becomes clear what is being reviewed.

Example:
https://example.com/page?utm_source=newsletter&x=1#start
  • https://example.com/page = base of the link
  • ? starts the parameter section
  • utm_source=newsletter = one individual parameter
  • & separates parameters from each other
  • x=1 = another parameter
  • #start = anchor
Key idea: ? starts parameters, & separates them, # starts an anchor.

6.1 Target-link parts

In redirects, a parameter may contain the actual target link. Then that part is extracted first.

Example:
https://www.google.com/url?q=https%3A%2F%2Fexample.org%2Fpage%3Futm_source%3Dgoogle&sa=D
Here q is not just a normal parameter, but contains the actual target link.

6.2 Measurement and click parts

These parts typically serve measurement or click attribution. They are usually not needed for the content of the target page.

  • utm_*
  • fbclid
  • gclid
  • msclkid
  • twclid
  • ttclid

6.3 Partner parts

Partner parts can carry deliberate attribution. They should be made visible and decided consciously.

  • tag
  • ref
  • referral
  • affiliate

6.4 Coupon parts

Coupon parts can carry discount or offer context. They should be considered separately from partner/affiliate.

  • coupon
  • coupon_code
  • promo
  • discount

6.5 Functional parts

Functional parts can determine what opens or how it is displayed. That is why they are not removed blindly.

  • v = video ID
  • list = playlist
  • t or start = start point
  • variant = product variant
  • sku or id = product or content identifier
  • lang = language
  • w, h, format = technical image parameters

6.6 Unclear parameters

Unclear parameters sit in the gray area. They are not clearly tracking, but also not clearly necessary for functionality.

Important: Unclear parameters are exactly the cases where a conscious decision is useful.

7) Set decisions at the end

The most important product logic of SafeShare Audit is: the decision comes after the analysis.

Correct: Analyze link → understand parts → review categories → set checkboxes.
Not ideal: Set checkboxes first without knowing what is actually inside the link.

7.1 Remove campaign tracking

Campaign tracking is usually removable if you want to pass on the link without measurement context.

Typical parts: utm_source, utm_medium, utm_campaign, utm_content, utm_term

7.2 Remove click IDs

Click IDs are usually removable because they carry click or ad attribution.

Typical parts: fbclid, gclid, msclkid, dclid, twclid, ttclid

7.3 Deliberately remove or keep partner / affiliate

Partner or affiliate parts are a conscious decision. Sometimes you want to remove them, sometimes you want to keep them deliberately.

Key idea: Partner is not just a technical disturbance. It is attribution. Whether it should stay is your conscious decision.

7.4 Deliberately remove or keep coupon

Coupon is its own decision. A discount code may be wanted, but it may also be an extra that you do not want to pass on.

Important: Coupon is not mixed with partner/affiliate.

7.5 Remove or keep unclear parameters

Unclear parameters are not clearly classifiable. If you want to share more cleanly, you can remove them. If you do not want to risk function, you can keep them more cautiously.

Tradeoff: Removing more can look cleaner, but with unclear parameters it can also cost function.

7.6 Functional parameters are usually kept

Functional parameters often define the target more precisely. That is why they are not treated like normal tracking additions.

Example: A YouTube start time, a product variant, or an image size may belong to the intended function.

8) Understanding the result card

The result card is the central explanation area of SafeShare Audit. It shows not only what comes out, but how the decision was made.

The main idea: The result card answers: What was attached to the link? What was recognized? What was removed? What was deliberately kept?

8.1 Original link

The original link shows the link you pasted. With long or nested links, this is important so the starting point stays clear.

8.2 Recognized link type

The recognized link type shows the context in which SafeShare reads the link: web link, shop link, social link, redirect wrapper, video link, file link, image link, or another case.

8.3 Found parts

Here you see which parameters or link parts were found. What matters is not only the name, but the meaning.

The most important questions:
  • Which part is actually inside the link?
  • How does SafeShare classify this part?
  • What does SafeShare recommend doing with it?
  • Why?

8.4 Decision and result

After the analysis, SafeShare shows what was removed and what stays in the link. This lets you check whether the result matches your intention.

  • removed = removed from the result
  • deliberately kept = remains in the result
  • functionally kept = may be important for function
  • unclear kept or removed = edge case, deliberately handled

8.5 Cleaned link

The cleaned link is the result of the selected decisions. It is not just “shorter”, but a deliberately created version of the original link.

Practical rule: For important links, do not only copy. Briefly check whether partner, coupon, function, and target still match what you want.

9) Practical examples

The following examples show typical cases. Real links can contain additional parameters, which SafeShare classifies depending on context.

9.1 Normal UTM link

Original link
https://example.com/page?utm_source=newsletter&utm_medium=email&utm_campaign=launch&x=1
Possible result
https://example.com/page?x=1
  • recognized: campaign tracking
  • removed: utm_source, utm_medium, utm_campaign
  • consciously reviewed: x=1 as not a clear standard tracking case

9.2 Google redirect wrapper

Original link
https://www.google.com/url?q=https%3A%2F%2Fexample.org%2Fpage%3Futm_source%3Dgoogle%26x%3D1&sa=D&source=hangouts
Possible result
https://example.org/page?x=1
  • recognized: redirect wrapper
  • extracted: target link from q
  • removed: redirect-wrapper additions and utm_source

9.3 Facebook/Meta redirect

Original link
https://l.facebook.com/l.php?u=https%3A%2F%2Fexample.net%2Fpage%3Ffbclid%3DXYZ%26x%3D1&h=AT0
Possible result
https://example.net/page?x=1
  • recognized: social/redirect wrapper
  • extracted: target link from u
  • removed: fbclid and wrapper context

9.4 Shop link with partner and coupon

Original link
https://amazon.de/dp/B0ABCDE123?tag=partner-21&utm_source=test&coupon=SAVE10&variant=black
  • recognized: shop link
  • campaign tracking: utm_source can usually go
  • partner: consciously decide tag
  • coupon: consciously decide coupon
  • function: treat variant cautiously
Important: This example shows the Audit logic: not everything is removed blindly. Partner, coupon, and function are made visible separately.

9.5 YouTube link with start time

Original link
https://www.youtube.com/watch?v=abc12345678&list=PL123&t=45s&si=XYZ#start
Possible result
https://www.youtube.com/watch?v=abc12345678&list=PL123&t=45s#start
  • functionally kept: v, list, t, #start
  • removed: si as share context

9.6 Unclear parameter

Original link
https://example.com/?ref_code=ABC123&utm_source=test
  • clearly removed: utm_source
  • unclear: ref_code
  • decision: remove or keep depending on the level of caution you want

9.7 File or image link

Original link
https://example.com/images/photo.jpg?utm_source=mail&w=1200&format=webp
Possible result
https://example.com/images/photo.jpg?w=1200&format=webp
  • removed: utm_source
  • functionally kept: w, format
Key idea: A short link is not automatically better. A sensibly cleaned link is better.

10) Audit report

The audit report is the copyable documentation of a link review. It is meant to make a decision traceable later, compare it, or pass it on.

In short: The result card is for understanding. The audit report is for documentation.

What the audit report contains

  • version of the Audit app
  • recognized runtime environment
  • original link
  • cleaned result
  • recognized link type
  • found categories
  • removed parts
  • deliberately kept parts
  • cautious or unclear decisions
  • technical context where relevant to the analysis

What the audit report is useful for

  • to document a decision before publication
  • to understand later what happened with an unusual link
  • to share an analysis internally
  • to make a support request specific
Note: Before passing it on, check whether the link or report contains information you do not want to share.

11) Limits of SafeShare Audit

SafeShare Audit helps you understand and clean the link itself. It does not change the target page or the entire tracking behavior of the web.

In short: SafeShare Audit works on the link. Not on everything that happens on the target page after the click.

SafeShare Audit does not make you anonymous

A cleaned link is not automatically an anonymous link. The target page can still set cookies, store logs, use fingerprinting, or run its own analytics systems.

Important: SafeShare Audit does not replace browser protection, a content blocker, a VPN, or a complete privacy setup.

Not every parameter is clear

A parameter can play a different role depending on the website. That is why SafeShare Audit acts cautiously and explains edge cases instead of promising artificial certainty.

  • not every unknown parameter is tracking
  • not every short link is better
  • not every redirect can be unpacked locally
  • not every platform structure is fully readable from the outside

Shortlinks and invisible targets

If a shortlink does not contain the target visibly inside the link, SafeShare Audit cannot safely recognize the target locally without opening the link online.

That is why: SafeShare Audit does not secretly fetch links online. This protects the local workflow, but limits the unpacking of invisible shortlink targets.

Removing more can cost function

If you remove too aggressively, the link may look cleaner, but lose a wanted function.

  • start time or playlist in videos
  • product variant in shops
  • coupon or discount code
  • deliberate partner attribution
  • image format, size, or quality
  • anchor to a page section
Practical rule: For important links, briefly check the result instead of only aiming for maximum shortness.

SafeShare Audit improves step by step

Link structures change constantly. Platforms, shops, newsletter systems, social apps, and ad systems use their own patterns. That is why a clear, extensible category logic matters more than a supposedly perfect endless list.

What can be expanded further:
  • more link types and platform patterns
  • better detection of unusual redirects
  • finer partner, coupon, and function logic
  • more explanation texts for special cases
  • more structured audit reports
  • later team and review workflows

12) Troubleshooting

If a result looks different from what you expected, it is usually because of one specific point: link type, category, decision, or browser environment.

A link was cleaned differently than expected

First check the result card:

  • which link type was recognized
  • which parts were found
  • which category they were assigned to
  • what was removed or kept
  • whether a part was treated as an unclear parameter

Partner markers are missing or remain

Partner or affiliate additions are meant to be decided consciously. Check whether you wanted to remove or keep that category.

Typical parts: tag, ref, referral, affiliate

Coupon is gone or remains

Coupon is its own decision. Check whether you wanted to deliberately keep discount or offer context.

Typical parts: coupon, coupon_code, promo, discount

An unclear parameter was removed or kept

It was probably treated as an edge case. That is not a bug, but exactly the kind of case where a conscious decision is useful.

Check: If a field such as ref_code was handled differently than expected, check whether it was classified as an unclear parameter.

A redirect was not unpacked

SafeShare Audit can only unpack what is locally visible inside the link. If the target link is not clearly contained in a parameter, Audit cannot reliably extract it.

Copying does not work

Some browsers or embedded views block direct access to the clipboard. Then the link logic is not broken; the environment simply does not allow copying.

  • first try the copy button
  • if that does not work: select the result and copy it manually
  • on iPhone/iPad, open directly in Safari whenever possible
  • run the selftest and include the support report in your support request

The page shows old states

If old terms, old texts, or old behavior are visible, the reason may be browser cache or an old file inside the ZIP.

  • reload the page
  • open a new tab
  • use the fresh ZIP version
  • when using locally, make sure the correct file was opened

When the audit report helps

If a case remains unclear, open the audit report. It summarizes the analysis in a copyable form.

Most helpful for support: short problem description, affected link or safe example link, and copied audit report.

13) FAQ

Does SafeShare Audit simply remove everything after the question mark?
No. SafeShare Audit breaks the link into individual parts and classifies them: tracking, click ID, target link, redirect context, partner, coupon, function, unclear parameter, or anchor.
Why do the checkboxes come at the end?
Because you should first see what the link contains. Only after the explanation do you consciously decide what should be removed and what should remain.
What is the difference from the Free App?
The Free App is for quick cleaning. SafeShare Audit is for understanding, reviewing, and documenting.
What is an audit report?
The audit report is the copyable documentation of the link review: original, result, recognized link type, found categories, removed parts, and deliberately kept parts.
Why can a partner parameter be important?
Partner or affiliate parameters can carry deliberate attribution. They are not automatically good or bad. That is why they should be visible so you can decide consciously.
Why is coupon handled separately?
A coupon can be a discount or offer code. That is a different question from partner/affiliate. That is why coupon is shown separately.
What does “unclear parameters” mean?
These are extra parameters that cannot be clearly recognized as tracking, partner, coupon, or functionally necessary. Unclear does not mean dangerous. It means not clearly classifiable.
Why are video, file, or image links treated more carefully?
Because such links often contain functional or technical parameters. Cleaning too aggressively could break start time, playlist, image size, format, or access.
Can SafeShare Audit resolve every shortlink?
No. If the target of a shortlink is not visible inside the link, SafeShare Audit cannot recognize it locally without opening the link online. SafeShare Audit does not secretly upload or fetch links.
Does SafeShare Audit make me anonymous?
No. SafeShare Audit cleans the link, but does not make you anonymous. The target page itself can still use its own analytics or tracking methods.
What matters more: the shortest possible link or a sensible link?
A sensibly cleaned link matters more than a maximally short link. SafeShare Audit tries to remove unnecessary ballast without unnecessarily breaking useful function.
What should I do if a result looks strange?
First check the result card and the audit report. Pay attention to link type, category, removed parts, deliberately kept parts, and unclear parameters.