Cookie Policy

1. What cookies are

   Cookies are small text files stored on your device when you visit a website. They help a site function, and they can report information back to its owner.

2. What this website does

   This website sets no cookies. It is a set of static files with no analytics, no tracking scripts and no consent banner, because there is nothing to consent to. No third party receives a request from these pages.

   There is one exception, and it only reads. If you already have a HubSpot cookie called hubspotutk on your device, set by another Prospero property, the demo request form includes its value when you submit the form, so that the submission can be attributed. If the cookie is not there, nothing is read and nothing is set in its place. Not submitting the form means the value is never read at all.

3. What we do not do

   We do not use cookies to collect special category data, such as information about health or religion.

   We do not run analytics on this website, we do not set marketing or tracking cookies, and we do not use company-level visitor intelligence here.

4. Managing cookies

   Because this website sets no cookies, there is nothing here to accept or decline. You can still control or delete cookies set by any website through your browser settings.

   Disabling cookies in your browser will not affect this website. It may affect others.

5. Changes to this policy

   We may update this policy to reflect changes in our practices or for other operational, legal or regulatory reasons. If tracking of any kind is added to this website, this page is updated in the same change rather than afterwards.

Where this differs from the published version

This document was carried across from the published version during a website migration. The substance is unchanged. What follows is every point at which this version departs from it, and why, so that the difference is visible rather than something you would have to diff for.

• This is the largest deviation of the three, and it is a correction rather than an edit. The published policy describes essential, performance, functionality and marketing cookie categories, a consent banner, and cookies set by HubSpot and LeadOnion. None of that is true of this website, which sets no cookies at all. A cookie policy that claims to set marketing cookies a site does not set is inaccurate in both directions, so the page describes what the code does.
• The published policy's section 5 explains how to opt out of Google Analytics and Leadfeeder. Neither is named anywhere else in that policy, which names HubSpot and LeadOnion instead. That inconsistency exists in the published version and has not been carried across.
• If analytics, LeadOnion or the HubSpot tracking script are added to this website, this policy is wrong from that moment and the published version becomes the more accurate one. That is a deployment concern, not a drafting one.

This migrated version has not yet been reviewed by a qualified adviser. Until it has been, the published version linked above is the authoritative one.