Essential account and display storage
LimeVu uses a session cookie and CSRF protection for sign-in and account actions. The session can also remember your portal language. A remember-login cookie may be used when that option is enabled. Blocking these cookies can prevent account actions.
The limevu_signage_device cookie stores an encrypted, randomly generated browser identity used to bind an activation code and enforce one-device access. It is set for up to one year. Short playback leases still expire independently; keeping the cookie does not grant permanent access. Clearing it or reinstalling a player may require an administrator to release and reactivate the code.
Native players also keep their selected service, campaign address and separate WebView profile locally. Video buffering is temporary and does not provide indefinite offline playback.
Optional analytics
If enabled by the site administrator, Google Analytics loads on public website pages only after you choose Accept analytics. Choosing Reject leaves campaign and player access available. The local key limevu.analytics-consent.v1 remembers your choice for 180 days. Google may then set _ga and related analytics cookies; their lifetime depends on the configured Google property. We do not load this analytics integration in the account portal or player.
Other providers
Cloudflare/Turnstile may use security storage when enabled. YouTube slides connect to its embedded player and may use provider storage when played. Google login and payment pages can use their own essential cookies. Consult the provider privacy notices linked in the Privacy Policy for their controls.
The contact page connects to Google Maps only when you choose to show the map.
Change your choice
When analytics is enabled, use the Analytics preferences button on public pages to accept or reject. Rejection disables future analytics collection through this integration and removes the accessible Google Analytics cookies. Browser settings can clear stored data, but this also removes consent choices, sessions and device identities. Withdrawing consent does not undo processing that already occurred. Contact [email protected] for help.