Cookie Preferences
Lumio asks for your consent before setting non-essential cookies. The consent dialog opens by itself on your first visit; afterwards you can reopen it from the round cookie button in the bottom-right corner (tooltip: Cookie settings).
Categories
| Category | Required | Examples |
|---|---|---|
| Essential | Always on | Login and refresh tokens, pop-out session, language and other preference mirrors, Cloudflare security, Auth.js login cookies on the ID app |
| Functional | Opt-in | Platform integrations (Twitch, YouTube, Kick, Discord), UI preferences, Sentry error tracking |
| Statistics | Opt-in | Anonymous product analytics (PostHog, when enabled) |
| Marketing | Opt-in | Reserved for future advertising integrations, currently unused |
Only Essential is on by default - functional, statistics and marketing start switched off until you accept them.
Preference cookies
Lumio uses four necessary preference cookies for display settings:
| Cookie | Category | Purpose |
|---|---|---|
locale | Essential | Mirrors your selected UI language so server-rendered pages load the right message catalog. |
lumio-tz | Essential | Mirrors your resolved timezone so server-rendered pages can format times in the same zone as the dashboard. |
lumio-season | Essential | Mirrors your Appearance settings (seasonal look, strength, animations, creature switches, closed seasonal banners) so the dashboard paints the right look before it has loaded. |
lumio-motion | Essential | Mirrors your Animations in Lumio setting (System, Reduced, Off) so the dashboard starts without unwanted motion before it has loaded. |
These cookies are preference state, not tracking. They are set from your Region & Language and Appearance settings and from the language switcher. The cookie-clearing dialog lists them under Preferences so you can remove them from the browser; your signed-in user preferences remain stored on your user profile and can repopulate the mirrors after the next dashboard render.
A shared web or sign-in link with a valid ?lang=en or ?lang=de can also set the locale cookie when your browser does not have one yet. It leaves an existing cookie unchanged. See Language.
How to change
Open the dialog via the cookie button. The first view offers Essential only, Accept all and Customize.
Pick Customize to switch the three optional categories individually, then confirm with Save preferences. Each category can be expanded to list the cookies and browser-storage keys it covers, with their purpose and duration.
Your choice is stored in your browser and read again on every page load, so it applies to new tabs and later visits in the same browser.
Revoking
Reopen the dialog and choose Essential only - statistics, functional and marketing cookies stop being set from that point on. Necessary preference cookies such as locale, lumio-tz, lumio-season and lumio-motion may still be set because they are required for rendering.
Cookies that were already set are not removed by that choice. To clear them, use the Cookies link in the page footer (see below).
Clearing cookies and dashboard data
The Cookies link in the page footer opens the Manage Cookies dialog. Select one or more categories and confirm with Clear:
| Category | What it clears |
|---|---|
| Authentication | lumio-token, lumio-refresh, lumio-popout-token, lumio-popout-origin. These cookies are httpOnly, so the dialog cannot count them and shows only an httpOnly badge. Clearing them signs you out in this browser and ends pop-out sessions opened in this browser; an OBS browser source is a separate browser and is not affected. |
| Preferences | The four preference cookies above, plus the theme and sidebar state stored in this browser. Your profile settings stay on your user profile and repopulate the cookies on the next dashboard visit. |
| Dashboard data in this browser | What the dashboard keeps in this browser's local storage: chat filters, keyword tabs, chat platform selections, chat alert settings, the viewer-list toggle, event filters, pop-out display settings, recent emotes and colours, and the emote cache. Chat filters, keyword tabs and alert settings saved only on this device are lost. The dialog shows how many entries are present. |
Some entries are never cleared by the dialog: streamer mode stays as it is (clearing it would switch streamer mode off without notice and could reveal private data on stream), your cookie consent choice is changed only in the consent dialog, and developer preview settings stay untouched.
The Auth.js login cookies of the ID app (id.lumio.vision) belong to that site; this dialog cannot read or clear them and does not list them.
Where the dialog appears
The consent dialog and its floating button are shown on Lumio's public pages - the marketing site, the legal section and the login flow.
They are deliberately suppressed on the dashboard (/dashboard, /account, /hub) and on OBS browser-source routes (/overlay/…, /popout/…), where a consent dialog would cover a live capture. Your stored choice still applies on those routes - only the dialog itself is hidden. To change it while you are in the dashboard, open a public page such as /legal/cookies and use the cookie button there. The footer Cookies link for clearing cookies is available everywhere.
Public Stats site
The public Lumio Stats site (stats.lumio.vision) runs the same consent stack: the banner opens on the first visit, the floating cookie button reopens it, and your choice is remembered in that browser. Your consent choice is stored in your browser's local storage, and - like the rest of Lumio - the site uses the essential locale cookie to remember your language. No non-essential script (analytics, error tracking, embedded clips) runs before you accept. Emotes, avatars and panel artwork load from the Stats site itself, so they show without a consent choice; GIPHY GIFs wait for the Functional category, as on the share pages of lumio.vision. Legal and cookie-policy links from that site point back to the main Lumio site (lumio.vision/legal/…).