The policy sets out the different areas where user privacy is concerned and outlines the obligations & requirements of the users, the website and website owners. Furthermore, the way this website processes, stores and protects user data and information will also be detailed within this policy.
This website and its owners take a proactive approach to user privacy and ensure the necessary steps are taken to protect the privacy of its users throughout their visiting experience. This website complies to all UK national laws and requirements for user privacy.
You can modify your cookie settings at any time.
Cookies consist of pieces of text, often including unique identifiers, that are sent by web servers to web browsers, and which may then be sent back to the server each time the browser requests a page from the server.
Cookies can be used by web servers to identity and track users as they navigate different pages on a website and to identify users returning to a website.
Cookies may be either “persistent” cookies or “session” cookies. A persistent cookie consists of a text file sent by a web server to a web browser, which will be stored by the browser and will remain valid until its set expiry date (unless deleted by the user before the expiry date). A session cookie, on the other hand, will expire at the end of the user session, when the web browser is closed.
Cookies on our website
We use both session cookies and persistent cookies on this website.
We will send to you the following cookies:
This is the main way Google Analytics tracks unique visitors. Stored in this cookie is a unique visitor ID, the date and time of their first visit, the time their current visit started and the total number of visits they have made.
The __utma cookie is a persistent cookie that expires in two years. With each new visit, the expiration date is refreshed.
This is how Google Analytics decides whether a visit has timed out and also how deep a visit has gotten. It stores the number of pageviews in the current visit and the start time of the visitor's current visit.
The __utmb cookie is a persistent cookie and each pageview refreshes it. (Expires: 30 minutes)
The expiration time can be customized for each site (or page).
The __utmc cookie is the only session cookie used by Google Analytics. Its only purpose is to register that the visit ended if the browser gets closed. (Expires: Session cookie)
This is the traffic source cookie. It contains all of the traffic source information for the current visit, if it was different from the previous visit. If no traffic source information can be found for the current visit, the cookie is not changed. This is the way that Google Analytics attributes visit information, including conversions and transactions to a traffic source. It does not contain historical information for previous sources. This cookie is only refreshed when the traffic source changes. (Expires: 6 months)
This cookie is used by Google Analytics to track website visits. You can find more information about it here. (Expires: 2 years)
This cookie contains a unique hash, which is used to prevent hack attacks on the website, protecting from Cross-site request forgery (Expires: Session cookie)
This cookie contains information about the current website session. It is used by PHP Framework, Laravel which the website is built on (Expires: Session cookie)
This cookie contains a unique identification string, which helps us associate you with a user type in one of the user behaviour tracking tools we use - Woopra (Expires: 2 years)
What cookies does HubSpot set in a visitor's browser?
HubSpot's tracking code sets the following cookies when someone visits your site:
The main cookie for tracking visitors. It contains the domain, utk (see below), initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). (Expires: 2 years)
This cookie is used for to keep track of a visitor's identity. This cookie is passed to HubSpot on form submission and used when de-duplicating contacts.(Expires: 10 years)
This cookie keeps track of sessions. This is used to determine if we should increment the session number and timestamps in the __hstc cookie. It contains the domain, viewCount (increments each pageView in a session), and session start timestamp. (Expires: 30 min)
Whenever HubSpot changes the session cookie, this cookie is also set. We set it to 1 and use it to determine if the user has restarted their browser. If this cookie does not exist when we manage cookies, we assume it is a new session. (Expires: None. Session cookie)
This cookie can be set to prevent the tracking code from sending any information to HubSpot. Setting this cookie is different from opting out of cookies, which still allows anonymized information to be sent to HubSpot. (Expires: 2 years)
This cookie is used to test whether the visitor has support for cookies enabled. (Expires: Session cookie)
This cookie is used to keep track of page views in a session. (Expires: Session cookie)
This cookie is used to recognize visitors who chat with you via the messages tool. If the visitor leaves your site before they're added as a contact, they will have this cookie associated with their browser. If you have a history of chatting with a visitor and they return to your site later in the same cookied browser, the messages tool will load your conversation history with that visitor. Learn more here.
If you are logged in to HubSpot, HubSpot will set additional authentication cookies. You can see a complete list of cookies set by HubSpot's app here.