Cookie Policy
This Cookie Policy explains how NeuroPage uses cookies and similar technologies on its website, platform interfaces, and NeuroPage-hosted personalized pages. It should be read together with the Privacy Policy and Terms of Service.
Last updated: 7 September 2026
Article 1. Introduction and Scope
1.1 This Cookie Policy describes how NeuroPage ("NeuroPage", "we", "us", or "our") uses cookies and similar technologies when individuals visit our website, use our platform, or interact with personalized pages hosted through the Services.
1.2 This Cookie Policy applies to: (a) the NeuroPage marketing website; (b) account login or platform interfaces we operate; and (c) personalized pages hosted by or on behalf of NeuroPage as part of the Services.
1.3 This Cookie Policy does not override the privacy settings, cookie settings, or third-party tracking practices of external websites, customer-owned websites, or third-party services that are not operated by NeuroPage.
Article 2. What Cookies and Similar Technologies Are
2.1 Cookies are small text files placed on a browser or device when a person visits a website or online service.
2.2 Similar technologies may include local storage, tags, scripts, SDKs, pixels, or other technologies that store or access information on a device or help us understand how a webpage or service is used.
2.3 For simplicity, this Policy refers to these technologies collectively as "cookies", unless the context requires otherwise.
Article 3. How NeuroPage Uses Cookies
3.1 NeuroPage uses cookies and similar technologies only for limited and specific purposes connected to operating, securing, measuring, and improving the Services.
3.2 Depending on the relevant page or service, cookies may be used to: (a) keep services functioning properly; (b) maintain session integrity or user preferences; (c) understand page performance and usage patterns; (d) measure engagement with NeuroPage-hosted personalized pages; and (e) support security, abuse prevention, and service diagnostics.
3.3 NeuroPage does not use this Cookie Policy to authorize unrestricted tracking. The categories of cookies actually used by NeuroPage are described below and may be updated from time to time as the service evolves.
| Category | Purpose | Examples / Notes |
|---|---|---|
| Strictly Necessary | Enable core website, account, and page functionality. | May include session continuity, load balancing, security, login persistence, and essential service settings. |
| Analytics | Understand how the website, platform, or NeuroPage-hosted pages are used and improve performance. | May include page views, interactions, scroll depth, referral context, device/browser information, and related usage signals collected through approved analytics tooling. |
| Functional | Remember non-essential preferences where such functionality is enabled. | May include language, display, or interface preferences when used. Functional cookies are only used where implemented and legally appropriate. |
Article 4. Cookies on the NeuroPage Website
4.1 The table below lists every cookie set on neuropage.io and inside the signed-in application, what it does, and how long it lasts. Strictly necessary cookies are set because the service cannot be delivered without them. Analytics cookies are set only after consent, and are not set at all if consent is refused or withdrawn.
| Cookie | Set by | Category | Purpose | Lifetime |
|---|---|---|---|---|
| sb-<project>-auth-token | NeuroPage (Supabase Auth) | Strictly necessary | Keeps a signed-in user signed in and authorises requests to the application. | Session, refreshed while signed in |
| theme | NeuroPage | Strictly necessary | Remembers the light or dark appearance the visitor selected. | Up to 1 year |
| lang | NeuroPage | Strictly necessary | Remembers the interface language the visitor selected. | Up to 1 year |
| Consent preferences | Consent management platform | Strictly necessary | Stores the visitor cookie choices so the banner is not shown again and so tags stay blocked where consent was refused. | Up to 1 year |
| _ga, _ga_<id> | Google Analytics via Google Tag Manager | Analytics | Distinguishes visitors and sessions to measure website traffic. Set only after analytics consent is given. | Up to 2 years |
| _clck, _clsk | Microsoft Clarity | Analytics | Measures how visitors move through the website. Set only after analytics consent is given. | _clck up to 1 year, _clsk 1 day |
4.2 Strictly necessary cookies may be set without consent to the extent permitted by applicable law, because they are required to provide the service you asked for.
Article 5. Analytics and Tag Management
5.1 On the NeuroPage website we use Google Tag Manager to load Google Analytics and Microsoft Clarity. These measure page views, sessions, device and browser attributes, referral context, and interaction signals. The tag manager container itself loads on page load; the analytics tags inside it are held in a blocked state and fire only once analytics consent has been given.
5.2 We use PostHog for product analytics in the signed-in application. PostHog runs on its EU Cloud, and no data is transferred outside the European Union for this purpose.
5.3 Where analytics data remains linked to a customer account, campaign context, or identifiable page usage, NeuroPage applies the retention limits set out in the Privacy Policy. Aggregated and de-identified analytics may be retained for longer for service improvement and benchmarking.
5.4 The providers named here and the data each one receives are listed in full on the Subprocessor List.
Article 6. Personalized Pages Set No Cookies
6.1 Personalized pages served by NeuroPage set no cookies and write nothing to local storage on the device of the person who opens them. No tag manager, advertising pixel, or third-party tracking script is loaded on these pages.
6.2 Page engagement is measured first-party and server-side: NeuroPage records that a page was opened, along with interaction events and technical request data such as device, browser, and IP address. Because a personalized page is generated for one named person, those events are linked to that person and are visible to the customer who sent the page.
6.3 No third-party analytics client, tag manager, or session-replay script is loaded on a personalized page. NeuroPage does not record session replays of the people who receive them.
6.4 NeuroPage does not offer customers a self-service option to place arbitrary third-party advertising pixels or custom tracking scripts on NeuroPage-hosted personalized pages unless expressly agreed otherwise in writing.
Article 7. Cookies on Customer-Owned Domains or External Websites
7.1 If a Customer deploys NeuroPage-generated content on a customer-owned domain, customer-managed hosting environment, or external website outside NeuroPage's direct operation, that Customer is responsible for the cookies, tracking technologies, scripts, consent practices, and disclosures applicable to that environment.
7.2 NeuroPage is not responsible for cookie banners, consent settings, or third-party tracking implementations on websites or domains that it does not operate.
Article 8. Legal Basis and Consent
8.1 Where required by applicable law, NeuroPage will rely on consent for non-essential cookies and similar technologies, including non-essential analytics cookies.
8.2 Where cookies are strictly necessary to provide a requested service or maintain the security and integrity of the website or Services, NeuroPage may use those cookies without consent to the extent permitted by law.
8.3 If a person refuses or withdraws consent for non-essential cookies, certain analytics, preferences, or measurement features may no longer function in the same way, but core access should remain available where legally and technically feasible.
Article 9. Managing Cookies
9.1 Users can manage cookies through available cookie banners or preference tools where implemented by NeuroPage.
9.2 Most browsers also allow users to block, limit, or delete cookies through browser settings. Blocking all cookies may affect the functionality of some pages or services.
9.3 Where browser or device settings are used to reject cookies, some strictly necessary functionality, login continuity, or page delivery features may not operate correctly.
Article 10. Retention of Cookie-Related Information
10.1 The lifespan of a cookie depends on whether it is a session cookie or a persistent cookie and on the technical purpose for which it is used.
10.2 Cookie-related information connected to identifiable, customer-linked, or page-linked analytics is retained only for limited periods as described in the Privacy Policy and applicable service settings.
10.3 Aggregated and de-identified analytics derived from cookie or interaction data may be retained for longer where they are no longer reasonably capable of being linked back to a specific individual, lead, personalized page, or customer campaign.
Article 11. Third-Party Providers
11.1 NeuroPage may use third-party service providers to help deliver analytics, hosting, security, or related infrastructure services. Those providers may place or read cookies or similar technologies on NeuroPage's behalf where necessary for the relevant service.
11.2 The providers that set or read cookies on our behalf are named in the table in Article 4. Every third party that receives personal data from NeuroPage, whether through cookies or otherwise, is named with its role, location, and data categories on the Subprocessor List.
11.3 This Policy does not govern the independent cookie practices of third-party websites, integrations, or services that a user may access outside NeuroPage-operated properties.
Article 12. Changes to this Cookie Policy
12.1 NeuroPage may update this Cookie Policy from time to time to reflect operational, legal, technical, or regulatory changes.
12.2 If changes are material, NeuroPage may provide notice through the website, platform, or other appropriate means. The "Last updated" date at the top of this Policy indicates when the most recent revision was made.
Article 13. Contact
13.1 Questions about this Cookie Policy may be sent to: privacy@neuropage.io