Skip to the content


What data is collected by Newham Patient View?


Cookies enable us to identify your device or when you have logged in. We use cookies to enable us to store your preferences and to provide analytics. You are able to turn off cookies at any point although you will lose some functions of the Newham Patient View website.

Personal Information

By agreeing to these terms and conditions, you consent to Newham Patient View storing any information provided in subsequent feedback pages. This may include your name, post code, contact information as well as any information you provide on recent healthcare experiences.

Newham Patient View collects this information to help improve health and social care services in Newham. Newham Patient View may share anonymised feedback to Newham CCG to help with decision-making about how services are run in your area. 

Analytical/Performance Cookies

We use the following analytical/performance cookies:

Name Domain Purpose
__cfduid The '__cfduid' cookie is set by the CloudFlare service to identify trusted web traffic. It does not correspond to any user id in the web application, nor does the cookie store any personally identifiable information.

Functionality Cookies

We use the following functionality cookies

Name Domain Purpose

This is an anti forgery token (prevent CSRF attack). It guarantees that the poster is the one who gets the form.

It prevents from anybody to forge a link and have it activated by a powered user.

cookies_accepted This cookie is placed if you click the Allow button to accept our cookies. It tells us you have given your consent to the use of cookies on our site.
yourAuthCookie This is  used to keep you logged in once you have logged in. This cookie is essential to the functionality of the site.
ASP.NET_SessionId When a user browses the website, a unique session ID will be associated with the user to keep track of any information that is stored for that session. This information is stored on the Web Server (known as storing information in session) and is identified via a GUID. The GUID is stored in the Cookie (known as the ASP.NET_SessionID) and is essential for any ASP.NET website to function correctly. If nothing is put in the session however, no cookie will be sent to the browser so this cookie will only be created when it is needed.