Cookies

Our eStore uses cookies and will not work if you have them disabled. The system runs three cookies:

• Session: 'ASP.NET_SessionId'
• Forms authentication: '.ASPXAUTH'
• Cookies accepted: 'CookieAccepted'

We do not store personal information in cookies - we only store session identifiers and information used to maintain the client state. Doitonline will not work correctly if you have cookies disabled as they are needed to hold information you add on each page of the form.

Server generated cookies

• AWSELB - "Amazon Web Services Elastic Load Balancer" - Used to direct your request to the appropriate server. No personal information is contained or used.
• firmstep2server - Used to direct your request to the appropriate server. No personal information is stored.
• firmstep2session - A unique identifier given to you for the duration of your site visit. It is used to ensure that you and only you are shown information relevant to you. It contains no personally identifiable information, but is temporarily linked to your user account when you log in.
• ASP.NET_SessionId - A unique identifier given to you for the duration of your site visit. It is used to ensure that you and only you are shown information relevant to you. It contains no personally identifiable information, but is temporarily linked to your user account if you log in.

Cookies set by javascript

• 0.js:
• fs2logevents: Only set by explicit user action. Increases the level of internal debug information kept by the browser.
• fs2debug: Only set by explicit user action. Causes the display of a button to allow the user to submit browser debug information for diagnostics.
• fs2diag: Only set by explicit user action. Causes the display of a toolbar that can submit or display browser debug information.
• NoAJAT: Used to disable AJAX. Only appears in redundant code. No longer actually set/used.
• combined.js:
• ui-tabs: Used by the client to maintain tabs state when the user moves between pages.

For authenticated CMS users, a session cookie is used to keep the user logged in to the site. The session cookie contains simply a random alphanumeric string to identify the user, it does not contain user information. The session cookie is required strictly for correct operation of the website. Users will not be able to log in to the site if the cookie is blocked.

Trapeze do not use cookies, however, they do store information on your device in local storage which helps them give you personalised information: 

• a session ID so we can save recently accessed information for as long as you keep the website or app open
• an authentication token which identifies you by your email address. This also includes your authorisation level
• stops, services and journeys you have chosen as 'favourites'
• any journey options where you have changed the defaults, for example if you change your preferred walking speed or select the option which gives you journeys with fewer changes

Local storage values stored

Strictly necessary local storage values

Optional local storage values