TrialBell ships 42 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.

Transparency: we make TrialBell, and this audit covers the cancellation routes shipped in our own app. It is a check of our own work, not an independent review. We publish the failures as well as the passes — the two broken routes below were found by this audit, and the fix is recorded here with the date.

The result

As of 28 July 2026, all 42 of 42 routes reach their intended destination: 20 are directly reachable, 18 redirect to the service's own sign-in for that billing or account page (expected — it's your account), and 4 refuse automated requests but were confirmed correct by hand in a browser. None are broken. On the first run, two were.

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 — 42 URLs 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

How each route is classified.
CategoryMeaningCount
Directly reachableReturns the cancellation or account page to an unauthenticated request.20
Valid sign-in destinationRedirects to the service's own login for that exact page. Correct behaviour — it's your account.18
Bot-protected — manually verifiedRefuses scripted requests, but renders the right page in a browser. Each one opened and read by hand.4
Broken or incorrect404, or lands somewhere that isn't the cancellation route.0

What this method can and can't tell you

It proves each route still resolves to the intended page. It does not measure how many taps cancellation takes once you're signed in, whether the page hides the cancel button behind a retention offer, or whether the route differs by country. Those need a signed-in human account on each service, and we haven't done that — so we publish no numbers for it. That measurement is the next update to this page.

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:

The corrected GitHub routes, verified 28 July 2026.
TemplateWasNowResult
GitHub/settings/billing/settings/billing/summaryValid sign-in destination
GitHub Copilot/settings/billing/settings/copilotValid sign-in destination

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.

TrialBell 1.0 cancellation routes — last checked 28 July 2026.
ServiceCategoryRouteResult
ChatGPTAIhelp.openai.comBot-protected — manually verified
GeminiAIone.google.comDirectly reachable
GitHub CopilotAIgithub.comValid sign-in destination
DropboxCloud & Storagewww.dropbox.comValid sign-in destination
Google DriveCloud & Storageone.google.comDirectly reachable
OneDriveCloud & Storageaccount.microsoft.comValid sign-in destination
iCloud+Cloud & Storageapps.apple.comDirectly reachable
Adobe Creative CloudDesign & Creativeaccount.adobe.comDirectly reachable
CanvaDesign & Creativewww.canva.comBot-protected — manually verified
GitHubDevelopergithub.comValid sign-in destination
Apple Fitness+Fitness & Healthapps.apple.comDirectly reachable
StravaFitness & Healthsupport.strava.comDirectly reachable
Amazon PrimeFood & Shoppingwww.amazon.comDirectly reachable
HelloFreshFood & Shoppingwww.hellofresh.comBot-protected — manually verified
Apple ArcadeGamingapps.apple.comDirectly reachable
Xbox Game PassGamingaccount.microsoft.comValid sign-in destination
Apple MusicMusic & Audioapps.apple.comDirectly reachable
AudibleMusic & Audiowww.audible.comDirectly reachable
SpotifyMusic & Audiowww.spotify.comValid sign-in destination
YouTube MusicMusic & Audiowww.youtube.comValid sign-in destination
Apple News+News & Readingapps.apple.comDirectly reachable
The New York TimesNews & Readingmyaccount.nytimes.comValid sign-in destination
1PasswordProductivitymy.1password.comDirectly reachable
Google OneProductivityone.google.comDirectly reachable
GrammarlyProductivityaccount.grammarly.comValid sign-in destination
LinkedIn PremiumProductivitywww.linkedin.comDirectly reachable
Microsoft 365Productivityaccount.microsoft.comValid sign-in destination
ZoomProductivityzoom.usValid sign-in destination
PatreonSocial & Otherwww.patreon.comValid sign-in destination
Apple TV+Streamingapps.apple.comDirectly reachable
CrunchyrollStreaminghelp.crunchyroll.comBot-protected — manually verified
Disney+Streamingwww.disneyplus.comDirectly reachable
HuluStreamingsecure.hulu.comValid sign-in destination
MaxStreamingwww.hbomax.comValid sign-in destination
NetflixStreamingwww.netflix.comValid sign-in destination
Paramount+Streamingwww.paramountplus.comDirectly reachable
PeacockStreamingwww.peacocktv.comDirectly reachable
YouTube PremiumStreamingwww.youtube.comValid sign-in destination
ExpressVPNVPN & Securitywww.expressvpn.comDirectly reachable
NordVPNVPN & Securitymy.nordaccount.comValid sign-in destination
ProtonVPN & Securityaccount.proton.meDirectly reachable
SurfsharkVPN & Securitymy.surfshark.comValid sign-in destination

"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.

42 built-in cancellation routes, checked and kept current

TrialBell reminds you before the deadline and opens the provider's cancellation page in one tap. Free for 3 subscriptions; Pro is a one-time $19.99.

Coming soon to theApp Store

Free for up to 3 subscriptions · Pro is $19.99 once · iPhone · iOS 17+

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 28 July 2026 — routes change without notice, so confirm on the provider's own site.

All research