Cookie Policy

JourneyCheck uses Cookies to provide some of the enhanced features available to users as well as to support some of the central functions of the website. We will not store any cookies other than ones strictly required by the website in order to function, unless you accept them here. Further information is available on our
Cookies Policy Page.

Privacy Policy

< Back to JourneyCheck

This Privacy Policy refers to information that Nexus Alpha Limited obtains about you and the use we make of it in the course of our business. 

Nexus Alpha Limited and Nexus Alpha Low Power Systems comply with the Data Protection Act 1998 (as amended or updated from time to time) as a data controller or data processor (as relevant) in respect of personal data that we use in the provision of services and services to clients.

With the exception of visits web logs (which we use only for analysis and to guide development, and Cookies (please see our Cookie Policy), the only service that we provide that involves capturing personal records (most of which are needed to operate the service), is JourneyCheck Alerts.

JourneyCheck Alerts is an alerting service that we provide to our clients, who then provide the service to their customers (i.e. the travelling public and their season ticket holders).

This is an optional service and users visiting our client's web sites can register to receive email or in some cases, additionally SMS Alerts. This service is described in detail here.

In order to generate alerts, we store information about when the subscriber to the service is likely to travel. The system does not "know" of course if the user is actually travelling on the service, and in most cases a time range of travel is supplied. Any live disruption at the time of travel is then processed, and a personalised output generated.

Our client may also send "broadcast" messages to groups of users to warn them of forthcoming disruption, or to apologise for previous disruption. Thus, the heart of the system is fully automated, but manual intervention by our clients also takes place. Nexus Alpha do not send broadcast messages to clients registering for JourneyCheck Alerts unless instructed to do so by our clients.

JourneyCheck Alerts can also capture marketing questions proposed by our clients (this is a configuration option of the service). Mostly these questions are optional, but in some cases they may be a prerequisite for the provision of the service.

Nexus Alpha and Nexus Alpha Low Power Systems make no use of the contact details in the registration data or the marketing information themselves. This data is "owned" by our clients, - the transport operators as it is their service that you are registering to. Nexus Alpha merely licences them the software to facilitate this service, and holds user data on their behalf. There are questions during registration that determine whether or not those registering are prepared for the transport operator to make use of this marketing data. Our clients are bound by these conditions.

Records or those registering are kept indefinitely.

The other set of JourneyCheck Alerts data that is held is the actual messages sent out which contain details of the disruption that was occurring at the time the registered users asked to be informed.

These are retained in order to support and improve the service and in order to analyse the amount of service disruption that has occurred. This data is retained for as long as necessary for this purpose. 

Nexus Alpha Limited shares none of this information with any third parties apart from the client to whom the specific instance of the service is being provided (the transport operator) to whom the users signed up with.

All personal details recorded can be amended by the registered user on JourneyCheck Alerts by logging into the system. If the password has been forgotten, this can be requested by entering the email address associated with the account into the JourneyCheck service. If there are still any issues, please initially use the Contact details provided by the transport operator you have signed up with - they are the first point of contact. Alternately, you can always Contact our Support Department directly.

If there is any issue or potential dispute associated with the use of the systems, or you have any questions, please contact us using the email form found here.

Cookie Policy
< Back to JourneyCheck
You are using cookies. Press here to decline them.
You are not using cookies. Press here to accept them.

We use cookies across our site to help improve its performance, to enhance the user experience and to support some key site functionality. Which cookies we use, and what we use them for is detailed below.

Cookies are small text files that are stored on your computer by websites you visit. They allow the website to do things such as keep track of your preferences as you move around the site so that we can personalise pages for you and store little bits of information about your visit so these can be stored for your future visits. Cookies stay on your computer for varying amounts of time depending on their type and the parameters the website sets whilst creating them.

Third Party Cookies

Third party cookies are not set by the website you are visiting. They are set by a different organisation whose features are being used by the website you are visiting. This is common practice if sites use analytical systems supplied by a third party (as most are) to track the usage and load on their website. These may also be created by embedded content in the web page, a YouTube video for instance, as these need their own cookies to work. This website may use cookies specified by the Train Operating Company. These can be removed at any time by amending your cookie preferences.

Cookies Key:

Cookies come in three different categories. The cookies themselves vary very little between the types but their effect and use is different.

  1. Strictly necessary - for the operation of the site.
  2. Functional - allow the website to remember choices that customers make and provide enhanced functionality and personal features.
  3. Performance - to help to improve the performance of c2c JourneyCheck.
Cookies in JourneyCheck
Cookie Name Product Purpose Category
JSESSIONID JourneyCheck This cookie is the default one used by used by our web server to identify your session with the server allowing it to link one page request with the next and therefore to keep track of your preferences and selections as you move through the site. Strictly Necessary
c2c_userid JourneyCheck This cookie is used in JourneyCheck Alerts to record the logged in user when they select the "Remember Me" option. Functional
c2c_cookie_accept JourneyCheck This cookie is used by our web server to track that user has acknowledged the cookies usage on this website. Functional
CCrecent* JourneyCheck This cookie is used by our web server to record the Journey searches made by the user. There can be multiple instants of this cookie which is TOC configured. It is store as CCrecent+FromCRSCode+toCRSCode. Functional
_utma Google Analytics We use Google Analytics to collect anonymous usage statistics for this website to allow us to monitor trends and loadings. These cookies are used by Google Analytics to help perform this function. Further details on Google Analytics and the cookies it sets is available here. Performance
_utmb Google Analytics Performance
_utmc Google Analytics Performance
_utmt Google Analytics Performance
_utmz Google Analytics Performance
_ga Google Analytics Performance
Disabling Cookies

Each browser has settings which allow you to elect not to allow websites to store cookies on your machine. As each browser is a little different, we advise you to check your browsers help functionality for this option or search for instructions that are specific to your browser.

If you choose to disable cookies, some aspects of this website may not function as intended.