Cancellation route audit: 76 subscription services

TrialBell ships 76 built-in cancellation routes — the pages you land on when you tap "Open cancellation page" for a service. We check every one of them and publish the result, including the two we found broken on the first run and have since fixed. This page records three runs: the original audit of 42 routes in July 2026, the expansion to 76 in September 2026, and a re-check of all 76 in October 2026 that found one newly broken route.

Why this is worth measuring

The gap between "I want to cancel" and "I have cancelled" is where subscription businesses make their unearned money. Some of that gap is deliberate design. A lot of it is just that billing pages move, get renamed, or hide three levels down a help centre — and a stale link is as good as no link when the deadline is today.

Any app that promises one-tap cancellation is making a claim about URLs it doesn't control. The only honest way to make that claim is to check, publish the check, and do it again.

Method

Deliberately simple, so anyone can repeat it:

1. Extract every cancellationLink shipped in TrialBell 1.0's service catalog — the 42 URLs shipping at the time, across 129 service templates.
2. Issue one HTTP GET per URL, following redirects, with an iPhone Safari user-agent and a 25-second timeout, from a US-routed connection, unauthenticated.
3. Record the status code and the final URL after redirects — a 200 alone proves nothing about where you ended up.
4. Classify into four buckets (below).
5. For anything that blocked the automated request, open it by hand in a real browser and confirm the page that renders is the intended cancellation page. If it isn't, it counts as broken.

The four result categories

What the first run found

Two routes were dead, both the same URL used by two templates: https://github.com/settings/billing, serving GitHub and GitHub Copilot. GitHub retired that path; it now returns a hard 404 rather than redirecting, so anyone tapping "Open cancellation page" for either landed on an error — on the day they were trying to cancel.

Both are fixed. The working routes are:

Both now redirect an unauthenticated request to GitHub's own login with a return_to pointing at the exact settings page — which is what a healthy account URL should do. The app also carries a regression test pinning both URLs, so the retired path can't come back through a copy-paste.

This is exactly the failure the audit exists to catch, and it's the argument for why "we ship cancellation links" should always come with "and here's when we last checked them".

Sign-in walls and bot walls are not failures

A cancellation page that asks you to log in is behaving correctly — it's your account, and no one should be able to reach it without signing in. Likewise, several help centres returned a 403 to our script while serving the page normally to a browser; that's bot protection, not a dead link. We separate these from genuine breakage rather than lumping everything non-200 together, because doing otherwise would make the numbers look worse and mean less.

The four bot-protected routes — Canva, ChatGPT, Crunchyroll and HelloFresh — were each opened by hand and confirmed to render the correct cancellation article.

The Apple route is the reliable one

If you subscribed through an iPhone app, the provider's own website often can't cancel it at all — the billing relationship is with Apple. That route doesn't rot, because it's a fixed path in iOS Settings: Settings → your name → Subscriptions → tap the subscription → Cancel Subscription. Five steps, same on every iPhone, no URL to go stale.

This is why knowing where you subscribed matters more than having a link. We walk through it in cancel an Apple App Store subscription.

Full results

All 42 routes, as checked on 28 July 2026. Domains are shown rather than full URLs because several are long help-centre paths; the live links are in the app.

"Valid sign-in destination" means the route redirects to the service's own login for that page. "Bot-protected" means the server refused our script but served the correct page to a browser, confirmed by hand.

What we'd take from this

• Cancellation URLs decay. Two of 42 broke without warning, and nothing in an app can detect that on its own. If you keep your own list of cancel links, re-check it.
• Check where you subscribed first. If it was an App Store subscription, go to iOS Settings — the provider's site may not be able to help at all.
• A link is not a cancellation. Nothing here confirms you actually cancelled. Go back and check the account page afterwards, and keep the confirmation email.
• Ask any tracker when it last checked. Including ours. That's why this page carries a date rather than a badge.

Sources

1. TrialBell 1.0 service catalog — the 42 cancellationLink values shipped in the app, July 2026
2. Live HTTP checks performed 28 July 2026 from a US-routed connection, unauthenticated, iPhone Safari user-agent
3. Manual browser verification of the four bot-protected routes, 28 July 2026
4. Apple — Subscriptions settings path, iOS 17 and later

Not affiliated with any service listed; referenced only to document public cancellation routes. Last checked 10 October 2026 — routes change without notice, so confirm on the provider's own site.

All research