Back to GrowthDex
Growth idea action plan

GitHub Marketplace cancellation cleanup within 30 days

Turn cancellation handling into a trust rule, with account deactivation, token revocation, webhook removal, and data deletion within 30 days after the Marketplace cancel event.

epic tacticlow budget

Why this can grow a startup

Cancellation is part of the product surface whether teams like it or not. GitHub is unusually clear about the cleanup steps after a Marketplace plan ends: deactivate the customer account, revoke the OAuth token, remove repository webhooks for OAuth apps, and remove customer data within 30 days of the `cancelled` event. That matters for growth because developer buyers remember exit friction. A clean offboarding flow lowers security anxiety, makes procurement conversations easier, and signals that the team can be trusted with repo access in the first place.

Company example

GitHub's cancellation guide says apps must deactivate the customer's account, revoke the OAuth token, remove repository webhooks for OAuth apps, and remove customer data within 30 days after receiving the `cancelled` Marketplace webhook.

Source and metric

Source: GitHub Docs: Handling plan cancellations

GitHub tells Marketplace apps to remove customer data within 30 days of the `cancelled` event.

MarketplacesBrandSecurityoffboardingsecurity trustdeveloper toolscompliance ops
GrowthDex operator note

When to use it

Use this when Marketplaces, Brand, Security is relevant to offboarding, security trust, developer tools and you can run a bounded test with a low budget.

When not to use it

Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.

Founder checklist

  1. Read GitHub Docs: Handling plan cancellations and identify what is directly supported.
  2. Choose one channel context: Marketplaces, Brand, Security.
  3. Define the test around GitHub tells Marketplace apps to remove customer data within 30 days of the `cancelled` event..
  4. Set an owner, evidence window, and stop condition before launch.

Explore the context

Advisory bridge

Apply this with an operator

Choose product surfaces that compound distribution without hiding weak activation or retention.

Work with Ian