Cookies & browser storage

Three different mechanisms are often lumped together as "cookies", and the rules that apply depend on what is actually being used:

• Cookies — small values sent between your browser and a server with each request.
• Local storage — values saved in your browser and read by the page's own code. Not transmitted with every request, but still covered by the same UK rules on storing information on your device.
• Strictly necessary storage — cookies or local storage that are essential to deliver a service you asked for, such as keeping you signed in. These do not require consent, but they must still be explained.

This list reflects the application as built, not a generic template:

• Authentication session (local storage) — set by our authentication provider once you sign in, so that you stay signed in between page loads and your access token can be refreshed. Strictly necessary. Cleared when you sign out.
• Site-language preference (local storage, ll.publicLocale) — remembers which public-site language you last chose. Strictly necessary preference storage; it never redirects you automatically.
• Demo / live data preference (local storage, ll.dataSource) — remembers whether your workspace is showing illustrative demo data or your own live data, so the choice survives a page reload. Defaults safely to demo.
• Sidebar layout cookie (sidebar_state) — remembers whether the application sidebar is expanded or collapsed. Interface preference only; it contains no identifier.

None of these are used to profile you, build an advertising audience, or track you across other websites.

LinguaLens Insights currently uses no non-essential analytics, advertising or social-media tracking cookies. There is no Google Analytics, no advertising pixel and no third-party tracker on this site or in the application.

Because only strictly necessary and preference storage is in use, we do not show a cookie consent banner. Adding one now would imply we were setting trackers that we are not.

A consent mechanism is already built into the codebase but stays dormant: it defaults to "not granted" and only becomes active if a non-essential tracker is ever added. If that happens, the tracker will be blocked until you opt in, this page will be updated, and a consent banner will appear.

Our hosting and authentication infrastructure records technical request and security information — for example sign-in events, timestamps and request metadata. This is server logging rather than browser storage, and it is described in the privacy notice.

You can clear cookies and local storage for this site at any time using your browser settings. Doing so will sign you out and reset your language and demo/live preferences; the service will otherwise continue to work.

Questions about this page can be sent to our privacy contact address — details to be confirmed before customer onboarding.