Friends of Cardigan Bay Smugmug videos and photos

 

Download Newsletter

Privacy and Cookie Policy

PRIVACY POLICY

Friends of Cardigan Bay is committed to your privacy we do not gather or store your personal information without your knowledge. We use a third party website Paypal to gather payment and membership details.

We apply the Data Protection Act 1998 when handling any personal information. When we ask you for personal information we will keep to the law, and promise to:

  • make sure you know why we need it
  • only ask for what we need, and not to collect too much or irrelevant information
  • protect it and make sure nobody has access to it who shouldn’t
  • make sure we don’t keep it longer than necessary
  • not make your personal information available for commercial use without your permission.

 

COOKIES

Cookies are small files that help add to the functionality of web sites, and allows site owners to better understand the behaviour of users on a web site. This web site uses a few cookies to compile usage statistics through a third party site google analytics. This information stored does not contain any personal information - it is anonymous and generalised. We will never sell this information.

DELETING AND BLOCKING COOKIES

If you wish to restrict or block the cookies which are set by websites you can do this through your browser settings. The Help function within your browser should tell you how.

 

Cookies & Google Analytics

An HTTP cookie—commonly referred to as just "cookie"—is a parcel of text sent back and forth between a web browser and the server it accesses. Its original purpose was to provide a state management mechanism between a web browser and a web server. Without a cookie (or a similar solution), a web server cannot distinguish between different users, or determine any relationship between sequential page visits made by the same user. For this reason, cookies are used to differentiate one user from another and to pass information from page to page during a single user's website session. A web server uses cookies to collect data about a given browser, along with the information requested and sent by the browser's operator (the visitor). Cookies do not identify people, but rather they are defined themselves by a combination of a computer, a user account, and a browser.

Google Analytics tracking (and most web tracking software) uses cookies in order to provide meaningful reports about your site visitors. However, Google Analytics cookies do not collect personal data about your website visitors.

 

How Google Analytics Uses Cookies

Google Analytics uses cookies to define user sessions, as well as to provide a number of key features in the Google Analytics reports. Google Analytics sets or updates cookies only to collect data required for the reports. Additionally, Google Analytics uses only first-party cookies. This means that all cookies set by Google Analytics for your domain send data only to the servers for your domain. This effectively makes Google Analytics cookies the personal property of your website domain, and the data cannot be altered or retrieved by any service on another domain.

The following table lists the type of information that is obtained via your Google Analytics cookies and used in Analytics reports.

FunctionalityDescription of CookieCookie Used
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 Cookies
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.

__utmb
__utmc
Identifying Unique Visitors Each unique browser that visits a page on your site is provided with a unique ID via the __utma cookie. 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. __utma
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. __utmz
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). ___utmv
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. ___utmx

 

 

 

 

Friends of Cardigan Bay Facebook