Changelog & test stand

Traceable, reproducible, checkable: what was changed, why, and with which fixed examples it was checked.

Entries Test stand View rules Open app
Core principle: changes are only considered cleanly finished when they have been checked reproducibly with fixed test cases.

Changelog entries

2026-03-29 — product logic wording unified

  • Area: App, Help, Shortcuts, Bookmarklets
  • Change: public wording changed to Clean link and Clean link + partner
  • Reason: clearer, more consistent language across all main products
  • Expected effect: less confusion between product pages, help, and app logic
  • Note: public explanations were aligned to the visible product logic

2026-03-29 — coupon logic simplified in the free app

  • Area: App
  • Change: no separate coupon option anymore in the free app
  • Reason: clearer two-way logic without an extra switch
  • Expected effect: Clean link removes tracking, partner, and coupon. Clean link + partner keeps partner and coupon.
  • Note: this logic is now also linguistically consistent with Shortcuts and Bookmarklets.

Test stand

Status: documented · Area: link cleaning · Reference cases for understandable checks.

  • Fixed reference cases show how link cleaning behaves in typical situations.
  • Each case documents: input, expected result, and visible differences depending on the logic.
  • Goal: make changes to rules or product logic quickly understandable and checkable.

This page is not an internal developer ticket, but an understandable check document for visible product changes.

Test cases

Protocol format per case: Case, Input, Clean link, Clean link + partner, Note.

Case 1 — classic tracking link 
Input:
https://example.com/article?utm_source=newsletter&utm_medium=email&fbclid=123&x=1

Clean link:
https://example.com/article?x=1

Clean link + partner:
https://example.com/article?x=1

Note:
Both variants produce the same result here because there is no partner or coupon value present.
Case 2 — partner link without coupon 
Input:
https://shop.example.com/product?tag=partner-21&ref=creator123&utm_source=mail

Clean link:
https://shop.example.com/product

Clean link + partner:
https://shop.example.com/product?tag=partner-21&ref=creator123

Note:
Visible difference because partner values are either removed or deliberately kept depending on the logic.
Case 3 — partner link with coupon 
Input:
https://shop.example.com/product?tag=partner-21&coupon=SAVE10&utm_source=mail

Clean link:
https://shop.example.com/product

Clean link + partner:
https://shop.example.com/product?tag=partner-21&coupon=SAVE10

Note:
With the current public product logic, coupon stays together with partner.
Case 4 — functionally necessary parameter 
Input:
https://example.org/search?q=privacy&utm_campaign=spring

Clean link:
https://example.org/search?q=privacy

Clean link + partner:
https://example.org/search?q=privacy

Note:
The search value stays because it is functionally necessary. Tracking is removed.
Case 5 — video link with function-relevant values 
Input:
https://www.youtube.com/watch?v=dQw4w9WgXcQ&t=43s&list=PL123&utm_source=x

Clean link:
https://www.youtube.com/watch?v=dQw4w9WgXcQ&t=43s&list=PL123

Clean link + partner:
https://www.youtube.com/watch?v=dQw4w9WgXcQ&t=43s&list=PL123

Note:
Video ID, start time, and playlist stay because they are needed for the link to open meaningfully.

Release check

  • ✅ results checked with fixed test cases
  • ✅ visible differences documented in a way that can be followed
  • ✅ expected and actual results match
  • ✅ public wording consistent with app, shortcuts, and bookmarklets
  • ✅ limits and scope communicated clearly
  • ✅ no invisibility promise

Scope

  • Yes: SafeShare cleans URL tracking parameters.
  • No: No protection against IP logs, fingerprinting, or tracking after login.
  • Important: There is no such thing as being invisible on the internet. SafeShare is one concrete hygiene step before sharing.

FAQ

What does this changelog document?

Documented changes, test stands, and understandable test cases for link cleaning in SafeShare.

Why are test cases important here?

Because changes to link cleaning only make sense if they have been checked with fixed examples in a way that can be understood.

Why is this page important?

Because it makes visible changes to product logic and help understandable — not only as a claim, but with fixed examples.