Current version, effective 2026-10-22 · All versions
Cookie Policy
1. Introduction
This Cookie Policy explains how NeoSpline ApS ("NeoSpline", "we", "us") uses cookies and similar tracking technologies on our website (neospline.ai), web platform (platform.neospline.ai), login domain (auth.neospline.ai), and associated web interfaces.
We may update this Cookie Policy from time to time. Each version shows the date it was published and the date it takes effect, and earlier versions stay available on this page.
2. What Are Cookies?
Cookies are small text files placed on your device when you visit a website. They are widely used to make websites work, to improve efficiency, and to provide information to the website operator.
Similar technologies include local storage, session storage, and pixel tags. References to "cookies" in this policy cover all such technologies unless stated otherwise.
3. Categories of Cookies We Use
We use three categories of cookies:
Strictly Necessary Cookies are required for the website and services to function. They enable core features such as security, authentication, and session management. These cookies cannot be disabled without affecting service functionality. They are exempt from the consent requirement because they are strictly necessary to provide the service you requested. Where these cookies involve processing of personal data, our legal basis is our legitimate interest in operating a secure and functional website (Art. 6(1)(f) GDPR).
Analytics Cookies help us understand how visitors use our website. They collect information about pages visited, traffic sources, and errors encountered. This information is used to improve our website. These cookies are only placed with your consent.
Support Chat Cookies are set by Intercom, the provider of our support chat. They keep the chat window open between page loads and let you continue a conversation on the same device. We set them only when you use the chat (on the web platform, when you open the chat; in the Support tab of our Rhino plugin, when you open the tab), or, on our website, when you have accepted cookies. Section 5 states when each entry is set on each of our surfaces.
4. Cookie Inventory
On our website, PostHog uses a combination of cookies and browser local storage. Auth0 uses strictly necessary cookies and related browser storage for login and session management. Intercom uses two local storage entries and two cookies for the support chat. The table below covers all three providers and our own entries.
| Provider | Name | Storage Type | Category | Purpose | Duration |
|---|---|---|---|---|---|
| NeoSpline | ns_cookie_consent | Cookie | Strictly Necessary | Consent: Stores your cookie consent preference so we do not ask again on each visit. | 12 Months |
| Auth0 | Auth0-managed login/session cookies | Cookie | Strictly Necessary | Authentication: Maintains login sessions, protects authentication transactions, and supports secure sign-in to the web platform. | Provider/session dependent |
| NeoSpline | Auth transaction storage | Cookie / browser storage | Strictly Necessary | Authentication: Temporarily stores login transaction state needed to complete secure redirect-based authentication. | Short-lived |
| NeoSpline | neospline.theme | Local Storage | Strictly Necessary | Preferences: Stores the light or dark theme you choose on the web platform; without it, the theme follows your device setting. | Persistent |
| NeoSpline | no_track | Local Storage | Strictly Necessary | Analytics opt-out: Stores a flag, set with the no_track link parameter, that turns off all website analytics in this browser. | Persistent |
| NeoSpline | neo:rhino-context | Session Storage | Strictly Necessary | Authentication: Briefly holds your Rhino plugin sign-in request, so the web platform can return you to the plugin after sign-in. | Short-lived |
| NeoSpline | neo:rhino-pending-cancel | Session Storage | Strictly Necessary | Authentication: Holds the address that tells the Rhino plugin a cancelled sign-in has ended; it is read once and then removed. | Short-lived |
| NeoSpline | neo:invite-decision | Session Storage | Strictly Necessary | Invitations: Carries your pending organization invitations from sign-in to the page where you accept or decline them. | Short-lived |
| NeoSpline | neo:verify-email | Session Storage | Strictly Necessary | Authentication: Briefly holds your sign-up email address, so the verification page can show where the email went. | Short-lived |
| PostHog | ph_{key}_posthog | Cookie | Analytics | Identity: Stores a pseudonymous distinct user ID and session ID to distinguish unique visitors and sessions across pages. | 12 Months |
| PostHog | ph_* (various keys) | Local Storage | Analytics | Session & event data: Stores queued events, feature flag results, and session metadata locally in the browser between page loads. | Persistent (cleared on opt-out) |
| Intercom | intercom-id-{app_id} | Local Storage | Support chat | Support chat: Stores an anonymous visitor ID in local storage so the Messenger can show the visitor's earlier support conversations. | Persistent |
| Intercom | intercom-session-{app_id} | Cookie | Support chat | Support chat: Keeps the Messenger session open between page loads, so the user stays in the same conversation. | 7 Days |
| Intercom | intercom-device-id-{app_id} | Cookie | Support chat | Support chat: Identifies the browser to the Messenger, so a conversation continues on the same device. | 270 Days |
| Intercom | intercom.intercom-state-{app_id} | Local Storage | Support chat | Support chat: Caches the Messenger state and conversations in local storage, so the chat opens quickly on the next page load. | Persistent |
The PostHog entries above are set only on our website (neospline.ai), and only with your consent. The web platform (platform.neospline.ai) sets no analytics cookies and stores no analytics data in your browser — see the PostHog section below.
The Intercom entries are set on our website, on the web platform, and in the Support tab of our Rhino plugin, but at different times: see the Intercom section below. In the entry names, {app_id} stands for the identifier of NeoSpline's Intercom workspace.
5. Specific Provider Practices
Auth0
We use Auth0 to provide secure login and session management for the web platform and associated service interfaces. Auth0 uses strictly necessary cookies and related browser storage to maintain authentication sessions, protect login transactions, and support secure redirects between NeoSpline and the login domain.
These cookies and storage entries are required for the web platform to function and are not used for analytics or advertising.
PostHog
We use PostHog for analytics on our website and web platform. Our PostHog instance is hosted on PostHog's European Cloud (EU region), meaning your data is processed and stored within the EEA.
PostHog operates as a first-party analytics tool: it does not track you across other websites and does not share your data with third parties for advertising purposes.
Website (neospline.ai). On our website, we use PostHog for analytics including page view tracking and session events. PostHog cookies and local storage entries are only set after you have given your consent via our cookie banner. The legal basis for this processing is your consent (Art. 6(1)(a) GDPR).
If you decline analytics cookies, no cookies or local storage entries are set and no profile of you is created. We still count your visit in aggregate using PostHog's cookieless server hash mode: PostHog computes a pseudonymous identifier on its servers from your IP address, browser type, our domain, and a project identifier, combined with a salt that rotates daily and is then deleted. This identifier is designed to minimize personal data — it is pseudonymous, is not linkable across days or across websites, and the underlying IP address and browser information are discarded after the identifier is computed. Nothing is stored on or read from your device in this mode, so it requires no cookie consent; the legal basis for the brief server-side processing is our legitimate interest in measuring website audience (Art. 6(1)(f) GDPR). You may object at any time by contacting privacy@neospline.ai (see Your Rights in our Privacy Policy).
Web platform (platform.neospline.ai). On the web platform, PostHog analytics runs exclusively in the cookieless server hash mode described above. It stores nothing in your browser — no cookies, no local storage, and no session storage — and page views are counted anonymously without creating a profile of you. Because nothing is stored on or read from your device, no cookie consent is required, and the web platform therefore shows no analytics consent banner. The cookies and browser storage on the web platform are the strictly necessary entries listed in the inventory above and, only after you open the support chat, the Intercom entries described in the next section.
Separately, we collect product usage analytics about your use of the Services through our own servers, not through your browser. That server-side collection involves no cookies or other device storage and is therefore outside the scope of this Cookie Policy; it is described in our Privacy Policy under "Product development and improvement," including the legal basis and your right to object.
Intercom
We use Intercom to run the support chat. On the web platform and in the Support tab of our Rhino plugin, the chat is the in-app support channel for our customers. On our website, it lets visitors ask pre-sales questions. Our Intercom workspace is hosted in the United States. The Privacy Policy describes the personal data that the chat processes, the legal basis, and the safeguards for the transfer.
Intercom's code is not loaded, and none of its entries are set, until one of the events below happens. We use the chat for support only, never for advertising.
Website (neospline.ai). The chat works in one of two ways, depending on your cookie choice:
- If you have accepted cookies in our cookie banner, the chat loads when a page loads, and its entries are set from then on. The legal basis is your consent (Art. 6(1)(a) GDPR).
- If you have not accepted cookies, the page shows our own chat button and loads nothing from Intercom. When you click the button, Intercom loads and the chat opens. Your click is an explicit request for the chat service, and Intercom sets its entries only after that click.
On the website, we send Intercom no account identity. A visitor who writes in the chat is anonymous to us until the visitor gives us their own details in the conversation.
Web platform (platform.neospline.ai). The chat loads only when you click the chat bubble or the Help item in the navigation. It never loads on its own, and the web platform shows no consent banner for it. It loads only as far as needed to deliver the support included in your subscription, and Intercom sets its entries only after you open the chat. The Privacy Policy lists the identifiers we share with Intercom when you open the chat.
Rhino plugin (Support tab). When you open the Support tab, a separate webview inside the plugin loads the page /plugin-support of our web platform, and the chat starts in that webview. The chat never starts before you open the tab, and Intercom sets its entries in the webview only after you open it. Opening the tab is your explicit request for the chat, so the plugin shows no consent banner for it. The entries are the same as on the web platform, with the same durations. The webview keeps its storage between Rhino sessions, like a browser profile. We start the chat with the identity of the account you are signed in with in the plugin, so you do not sign in a second time. When you sign out in the plugin, or your plugin session expires, the chat session in that webview ends. If the chat cannot start, the tab shows our support email address, support@neospline.ai, instead. The plugin itself sends Intercom no further data.
6. Consent and Your Choices
When you first visit our website, we display a cookie banner. Analytics cookies are disabled by default and are only activated if you click "Accept" or otherwise provide your consent. Rejecting analytics cookies is as easy as accepting them: the banner provides a "Reject" option with equal prominence to "Accept," and no analytics cookies are set if you reject or close the banner. Strictly necessary cookies are active regardless of your choice.
The web platform shows no analytics consent banner because its analytics sets no cookies and stores nothing in your browser (see Section 5). The strictly necessary cookies it uses are exempt from the consent requirement. The support chat on the web platform and in the plugin's Support tab loads only when you open it (see Section 5), so it needs no banner either.
The same banner covers the support chat on our website. If you accept cookies, the chat loads when a page loads. If you reject or close the banner, the chat does not load, and you can still start it with our own chat button. If you withdraw consent after the chat has loaded, we close the chat session and show our own chat button again.
You can change or withdraw your consent at any time via the "Cookie settings" link in our website footer; withdrawal does not affect the lawfulness of processing before withdrawal.
If you decline or withdraw consent, we no longer set analytics cookies or local storage entries. We continue to count visits in aggregate using the cookieless method described in Section 5 above, which stores nothing on your device. Because that method involves no identifier stored on your device or attributable to you as a person, it cannot be switched off per visitor through the banner — if you object to it, contact us at privacy@neospline.ai.
You can also control or delete cookies through your browser settings. Please note that disabling certain cookies may affect the functionality of our website. For guidance on how to manage cookies in your browser, refer to your browser's help documentation or visit www.allaboutcookies.org (opens in a new tab).
7. No Sale or Sharing for Advertising
We do not sell personal data collected via cookies to third parties. We do not share personal data collected via cookies with third parties for their own marketing or advertising purposes.
8. Data Retention
The "Duration" column in the cookie inventory above refers to how long cookies and local storage entries persist on your device (for the Support tab of the Rhino plugin, in the plugin's webview). Server-side analytics data (the events collected by PostHog) is retained separately for up to 24 months. The "Duration" column does not cover support conversations or the visitor and user records in Intercom; the Privacy Policy states how long we keep them. Aggregate visit counts collected via the cookieless method (Section 5) are keyed to a daily-rotating pseudonymous identifier and are no longer attributable to any visitor after the daily salt is discarded. For more information on our data retention and deletion practices, see our Privacy Policy.
9. Contact
If you have questions about our use of cookies, please contact us at:
NeoSpline ApS — see our Imprint for full company details.