Cookies & storage

About this draft notice

Cookies are small values stored by a browser and sent with matching requests. Local storage and browser caches are other ways to retain information on a device. This draft covers the current application’s use of those technologies and needs a production review before it becomes effective.

The main website

The current marketing website does not add advertising pixels, third-party analytics scripts, or a nonessential cookie preference system. Interactive examples run in the page, and the site’s current fonts are served locally.

Hosting infrastructure can have separate logs or storage behavior. No consent banner is included just to imply that optional tracking exists; if optional tracking is added, the notice and any required consent controls need to be implemented together.

The management portal

Local-storage values can remain until the application removes them or you clear the site’s data. Blocking authentication cookies can prevent sign-in.

• Authentication cookies: support signed-in sessions. Their expiry is controlled by the authentication service.
• Selected location: the ck:venueId local-storage value remembers your workspace selection on that browser.
• Interface state: local storage can remember your color-theme preference and that a first-publish celebration has already been shown.

The screen player

Local board data and credentials do not have those image or font cache expiry limits. They can remain until replaced or cleared. Offline playback depends on data having loaded successfully first.

• ck:playerToken stores the paired player’s credential. Treat it as a secret.
• ck:bundle stores the downloaded board and version; ck:live stores the last saved live state.
• Local play-report storage holds reports waiting to be sent to the service. Weather widgets can also store their last fetched forecast in ck:weather values.
• A service worker caches the player application and supported assets. The current cache configuration allows images for up to 30 days and fetched fonts for up to one year, subject to cache limits and browser eviction.

External provider pages

Stripe-hosted checkout, payout onboarding, and billing management, and Square authorization pages operate under those providers’ own storage and privacy practices. Some board fonts are fetched from Google Fonts and can be cached by the player.

Manage or remove stored data

Use your browser’s site-data settings to inspect, block, or remove cookies and storage for each ConcessionKit site you use. The website, portal, and player may be on separate domains and need separate removal.

Clearing portal data can sign you out and reset preferences. Clearing player data and caches removes offline content and can require pairing again. Before reassigning a player device, clear its site data on the device itself; server-side account changes cannot guarantee deletion of an offline copy.