Privacy information for London Stay Hub.

What information is processed?

When you use Find My Neighbourhood, we process your selected answers, recommendation and refinement results, feedback you choose to send, journey references, relevant version information and timestamps. Feedback can include an optional written comment. Please do not include your name, contact details or sensitive information in that field.

The service does not require you to create an account or provide your name, email address or payment details. Although journeys are not associated with named accounts, journey references and related information may constitute pseudonymous personal data.

Why we process this information

We use interview answers to generate personalised neighbourhood recommendations and comparisons, retain a journey temporarily so you can return to it, receive voluntary feedback, protect the service and investigate operational problems. Recommendation selection is automated, but it provides travel-planning suggestions rather than decisions with legal or similarly significant effects.

Our lawful basis for providing recommendations, temporary journey restoration, protecting and maintaining the service, voluntary feedback, domain-level website traffic statistics and responding to ordinary enquiries is legitimate interests under Article 6(1)(f) GDPR. These interests are to provide a useful travel-planning service, maintain its security and reliability, and understand whether it works well. Where we process information to comply with an applicable legal obligation, such as handling certain GDPR rights requests, Article 6(1)(c) may apply.

Browser storage

Your browser stores a journey reference, access credential and local question history so the service can restore your answers. The server stores a hash of the journey access credential rather than the credential itself. This storage supports the service you request; it is not used as a cross-site advertising identifier.

Website analytics and error monitoring

Cloudflare Web Analytics (the JavaScript-based Real User Measurements service) is currently disabled. Cloudflare continues to provide domain-level traffic statistics from requests handled by its network, such as visits, pageviews, traffic sources and general technical information. These domain-level statistics do not require a Web Analytics browser beacon. We do not currently use advertising cookies or third-party behavioural advertising trackers. Sentry is used for technical error monitoring, with its data region configured in Germany and the Free plan in use. Diagnostic events may include technical context, and infrastructure request logs can contain pseudonymous journey identifiers. We do not intentionally send full interview answer histories, journey credentials or feedback text to analytics services.

How long information is retained

• Unfinished journeys: ordinarily deleted after 30 days of inactivity.
• Completed journeys: ordinarily retained for restoration for 90 days after last activity.
• Feedback-linked journeys: after 90 days of inactivity, detailed answers and recommendation history are minimised; limited structured feedback may be retained for up to 365 days after the journey’s last activity.
• Optional free-text feedback: removed during the 90-day minimisation step.
• Production database backups: held privately in Cloudflare R2 under a 14-day expiry policy; deletion from the active database does not immediately remove older backup copies.
• Railway platform logs: ordinarily retained for 7 days on our Hobby plan. Sentry error events: ordinarily retained for 30 days on its Developer plan. Other provider-internal records may have different retention periods.

Providers and data locations

The website uses Cloudflare Pages and Cloudflare’s domain-level traffic analytics. Cloudflare Web Analytics (RUM) is disabled. The application API and PostgreSQL database use Railway services deployed in Amsterdam; the scheduled database backup worker is also deployed in Amsterdam. Private backups are stored in a Cloudflare R2 bucket with Western Europe (WEUR) location. Sentry error monitoring is configured for Germany, and Zoho Mail handles correspondence sent to our project contact address.

These regional settings do not mean that all processing or support access occurs exclusively within the European Economic Area. Where providers process data outside the EEA, relevant safeguards may include adequacy decisions or contractual protections such as the EU Standard Contractual Clauses. We are completing the account-specific verification of these arrangements. Contact us if you would like information about the safeguards relevant to your data.

Deletion and your rights

If your browser still holds your journey credential, you can delete the saved journey through Find My Neighbourhood. This removes its linked records from the active application database, while any existing recovery backups expire under their separate schedule. After the restoration period, the remaining minimised feedback record is intended to remain deletable using the original credential until its final expiry.

Depending on the circumstances, GDPR rights may include access, rectification, erasure, restriction, portability and objection. Contact [email protected] to make a request. Because journeys do not require identity details, we may need the relevant journey reference or credential to locate a particular record, and we will not demand unnecessary identity information. You may also complain to an appropriate supervisory authority, including the Spanish Data Protection Agency (AEPD).

Email enquiries

We use Zoho Mail to respond to enquiries sent to our contact address. Ordinary correspondence is reviewed periodically and is ordinarily deleted within 12 months of the last meaningful exchange once no longer needed. We may keep it longer when an ongoing matter, legal obligation or dispute requires this. Records of formal privacy rights requests are handled separately.

Contact

For privacy questions or requests, email [email protected].