What are Cookies?
- Remembering settings, so you don’t have to keep re-entering them whenever you visit a new page
- Remembering information you’ve given (e.g. your ZIPCODE) so you don’t need to keep entering it
- Measuring how you use the website so we can make sure it meets your needs
The Cookies we use:
General website cookies
Measuring website usage – Google Analytics
Description of Cookie
|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.js tracking code to define content scope. See Domains & Directories in the Collection API document for details.||All Used|
|Determining Visitor Session||
The Google Analytics tracking for ga.js uses 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 customize 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
|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 utmcc variable). 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.||
|Custom Variables||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).||
|Website Optimizer||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.||
Cookies Set By Google Analytics
|__utma||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.||2 years from set/update.|
|__utmb||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.||30 minutes from set/update.|
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.
|__utmz||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.||6 months from set/update.|
|__utmv||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.||2 years from set/update.|
|__utmx||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.||2 years from set/update.|
Measuring website usage – DC Storm
First Party cookies Information
|_#srchist||Stores the history of traffic sources the user has arrived to the site by||1000 days|
|_#sess||Stores information about the session||1000 days|
|Stores the visit definition – ts type, number of visits, expiry||1000 days|
Stores a user identifier (only within a site)
Unique sale ID
|_#clkid||Unique identifier for a click generating a landing||1 year|
|_#lps||Flags that the last page was secure and therefore has no referrer||20 min|
|_#tsa||Stores the referrer details to avoid duplicate Landing events||10 min|
|_#env||Flags whether the environment variables (screen size, browser etc) need to be collected again||30 days|
Other 3rd Party Cookies we may use
How do I Control or Delete Cookies?
QGate Data Privacy Statement
- Describes the type of data that we collect;
- How we collect data and why;
- How data will be used and who we can disclose or transfer data to and why;
- How data can be corrected or deleted;
- The measures that we take to protect data; and
- The process and contact information that customers can use to raise enquiries, concerns and complaints.
TYPES OF DATA COLLECTED
- Personal Information
- Performance Data
COLLECTION OF PERSONAL INFORMATION
When you use our Products or Websites, you may be asked for personally identifiable information such as your name, address, email address, telephone number. By giving us such information, you will consent to us using it in the manner described in this policy.
You may withdraw your consent at any time by emailing us at email@example.com. We will return or destroy your personal information within five days of receipt of your withdrawal of consent.
Cookie information, pages you have requested and your IP address may also be recorded by us and/or third parties from your browser as set out in this policy.
USE OF PERSONAL INFORMATION
We use personal information to allow us to process your product requests, send out newsletters, personalise your visit to our Websites, personalize your use of our Products, and enable us to improve the products and services we offer. We may occasionally carry out market research and send you details of services and offers that we think may be of interest to you. If you do not wish to receive such information, please e-mail firstname.lastname@example.org or when we send you an e-mail, it will contain a provision for you to opt out of receiving any further information from us.
COLLECTION OF PERFORMANCE DATA
QGate will collect Performance Data, including performance and usage statistics, bug fixes and other similar data uploaded to our Websites or acquired through the use of our Products.
USE OF PERFORMANCE DATA
QGate may use Performance Data in any way, including, but not limited to, using, editing, altering, reproducing, publishing and/or distributing the Performance Data for any purpose including, but not limited to, commercial, billing, product improvement. QGate may use the statistical information for external marketing, but only where any personal data has been removed to prevent identification of the source.
DISCLOSURE OF PERSONAL INFORMATION
We may provide information about you to our employees and agents in order to administer any accounts, products and services provided to you by QGate.
Third-party advertisers may also create and access cookies, which will be subject to their privacy policies – we accept no responsibility or liability for the use of such third parties’ cookies. If you do not wish cookies to be placed on your PC or handheld device, then they can be disabled in your web browser. The option to do so is normally found in your browser’s “security settings” section. Please note that permanently disabling cookies in your browser may hinder your use of our Websites as well as other websites and interactive services.
All security on our Websites is treated seriously. Where applicable, we undertake security steps, including use of SSL technology, on our back-end systems that store customer account information and to protect data transmissions. However, this is not a guarantee that such data transmissions cannot be accessed, altered or deleted due to firewall or other security software failures.
If you have any further concerns about security, please email our Technical Service team at email@example.com.