How Greenhill Events uses the information we collect
Your personal data is held for the purpose of dealing with your requests for information and for any work you have asked us to undertake. Not at any point will we sell, rent or deal in your personal information and will only pass on your details to a third party under the circumstance where you have requested we do in connection with our services.
In accordance with your rights under the Data Protection Act 1998 and upcoming General Data Protection Regulation, at any time you may request the amendment of your personal information or cease receiving material from us.
Cookies - What are they?
Cookies are simple text files that typically hold a minimal amount of data specifically relevant to your visit on a site. They are not programs and they do not actively do anything.
They are designed to improve your user experience of a website, enabling facilities like:
- Remembering your user ID or password so you do not need to keep entering them every time you visit a fresh page.
- Customising a web page to your requirements
- Identifying when a website is not providing users with the information they are looking for
They are not programs and they do not actively do anything. A web server sends you a cookie and your browser stores it. The browser then returns the cookie to the server the next time the page is referenced.
- General cookies
This website is built using PHP web technologies, as part of that we use the built in session cookie ‘Symphony’ to manage your session. When you navigate to the site, the server establishes a unique session that last for the duration of your visit.
- Google Analytics
The following lists the type of information that is obtained via Google Analytics cookies and used in Analytics reports.
Setting the scope of your site content
Because any cookie read/write access is restricted by a combination of the cookie name and its domain, default visitor tracking via Google Analytics is confined to the domain of the page on which the tracking code is installed. For the most common scenario where the tracking code is installed on a single domain (and no other sub-domains), the generic setup is correct. In other situations where you wish to track content across domains or sub-domains, or restrict tracking to a smaller section of a single domain, you use additional methods in the ga.jstracking code to define content scope. See Domains & Directories in the Collection API document for details.
Determining visitor session
The Google Analytics tracking for ga.jsuses two cookies to establish a session. If either of these two cookies are absent, further activity by the user initiates the start of a new session. See the Session article in the Help Center for a detailed definition and a list of scenarios that end a session. You can customise the length of the default session time using the _setSessionCookieTimeout() method.This description is specific to the ga.js tracking code for web pages. If you use Analytics tracking for other environments—such as Flash or mobile—you should check the documentation for those environments to learn how sessions are calculated or established.
Identifying unique visitors
Each unique browser that visits a page on your site is provided with a unique ID via the __utmacookie. In this way, subsequent visits to your website via the same browser are recorded as belonging to the same (unique) visitor. Thus, if a person interacted with your website using both Firefox and Internet Explorer, the Analytics reports would track this activity under two unique visitors. Similarly if the same browser were used by two different visitors, but with a separate computer account for each, the activity would be recorded under two unique visitor IDs. On the other hand, if the browser happens to be used by two different people sharing the same computer account, one unique visitor ID is recorded, even though two unique individuals accessed the site.
Tracking traffic sources & navigation
When visitors reach your site via a search engine result, a direct link, or an ad that links to your page, Google Analytics stores the type of referral information in a cookie. The parameters in the cookie value string are parsed and sent in the GIF Request (in the utmccvariable). The expiration date for the cookie is set as 6 months into the future. This cookie gets updated with each subsequent page view to your site; thus it is used to determine visitor navigation within your site.
You can define your own segments for reporting on your particular data. When you use the _setCustomVar() method in your tracking code to define custom variables, Google Analytics uses this cookie to track and report on that information. In a typical use case, you might use this method to segment your website visitors by a custom demographic that they select on your website (income, age range, product preferences).
You can use Google Analytics with Google Website Optimizer (GWO), which is a tool that helps determine the most effective design for your site. When a website optimizer script executes on your page, a _utmx cookie is written to the browser and its value is sent to Google Analytics. See the Website Optimizer Help Center for more information.
Once the cookies are set/updated on the web browser, the data they contain that is required for reporting purposes is sent to the Analytics servers in the GIF Request URL via the utmccparameter.
Cookies set by Google Analytics
Google Analytics sets the following cookies as described below. A default configuration and use of Google Analytics sets only the first 4 cookies.
This cookie is typically written to the browser upon the first visit to your site from that web browser. If the cookie has been deleted by the browser operator, and the browser subsequently visits your site, a new __utma cookie is written with a different unique ID. This cookie is used to determine unique visitors to your site and it is updated with each page view. Additionally, this cookie is provided with a unique ID that Google Analytics uses to ensure both the validity and accessibility of the cookie as an extra security measure.
This cookie is used to establish and continue a user session with your site. When a user views a page on your site, the Google Analytics code attempts to update this cookie. If it does not find the cookie, a new one is written and a new session is established. Each time a user visits a different page on your site, this cookie is updated to expire in 30 minutes, thus continuing a single session for as long as user activity continues within 30-minute intervals. This cookie expires when a user pauses on a page on your site for longer than 30 minutes. You can modify the default length of a user session with the _setSessionCookieTimeout() method.
This cookie is no longer used by the ga.js tracking code to determine session status.Historically, this cookie operated in conjunction with the __utmb cookie to determine whether or not to establish a new session for the user. For backwards compatibility purposes with sites still using the urchin.js tracking code, this cookie will continue to be written and will expire when the user exits the browser. However, if you are debugging your site tracking and you use the ga.js tracking code, you should not interpret the existence of this cookie in relation to a new or expired session.
This cookie stores the type of referral used by the visitor to reach your site, whether via a direct method, a referring link, a website search, or a campaign such as an ad or an email link. It is used to calculate search engine traffic, ad campaigns and page navigation within your own site. The cookie is updated with each page view to your site.
This cookie is not normally present in a default configuration of the tracking code. The __utmv cookie passes the information provided via the_setVar()method, which you use to create a custom user segment. This string is then passed to the Analytics servers in the GIF request URL via the utmcc parameter. This cookie is only written if you have added the _setVar() method for the tracking code on your website page.
This cookie is used by Website Optimizer and only set when the Website Optimizer tracking code is installed and correctly configured for your pages. When the optimizer script executes, this cookie stores the variation this visitor is assigned to for each experiment, so the visitor has a consistent experience on your site. See the Website Optimizer Help Center for more information.
For further information about the Cookies Google uses please visit this Cookie Information page.
- Third Party Applications
Because we use external content on our site, particularly on our blog page, from sites such as YouTube and Twitter, you may find cookies collecting information on their behalf.
We do not have any control the setting of these cookies and would advise that you visit the sites below to find out more about their cookie usage if you are interested:
What can I do about cookies?
Your web browser allows you to control cookie acceptance. You can choose whether to accept or decline cookies. Most web browsers automatically accept cookies, but you can typically modify your browser settings to decline cookies if you prefer.
Please be aware that doing this may result in your user experience on our website being impinged upon and you not experiencing all the features on our site.