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.
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.
Source-backed 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-reported evidence
Source: GitHub Docs: Handling plan cancellations
GitHub tells Marketplace apps to remove customer data within 30 days of the `cancelled` event.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
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.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Marketplaces and Brand, using evidence from GitHub Docs: Handling plan cancellations as context—not as a promised result.
- Record a baseline for: Target users who complete the tactic’s intended next action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.