Privacy on Travel247

Travel247 is a static reference site. It does not ask readers to create an account, does not run a subscriber area and does not sell anything directly from the site. That limits what personal data is handled in the ordinary course of a visit.

The two situations in which personal information may be received are straightforward: when someone writes to the site by email, and when the web server keeps ordinary access logs needed to run and secure the service.

If you email Travel247, the site receives the information you choose to send: typically your email address, your message and any detail needed to answer it. If you report a correction, that may include information about a venue, route or page that needs to be checked.

Like any web service, the server may also record technical information such as IP address, requested URL, user agent, referrer and the time of the request. This is used for delivery, troubleshooting, abuse prevention and basic operational monitoring.

Travel247 does not provide a comment system, user profiles or an upload area, so it does not collect the categories of personal data those features would normally create.

The site does not sell personal data, does not run behaviour-based advertising and does not build reader profiles for resale or targeting. It is a reference publication, not an ad-tech product.

Messages sent to the site are used to answer the message itself, to verify a correction or to assess a commercial enquiry. They are not used to subscribe someone to a mailing list, because the site does not run one.

If a correction turns out to be valid and generally useful, the result may appear on the relevant page in updated form, but private details from the sender are not published as a matter of course.

Privacy questions can be sent to [email protected]. If you are asking about a specific message or correction, include enough detail to let it be identified.

This page describes the site as built on 28 August 2026. If the operating model changes materially, the page should be revised with it.