Privacy policy

Who is responsible

Pro Travel Net is operated by Ashers Hub Limited, company number 17204476, registered in England and Wales, 23 Kenilworth Road, London, W5 5PA, United Kingdom. For the purposes of the UK General Data Protection Regulation and the Data Protection Act 2018, Ashers Hub Limited is the controller of whatever personal data this site touches, which is very little. You can reach us at info@protravelnet.com.

This policy is written in plain words by the people who built the site. Every statement in it is a statement about how the site works today. If the site starts doing something new, this page changes first.

What this site is

A journey planner and referral service. You type two places and a date; we show the ways between them, with typical times, changes, approximate emissions and fare bands. There are no accounts, no logins, no profiles and no purchases on this site, and there will be none in this first year. When a leg can be booked, we hand you to the operator or to an authorised seller on their own site, and the booking and the payment happen there under their terms and their privacy policy.

A plan is a link, nothing more. Everything a plan page needs is in its address: the two places, the date and the version of the network that answered. Opening the link again recomputes the plan. We do not keep a copy of your plan on our servers and we cannot tell who opened one.

What we process, and why

We keep this list short because the list is short. Nothing on it identifies you, and nothing on it is joined to anything else that could.

• The places and date you search for. They are in the address of the plan page and are used to answer your search. When the site cannot answer a search, we count the pair that was asked for, because that is where the network should grow next. The record is the two places as you typed them, cleaned of anything that looks like an email address, a phone number or a long number, what they matched in our registry if anything, why the answer fell short, the language of the page and the hour of the request, rounded to the hour. It holds no IP address, no browser fingerprint, no device identifier and no session identifier of any kind. A pair is named in a report only once it has been asked for at least five times in the period; below that it is folded into an unnamed total, so no line of the report can describe one person. We rely on our legitimate interest in seeing which routes people ask for that we do not yet cover (UK GDPR Article 6(1)(f)).
• Handover events. When you choose to continue to an operator or a seller, we record that a handover happened, for which leg and in which hour, so that we can see which legs people act on and reconcile any referral commission. The record is the leg, the seller and the hour, rounded to the hour, and it is counted under the same rule of five. It holds nothing about you and it is never joined to a search.
• Instrumentation. To keep the site working we count events such as a plan being shown, an error being returned or a page being slow, again by hour and again with no identifier. These are counts of things that happened, not records of people.
• A saved plan on your own device. If you ask the site to keep a plan for later, it is written to your browser’s local storage on your device and nowhere else. It never leaves your device, we cannot read it, and clearing your browser’s site data removes it.
• A correction you send us. Every leg has a link for telling us a figure is wrong. When you use it, we store the message you typed and the reference of the leg you were looking at, meaning the leg, the network row it was built from and the source record behind it, together with the kind of correction you chose, the language of the page and the hour it arrived, rounded to the hour. Before the message is stored, anything in it that looks like an email address, a phone number or a long number is blanked. We do not ask for your name or address and we do not record where the report came from. Please do not write personal details in the message; if some get through, we will remove them when we read it. We rely on our legitimate interest in keeping the network right.
• Technical data that any web server records. Our hosting provider keeps ordinary server logs, which include the address your request came from, the page requested and the time. The provider keeps them for a short period for security and to run the service, and we do not use them to work out who anyone is. We rely on our legitimate interest in running a secure website.
• What you send us by email. If you write to info@protravelnet.com, we keep the correspondence for as long as needed to deal with it. We rely on our legitimate interest in answering you.

The waiting list (coming soon)

We are preparing a waiting list for people who want to hear when the full service opens. It is not live yet. This section is published ahead of it so that, as promised above, this page changes before the site does; nothing in it applies until the form appears on the site. When it does, this is what it will do.

Joining is a tick box and an email address, nothing more. We rely on your consent (UK GDPR Article 6(1)(a)) and, because the messages are marketing sent by email, on your consent under regulation 22 of the Privacy and Electronic Communications Regulations 2003 (PECR). You give it by ticking the box, which is never ticked for you, and the words you agree to are shown beside it.

We will use your address for one thing: one message when the service opens and, until then, at most one update a month on how it is going. No other message, no other purpose, and never passed to anyone else for theirs. Joining the list does not create an account and does not promise you anything; it is a way of being told.

The list is held for us by Supabase, a database provider, in a European Union region, under a data processing agreement. Their privacy policy is at https://supabase.com/privacy. They store the list; they do not use it.

Your address is deleted when you unsubscribe and in any case no later than twelve months after the service opens. Every message carries an unsubscribe link, and you can also write to info@protravelnet.com and we will remove you by hand. Withdrawing consent stops the messages; it does not undo anything done while it stood. Your other rights, listed below, apply to the list as they apply to everything else.

In full, this is what we hold for each person on the list:

• your email address;
• the language of the page you joined from;
• the time you joined;
• the version of the consent text you agreed to, so that we can show you exactly what you were asked;
• a one way hash of the address your request came from, kept for seven days only and used only to stop one machine from filling the list with addresses that are not its own. The address itself is never stored, and after seven days the hash is deleted.

Usage events (coming soon)

Alongside the waiting list we are preparing a plain count of how the planner is used, so that we can see which routes matter and whether the handover links are of any use. It is not live yet either. When it is, this is what it will count.

An event is a route that was searched (the two places), whether a date searched for and an arrival deadline were given, the language of the page, how many ways came back, and whether a link on the plan was clicked or the plan was exported. There is no user name, no email address, no account, no IP address, no hash of an IP address, no cookie and no user agent, and nothing else that says who searched. The address your request came from is not stored against a usage event in any form, not even for a moment.

We rely on our legitimate interest (UK GDPR Article 6(1)(f)) in understanding what the site is asked for and whether it helps. We have weighed that interest against the effect on you: the count holds nothing that identifies you, no address and no hash of an address is kept beside it, the effect on your privacy is minimal, and it is what anyone would expect a journey planner to count. Our interest is real and the intrusion is slight, so we consider the balance falls in favour of counting. You can object at any time by writing to info@protravelnet.com.

Because an event holds no personal data, there is nothing in it that could be found and deleted for you. The events are kept as totals of what the network was asked for, and a report made from them names a route only once five or more searches for it exist.

Correction reports

Every leg on a plan carries a link that says this does not look right. It opens a form with no account behind it: what kind of thing is wrong, what the operator actually says, and, if you want an answer, an email address. The report goes into a table we read by hand, and a person decides every one of them.

The message is about a timetable and not about you. Before it is stored, anything in it shaped like an email address or a long number is replaced, so a name or a telephone number typed into it by habit is not kept. Please do not put anything about yourself in the message: the field below it is there for that.

We rely on our legitimate interest (UK GDPR Article 6(1)(f)) in keeping the network true, which is the whole purpose of this site, and we have weighed that interest against the effect on you: a report holds what you typed about a route and nothing that identifies you. The email address is different. It is never required, it is stored only when you type it and tick the box beside it, and there we rely on your consent (UK GDPR Article 6(1)(a)). We use it for one thing, answering that report, and for nothing else; it is never added to the waiting list or to any other list.

A report is held for us by Supabase in a European Union region under a data processing agreement, like the waiting list. A report may become a correction on the site: the figure changes, the network version changes, and the page shows the new date its source was verified. The correction is published; your report is not, and neither is your address.

In full, this is what we hold for each report:

• what kind of thing you said is wrong, and the message you typed, cleaned as described above;
• the two places and the mode of travel the leg you were looking at runs on;
• the version of the network you saw, so we can read the report against the table as it was;
• the language of the page you sent it from, and the time you sent it;
• your email address, only when you typed one and ticked the box beside it;
• a one way hash of the address your request came from, kept for seven days only and used only to stop one machine from filling the queue. The address itself is never stored, and after seven days the hash is deleted.

What we do not do

• We do not have accounts or logins, and we do not store your name, phone number, payment details or travel documents. We have nowhere to put them. The one email address we will ever hold is the one you give us for the waiting list, described above, and only for as long as you want to be on it.
• We do not set cookies of our own beyond those strictly necessary for a page to work, and we set no advertising, analytics or tracking cookies at all. No third party is allowed to set a cookie through our pages.
• We do not record your IP address, your browser fingerprint or any identifier against a search, a handover or a correction. The waiting list keeps a one way hash of the address for seven days to stop abuse, and nothing more; the usage events described above keep no address and no hash of one at all. Our own counts are kept at hour precision and are only used once five or more of the same kind exist.
• When you continue to an operator or a seller, the link carries the journey only: the places, the date if you gave one, and an identifier that tells the seller the referral came from this site. It never carries anything about you. The seller learns who you are only if you tell them on their site.
• We do not sell, rent or share personal data with anyone for their own purposes, and we do not build profiles of anyone.
• We do not link a saved plan on your device, a correction you send or a search you make to each other or to you.

Who else sees data

Our hosting and deployment provider serves the site and keeps its server logs, from data centres that may be outside the United Kingdom. It does so under a data processing agreement and, for any transfer outside the UK, under the safeguards the UK GDPR provides for. It has no access to a saved plan on your device, because we do not have one either.

The operator or seller you continue to is an independent controller of whatever you give them on their site, and their privacy policy applies from the moment you arrive there. They do not receive anything about you from us.

When the waiting list opens, Supabase will hold it for us as a processor in a European Union region, under a data processing agreement, and will do nothing with it but store it. Their privacy policy is at https://supabase.com/privacy.

Some legs are handed over through a referral programme rather than straight to the operator's own address. Where that happens the step passes through the programme's address first, and the programme, not we, may set a cookie there to attribute the referral; nothing is set on our pages. The programme set up for this site is Travelpayouts, https://www.travelpayouts.com, whose privacy policy is at https://www.travelpayouts.com/privacy. It receives the journey and the referral identifier described above, and nothing about you. Where no programme applies, the step goes to the operator's own address directly.

Nobody else. We have no analytics vendor and no data brokers, and nobody buys placement on this site: a referral programme is paid a commission after you have chosen, and it buys nothing. The order of the options is journey time, always.

How long we keep things

Demand counts, handover counts and instrumentation counts hold no personal data and are kept indefinitely as the record of what the network was asked for. A correction report, meaning the message you typed and the leg it names, is kept for twelve months from the day it was sent and is then deleted, whether or not the network was changed because of it. An email address left on a report is deleted with that report, and sooner once the report is answered and closed. The hash kept against a report for abuse protection is deleted after seven days, as it is on the waiting list. Server logs are kept by our hosting provider for a short period for security and are then deleted or anonymised. Email correspondence is kept for as long as it is needed to deal with and then deleted. A saved plan on your device stays until you clear it; we cannot delete it for you because we cannot see it.

When the waiting list opens, an address on it is kept until you unsubscribe and in any case no more than twelve months after the service opens, and the hash kept against it for abuse protection is deleted after seven days. That deletion runs whenever somebody joins and again every week whether or not anybody does, so it never waits for traffic. The usage events described above hold no personal data at all, so nothing in them is kept against a person; they are kept as totals of what the network was asked for.

Your rights

Under the UK GDPR you have the right to ask what personal data we hold about you, to have it corrected or erased, to object to or restrict its processing, and to receive it in a portable form where that applies. Because this site holds no accounts and no identifiers, we will usually be unable to find anything that is about you, and we will tell you so honestly rather than guess. If you sent a correction that contains personal details and want it removed, tell us roughly when you sent it and which leg it concerned and we will find it and delete it. Write to info@protravelnet.com.

You also have the right to complain to the Information Commissioner’s Office at ico.org.uk. If you are in the European Union, the EU GDPR gives you the same rights and you may complain to your local supervisory authority.

Changes

This policy was last updated on 13 September 2026. It describes the first year of the site: no accounts, counts at hour precision, a correction box that keeps only the message and the leg, and, when they open, a waiting list you join by consent and a plain count of usage events, both described above. If any of that changes, this page will say so before the site does. Where this policy is offered in another language, the English text is the one that counts.