Updates

Every boilerplate says "lifetime updates". The phrase is usually meaningless, because "lifetime" quietly means the product's lifetime, and abandoned kits are the number-one fear when buying one. So instead of a slogan, here is how it actually works.

What "lifetime updates" means here

Your one-time purchase includes access to the private repository for as long as ExtensionStart exists as a product: every bug fix, platform update, and new module lands in the same repo you already have. No annual renewal, no "updates plan" upsell. Because "as long as the product exists" is the honest definition, we back it with the specifics below.

How updates work

1. Actively maintained, and verifiably so. The kit is under active development: we build on it ourselves, and updates ship to the same repository you bought. We don't put a contractual number on that (nobody honest can promise a product's future); instead we make it checkable: the public changelog is the heartbeat, and the end-of-life terms below are your downside protection. Maintenance activity is never a countdown on access; your repository access doesn't expire.
2. Browser-breakage fixes come first. When Chrome or Firefox change the rules (Manifest V3 revisions, API deprecations, Web Store policy shifts that break the kit), those fixes are prioritized above feature work. A kit that doesn't build against current browsers is broken, and we treat it that way.
3. No SaaS lock-in, even at end-of-life. If ExtensionStart is ever discontinued, the repository stays accessible to license holders and the final source is yours to keep and build on. The kit has no server-side dependency on us: nothing you shipped stops working, and nothing you build next requires our blessing. The worst-case outcome of buying is that updates stop, never that the product is taken away.

The one exception

Only two things end repository access, and neither is "time passed": a refund or chargeback (the purchase is undone; see the refund policy), or a violation of the license. Discontinuation of the product, as described above, is explicitly not one of them.

What updates are not

Updates are not a support contract: email support stays reasonable-effort (see the terms), and "maintenance" means keeping the kit working and current, not building your feature requests on demand.

How to check

Don't take this page's word for it. Look at the changelog. It's the public record of what has shipped and how often; an abandoned kit can't fake a heartbeat.

Questions

Anything unclear: support@extensionstart.com.