1. Introduction
1.1 Burges Salmon LLP and all Burges Salmon entities (“we”, “us”, or “our”) are committed to respecting and protecting your privacy. Our Privacy Policy explains how we will collect, store and use any personal data you provide via our website, email or networking with our people and when you otherwise communicate with us.
1.2 This Cookie Policy explains how we use cookies, why and how this improves our service to you. It also sets out how you can manage your cookies.
1.3 By visiting our website, using our apps or other digital service you are accepting and consenting to the practices described in this Cookie Policy.
1.4 We reserve the right to make changes to this Cookie Policy at any time. This Policy may change from time to time and, if it does, the up-to-date version will always be available on our website and becomes effective immediately. Your continued use of our website, apps or other digital service is taken as meaning that you agree to any such changes.
2. What are cookies
A cookie is a small text file which is downloaded to your device when you visit a website or use an app.
3. Why do we use cookies?
Cookies help us to distinguish you from other users and to see how you interact with our website, app or other digital service. This information can help us to improve our website, apps and surface website content based on your previous browsing behaviour.
3. What types of cookies do we use?
We use the following types of cookies:
(a) Analytical and performance cookies
We may use analytics service providers for website or app traffic analysis and reporting. These providers use cookies to generate statistical and other information about how you use our website or app. The analytics generated include the number of visitors to the site or app, how long they stay and how they navigate the site or app. This helps us to improve the way our website and apps work. The analytics generated may be used to create reports about the use of our site or apps and the analytics service provider will also store this information.
(b) Advertising and targeting cookies
We may use cookies such as the Google AdWords tracking cookie to advertise online. This cookie uses information about you and your browsing behaviour on our site to serve relevant adverts across the Google Display Network. You can opt out of Google’s AdWords cookies at any time by changing your preferences in Google’s Ad settings.
(c) Functionality cookies
We may use functional cookies that remember choices you have made when browsing our site or app. We are then able to provide a more personalised and enhanced user experience by delivering content related to your interests.
(d) Strictly necessary cookies
These cookies are required for the administration and operation of our website, app or other digital service. Some cookies that we use are necessary for our site, app or other digital service to function properly and to enable you to navigate and use its features.
(e) Third party cookies
Third party cookies are cookies that exist on our website, apps or other digital services but originate from different domains. For example, we encourage visitors to share our content on various social networks. We add buttons to allow people easily to share to those networks. When we include these social ‘plugins’, it gives those sites the flexibility to use cookies. They can’t read any cookies we set from our website, app or other digital service, and we can’t read any cookies they set.
Other websites, apps and other digital services (e.g. advertising networks, web traffic analysis services and content recommendation engines) may also use cookies. We have no control over these cookies and you can find out more about them by checking the third party providers’ websites. These cookies are likely to be analytical/performance cookies or targeting cookies.
See below for a list of our main cookies:
| Cookies used | Why do we use this cookie? |
| ASP.NET_SessionId | To keep track of any information that is stored during a visit of the Site. This cookie will only be created when it is needed and will expire at the end of the session. |
| cookieyes-consent | CookieYes sets this cookie to remember users’ consent preferences so that their preferences are respected on subsequent visits to this site. It does not collect or store any personal information about the site visitors. |
| __cf_bm | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
| _cfuvid | Calendly sets this cookie to track users across sessions to optimize user experience by maintaining session consistency and providing personalized services |
| yt-remote-device-id | YouTube sets this cookie to store the user’s video preferences using embedded YouTube videos. |
| ytidb::LAST_RESULT_ENTRY_KEY | The cookie ytidb::LAST_RESULT_ENTRY_KEY is used by YouTube to store the last search result entry that was clicked by the user. This information is used to improve the user experience by providing more relevant search results in the future. |
| yt-remote-connected-devices | YouTube sets this cookie to store the user’s video preferences using embedded YouTube videos. |
| yt-remote-session-app | The yt-remote-session-app cookie is used by YouTube to store user preferences and information about the interface of the embedded YouTube video player. |
| yt-remote-cast-installed | The yt-remote-cast-installed cookie is used to store the user’s video player preferences using embedded YouTube video. |
| yt-remote-session-name | The yt-remote-session-name cookie is used by YouTube to store the user’s video player preferences using embedded YouTube video. |
| yt-remote-fast-check-period | The yt-remote-fast-check-period cookie is used by YouTube to store the user’s video player preferences for embedded YouTube videos. |
| sp_t | The sp_t cookie is set by Spotify to implement audio content from Spotify on the website and also registers information on user interaction related to the audio content. |
| sp_landing | The sp_landing is set by Spotify to implement audio content from Spotify on the website and also registers information on user interaction related to the audio content. |
| loglevel | Squarespace sets this cookie to maintain settings and outputs when using the Developer Tools Console on the current session. |
| .PassleASPXANONYMOUS | |
| __Secure-ROLLOUT_TOKEN | |
| YSC | Youtube sets this cookie to track the views of embedded videos on Youtube pages. |
| VISITOR_INFO1_LIVE | YouTube sets this cookie to measure bandwidth, determining whether the user gets the new or old player interface. |
| VISITOR_PRIVACY_METADATA | YouTube sets this cookie to store the user’s cookie consent state for the current domain. |
| yt.innertube::requests | YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. |
| yt.innertube::nextId | YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. |
| li_gc | Linkedin set this cookie for storing visitor’s consent regarding using cookies for non-essential purposes. |
| lidc | LinkedIn sets the lidc cookie to facilitate data center selection. |
| _ga | Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site’s analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. |
| _gid | Google Analytics sets this cookie to store information on how visitors use a website while also creating an analytics report of the website’s performance. Some of the collected data includes the number of visitors, their source, and the pages they visit anonymously. |
| _gat_UA-* | Google Analytics sets this cookie for user behaviour tracking. |
| _ga_* | Google Analytics sets this cookie to store and count page views. |
| _hjSessionUser_* | Hotjar sets this cookie to ensure data from subsequent visits to the same site is attributed to the same user ID, which persists in the Hotjar User ID, which is unique to that site. |
| _hjSession_* | Hotjar sets this cookie to ensure data from subsequent visits to the same site is attributed to the same user ID, which persists in the Hotjar User ID, which is unique to that site. |
| _hjTLDTest | To determine the most generic cookie path that has to be used instead of the page hostname, Hotjar sets the _hjTLDTest cookie to store different URL substring alternatives until it fails. |
| bcookie | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs. |
| muc_ads | Twitter sets this cookie to collect user behaviour and interaction data to optimize the website. |
| personalization_id | Twitter sets this cookie to integrate and share features for social media and also store information about how the user uses the website, for tracking and targeting. |
(f) cookies stored via our apps:
| Cookie | Issuer | Source |
https://burges-salmon-c19.mendixcloud.com | DeviceType | Determines the type of device accessing the service, e.g. Desktop or Mobile. Used to determine best display of page for the specific device. |
| https://burges-salmon-c19.mendixcloud.com | Profile | The display profile to use based on the DeviceType cookie. |
| https://burges-salmon-c19.mendixcloud.com | XASESSIONID | Used to maintain user session. |
| https://burges-salmon-c19.mendixcloud.com | originURI | Used to determine how the user logged into the service. |
| https://burges-salmon-c19.mendixcloud.com | Xasid | Used for load balancing infrastructure services. |
| https://burges-salmon-c19.mendixcloud.com | cc_cookie_accept | Used to track acknowledgement of the cookie notice. |
| https://burges-salmon-c19.mendixcloud.com | cc_cookie_decline | Used to track rejection of the cookie notice. |
5. Cookie consent
On your first visit to our website or app you will be notified of our use of cookies and will be given the option to accept all cookies or opt in and out of specific groups of cookies via our preference centre. The preference centre is always accessible via the ‘Privacy Settings’ link in our website footer should you wish to change your settings at any time.
6. Policy revision history
| Version | Revision date | Summary of changes |
| 1 | March 2018 | New policy created to provide separate Privacy Policy and Cookie Policy Policy approved by Paul Haggett as GC |
| 2 | June 2018 | Policy updated to remove reference in section 5 to new cookie functionality post 25 May. Policy approved by Paul Haggett as DPO. Published to Burges Salmon website 10 July 2018. |
| 3 | September 2018 | Updated section 5 to detail new cookie consent functionality. Policy approved by Paul Haggett as DPO. Published to Burges Salmon website 27 September 2018. |
| 4 | April 2020 | Updated to include reference to apps and other digital services and associated cookies collected. Approved by Paul Haggett as DPO on 7 April 2020. Published to Burges Salmon website in April 2020. |
| 5 | March 2025 | Updated to include correct references to apps and other digital services and associated cookies collected within the new website structure. Published to Burges Salmon website in March 2025. |