Cookies and Local Storage Policy
Last updated: Aug 31, 2026
This policy explains how Nebular Studio and its associated overlay-rendering service use cookies and browser storage.
Summary
Nebular Studio does not use analytics, advertising or third-party cookies. The application uses the browser’s localStorage and one strictly necessary authorization cookie for authentication, overlay rendering and functional state needed to provide the Service.
Cookie used for overlay rendering
| Cookie | Purpose | Typical contents | Duration |
|---|---|---|---|
ns-live-token |
Authorizes the browser-based renderer to request protected overlay templates and resources | Authentication token | Until the authorization token expires |
The Overlay Server scopes ns-live-token to its rendering API path and issues it with the Secure and HttpOnly attributes. In production it also uses SameSite=Strict. JavaScript running in the page cannot read an HttpOnly cookie; the browser supplies it only to matching renderer requests.
Browser storage used by Studio
| Storage key | Purpose | Typical contents | Duration |
|---|---|---|---|
nstoken |
Keeps you authenticated between page loads | Your organization identifier and authentication token | Until logout, token expiry or manual deletion |
obst.skin |
Remembers application preferences | Theme, language and storage-policy acknowledgement | Until changed or manually deleted |
localStorage remains on your device and is sent to Nebular only when the application uses the stored authentication token to make an authenticated request. Authentication tokens are security credentials and should not be copied or shared.
Strictly necessary storage
The storage described above supports authentication, security and preferences explicitly requested through the application. Studio does not use it to profile users or deliver advertising.
Because Studio currently uses no optional analytics or advertising storage, there are no optional cookie categories to accept or reject. If that changes, we will update this policy and request consent where required before activating optional storage.
Managing stored data
Logging out removes the persisted Studio authentication token. The renderer authorization cookie expires automatically with its token. You can also remove Studio and renderer browser data through your browser’s site-data or privacy settings. Doing so will sign you out and reset saved preferences.
Your organization, browser, reverse proxy or identity provider may operate additional storage outside Nebular Studio. Their respective policies apply to that storage.
Changes to this policy
We may update this policy if Studio’s use of browser storage changes. The date above identifies the latest revision.
Contact
Questions about this policy may be sent to support@nebular.tv.