When you are on the Nevie-Pie Cakes website and are asked for personal information, you are sharing that information with Nevie-Pie Cakes alone unless stated otherwise. Nevie-Pie Cakes will not disclose any of your personally identifiable information. If you indicated that you are interested in receiving regular information about Nevie-Pie Cakes work we will send you communications regarding Nevie-Pie Cakes work and activities, either electronically or otherwise. In addition, we may send you direct mail that we feel may be of interest to you. Nevie-Pie Cakes does not sell, rent or share user information with anyone. The accuracy of your individual identifying information is important to Nevie-Pie Cakes. We are working on ways to make it easier for you to review and correct the information that Nevie-Pie Cakes maintains about you. In the meantime, if you change email address or any of the other information we hold is inaccurate or out of date, please email Natasha Collins, or write to us.
Nevie-Pie Cakes is committed to taking reasonable steps to protect the individual identifying information that you provide to us.
Unfortunately, no data transmission over the Internet can be guaranteed to be 100% secure. As a result, while we strive to protect your personal information, Nevie-Pie Cakes cannot ensure or warrant the security of any information you transmit to us, and you do so at your own risk. Once we receive your transmission, we make our best effort to ensure its security on our systems.
A cookie is a small file of letters and numbers that we store on your browser or the hard drive of your computer if you agree. Cookies contain information that is transferred to your computer’s hard drive.
The cookies we use are “analytical” cookies. They allow us to recognise and count the number of visitors and to see how visitors move around the site when they are using it. This helps us to improve the way our website works, for example, by ensuring that users are finding what they are looking for easily. You can find more information about the individual cookies we use and the purposes for which we use them in the table below:
The following table lists the type of information that is obtained via your 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 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.
|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.jstracking 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.
Source : Google Analytics
You block cookies by activating the setting on your browser that allows you to refuse the setting of all or some cookies.
However, if you use your browser settings to block all cookies (including essential cookies) you may not be able to access all or parts of our site.