Information about our Organisation and Website
Modern information and communication technologies play a fundamental role in the activities of an organisation like Alpha Laboratories Ltd. We are based in England.
Organisation Name: Alpha Laboratories Ltd
Address: 40 Parham Drive
City, Postcode: Eastleigh , SO50 4NU
Controller: Alpha Laboratories Ltd
Websites(s): https://www.alphalabs.co.uk/ also https://www.pasteur-pipette.com
Providing Visitors with Anonymous Access
You can access our Website home page and browse our site without disclosing your personal data.
The services and links of our Website
Our Website does not enable our visitors to communicate with other visitors or to post information to be accessed by others. Our Website does not include links to third party Web service providers.
Automatic Collection of Information
We do not automatically log personal data nor do we link information automatically logged by other means with personal data about specific individuals.
Data Collection and Purpose Specification
We collect the personal data that you may volunteer while using our services.
We do not collect information about our visitors from other sources, such as public records or bodies, or private organisations.
We do not collect or use personal data for any purpose other than that indicated in the table below.
If we wish to use your personal data for a new purpose, we offer you the means to consent to this new purpose: by indicating in a box at the point on the site where personal data is collected.
Disclosure and Visitor Choice
We do not disclose your personal data to our subsidiaries or other organisations.
Where we disclose your personal data for purposes which are different from those indicated in the table mentioned above, we offer you the opportunity to consent to disclosure.
Confidentiality / Security
We have implemented security policies, rules and technical measures to protect the personal data that we have under our control from:
Unauthorised access improper use or disclosure unauthorised modification unlawful destruction or accidental loss
All our employees and data processors, who have access to, and are associated with the processing of personal data, are obliged to respect the confidentiality of our visitors’ personal data.
We ensure that your personal data will not be disclosed to State institutions and authorities except if required by law or other regulation.
Access to the personal data we may hold about you
You can ask us, by:
sending an email (firstname.lastname@example.org)
whether we are keeping personal data about you.
Upon request, which you can indicate by:
sending an email (email@example.com)
We will provide you with a readable copy of the personal data which we keep about you, within a week. – although we may before require proof of your identity -. We will provide the information without any charge.
We allow you to challenge the data that we hold about you and, where appropriate, you may have the data:
erased rectified or amended completed
Alpha Laboratories Ltd
+44 (023) 80 483000
If you are not satisfied with our response to your concern:
you may wish to contact ICO ( http://www.ico.gov.uk/ )
The Cookies we use:
General website cookies
This website is built using WordPress, as part of that we use a number of cookies to manage your session and to make the website function correctly. When you navigate to the site, the server establishes a unique session that last for the duration of your visit.
Cookie notice acceptance
This site uses a cookie to remember your cookie consent. This expires after 6 months.
Measuring website usage – Google Analytics
The following table lists the type of information that is obtained via Google Analytics cookies and used in Analytics reports.
||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 setupis 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 & Directoriesin 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 Sessionarticle 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
__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 Centerfor 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 in the table below. A default configuration and use of Google Analytics sets only the first 4 cookies in the table.
||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.
||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.
||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.
||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.
||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 Centerfor more information.
||2 years from set/update.
For further information about the Cookies Google uses please visit this Cookie Information page.
Measuring website usage – DC Storm
DC Storm Cookies are used by this website to identify how users interact the website, so that they can see things like the most popular pages and the journey that users take though their site.
First Party cookies – These cookies are set by this website that you are visiting.
Cookies are also created to identify when a user has viewed an advert for this website on an external site.
The cookie contains a unique identifier and nothing else. If you subsequently visit this website, then we link that cookie (and hence the advert) to your visit, but if you never visit the website, the cookie is meaningless and will expire automatically, 90 days after you last saw one of the adverts.
First Party cookies Information
These cookies are written to track website usage of this site:
||Stores the history of traffic sources the user has arrived to the site by
||Stores information about the session
||Stores the visit definition – ts type, number of visits, expiry
||Stores a user identifier (only within a site)
||Unique sale ID
||Unique identifier for a click generating a landing
||Flags that the last page was secure and therefore has no referrer
||Stores the referrer details to avoid duplicate Landing events
||Flags whether the environment variables (screen size, browser etc) need to be collected again
For further information about the Cookies DC Storm uses please visit their Cookie Information page.
Other 3rd Party Cookies we may use
When you visit our website, you may notice some cookies that are collecting information for other websites. For example, if you visit a page that has video content, cookies from YouTube may be served. We do not control the setting of these cookies and we recommend you visit the third party websites for more information.
Please find a list of some third party cookies you may find present on this website and links to their specific cookie information:
Paid on Results
How do I Control or Delete Cookies?
If cookies are not enabled on your computer is could mean that your experience with our website will be impacted. However, if you want to control or delete cookies you can do so.
Information on deleting cookies or controlling cookies is available at www.aboutCookies.org. To reiterate though, by deleting our cookies or disabling future cookies you may not be able to access certain areas or features of our site