Eligibility and subscription requirements
Who can run the extension.
The server checks your subscription on every extension call. This is not a client-side gate you can bypass by editing the extension; the check reads trusted billing records only.
Who is eligible
| Subscription state | Can use the extension? |
|---|---|
| Active or successful subscription on an eligible plan | Yes |
| Cancelled, but the paid-through end date is still in the future | Yes, until that end date |
| Expired | No |
| Trial that has ended, or a failed/halted payment | No |
| Pending | No |
| A live subscription on a plan your deployment does not mark eligible | No |
| No subscription at all | No |
| Administrator account | Yes, treated as the highest plan |
Which plans are eligible
Eligibility is defined server-side. The default eligible set is Starter, Pro and Premium. On a lapsed token, protected calls return a subscription-required response with a link to the plans page rather than silently failing.
How it is enforced
- Authenticating the token and checking entitlement are separate steps; entitlement is re-checked on every protected call.
- Nothing the browser sends (plan names, flags, ids) is trusted. Only server-side billing records are used.
- Administrators are entitled without a subscription, but spend budgets and rate limits still apply.