How licensing and continuity work
The banner runs entirely on your own server. It does not call our servers on every page — licensing is a light background check, and a temporary outage does not interrupt your visitors.
related: Security & Architecture
The banner runs locally
Validation happens in the background, roughly once a day — not on every page a visitor opens. Cookie Craft keeps the last valid signed verdict and applies it, so your banner does not wait on a network call while a visitor loads a page. This is the difference between a first-party runtime and a hosted script that phones home.
If validation is temporarily unavailable
A short outage of our licensing service does not take your banner down.
Last verdict is kept
If the API does not respond, or the response cannot be validated, Cookie Craft keeps using the last valid signed verdict. A failed day is recorded at most once per day.
Seven days of grace
The product keeps working through seven consecutive days of failed checks — ample room for any normal outage to resolve.
Admin always accessible
Only after seven failed days does the front-end runtime go inactive. The admin stays accessible throughout, and your configuration is never deleted.
If a subscription lapses
Non-payment is handled separately from an outage. The licensing server can grant a commercial grace period of seven days after your valid_until date: during it the status is grace, and the front end continues to work until grace_until. You are not cut off the moment a renewal is late.
Suspension, revocation and domain mismatch
Signed statuses such as suspended, revoked, domain_mismatch or a kill_switch are different from a simple outage — they do not use the outage tolerance. They take effect when the signed verdict is received, normally at the next scheduled check. This keeps the model predictable: temporary unavailability is forgiving; an explicit signed decision is applied as intended.
Runs on your server. Predictable by design.
A first-party runtime that doesn’t depend on us at every page load. See the architecture.