Loading...
Loading...
We hold ourselves to the standard we audit other companies on. These are the seven observable signals our cancellation flow is measured against.
Note (2026-05-08): TrustedMetrics is currently in an ad-supported phase. The subscription paywall is paused — there are no plans to buy and nothing to cancel for new users today. This page documents the cancellation flow as it exists for future paid users, audited against the same standard we apply to other companies on /cancellation-leaderboard (Phase 1).
Within TrustedMetrics surfaces, signup and cancel each take a single decisive click after the user has navigated to the relevant page. Stripe Portal handles the final confirmation — same pattern as Apple App Store managed subscriptions.
Measured manually after PR #99. No retention puzzles or delays gating the action. Stripe Portal redirect is direct.
A "Pause for 1–3 months" alternative card sits adjacent to the Cancel CTA, but it does not block, gate, or interrupt the cancellation action.
No intermediate confirmation pages, no email "are you sure" loops, no support-ticket detours.
Cancellation takes effect at period-end (standard); status reflects the change immediately in /dashboard/settings/billing.
No mobile-only friction; no app-only cancellation gate; no "cancel from desktop" requirement.
After period-end fully cancels the subscription, restarting requires a fresh checkout (standard).
Each signal is observable telemetry, not interpretation. We report what was measured, not what we judge it to mean. The same instrumentation we ship on /cancellation-leaderboard applies here — no exceptions.
Audit cadence: this page updates whenever the /dashboard/settings/billing/cancel flow changes. Last underlying commit: 2f0004c.
Reproducibility: the audit script that captured these numbers is open-source and shippable in CI (Phase 1.x).