Cookie policy

Cookie Policy

Cookies are small text files that are placed on your computer, smartphone or other device when you visit our Service Directories. A cookie file is stored on your device and allows us, or our third party service providers (see below) to recognise you and make your visit easier and more useful to you when you revisit our Service Directories.

The following lists the cookies used on our Service Directories:

i. XSRF-TOKEN: a token (a string) that is generated by the application platform (Laravel) for each active user session, that is used to verify that the authenticated user is the one actually making the requests to the application and makes it easier to protect the application from Cross-site request forgery (CSRF);

ii. ga, gat, gid: Google Analytics generated cookies are used to gather information allowing us to understand your interactions with our sites and improve your experience. For more information about the use of Google Analytics and how it collects and processes data, please see “How Google uses information from sites or apps that use our services”.

iii. font-preference: used to store your preference of font-size;

iv. cookie-accepted: cookie that checks whether you accept the cookie notice;

v. laravel_session: cookie generated by the application to identify a session instance for a user; and

vi. subdomain: cookie that stores value of which Service Directory is browsed, either Birmingham or Surrey, that will allow the application to return the correct information for each directory.

These cookies help us understand if you have visited our Service Directories before, the time you visited the site and the pages you looked at. If you choose to block cookies you will not be able to use all the features on our Service Directories. Certain cookies are required in order for the Service Directories to work properly. These are XSRF-TOKEN, Laravel session and Subdomain.

For more information about cookies, including how to view the cookies that have been set and how to manage or delete them, please visit