A little information.
A clear purpose.

Who is responsible?

Travel Wide App is responsible for the waitlist information described here. For a privacy question, a copy or correction of your details, or to withdraw from the waitlist, use the contact email below.

What we collect and why

The waitlist asks for your email address. We store it with your registration time, signup source and beta status. For website signups we also record the wording and date of your request for beta emails. Joining does not create an app account, verify your email address or give immediate access to the app.

We use these details to manage the waiting list, avoid duplicate registrations, share progress towards beta and contact people with invitation information. Joining is optional. We rely on your consent for the beta emails you request and our legitimate interest in securing the service for the limited technical information used to prevent misuse.

Selecting “Join the beta” requests beta emails and the TravelWide newsletter with behind-the-scenes updates, travel inspiration and community news, as explained above the button. We record your choice, the wording shown and the time of your request. You can unsubscribe from the newsletter anytime without losing your beta place. We do not automatically subscribe previous beta-only registrations or override a recorded newsletter opt-out.

The waitlist count

This waitlist is capped at 250 registrations. The remaining-spaces number counts eligible existing CRM registrations as well as new website signups. Test records do not count, and submitting the same address again does not take another place.

A confirmed registration reserves your beta place. The beta is planned for later in 2026; access details will follow when it is ready. Joining does not give immediate app access, and no payment details are collected here.

Where information is handled

Waitlist details are stored in our private CRM using Supabase. The marketing site is hosted through Sites on Cloudflare infrastructure. These providers process the requests needed to host the website and save registrations. The public website can submit a signup and read the remaining count; it cannot read the CRM contact list or open TravelWide HQ.

Hosting and database providers may process technical information through infrastructure outside the UK. Their contractual data-protection terms describe the safeguards that apply. See Supabase’s data-processing terms, OpenAI’s data-processing terms and Cloudflare’s data-processing terms.

Resend delivers the automatic welcome email for new website registrations and the newsletters you subscribe to. It processes the recipient address, message and delivery information for that purpose, which may involve processing outside the UK. See Resend’s data-processing terms. We keep a private delivery record to avoid duplicate messages and retry temporary failures. A welcome email acknowledges the request; it does not verify ownership of the address. You can ask to leave using the contact route above.

Security, cookies and measurement

The signup service validates submissions, limits repeated attempts and keeps credentials on the server. For request limits, it uses a keyed identifier derived from technical request information. The signup database does not store your raw IP address for this purpose. Hosting providers may still process IP addresses and normal request logs to operate and protect their services.

Optional first-party analytics stay off unless you accept. With your consent, we count page views, clicks on our signup invitations and new signups, along with a broad device category, referring source and recognised campaign label. We use a random session identifier stored in your browser to group a visit; it expires after 30 minutes of inactivity. We do not copy your email address, raw IP address or complete referring URL into these analytics records, and we do not use advertising pixels or cross-site tracking.

We remember your analytics choice in the tw_measure cookie for six months. Change it using “Analytics choices” at the bottom of any marketing page. Declining or withdrawing consent does not affect signup or access to the website. We honour browser Global Privacy Control and Do Not Track signals. Withdrawing stops future measurement; it does not undo processing already carried out with consent. Your motion preference lasts only while the page is open. Essential hosting security and private HQ sign-in may use cookies. External websites have their own privacy practices.

Newsletter links may contain a campaign label shared by all recipients, so we can measure website visits from a newsletter when analytics is accepted. We do not enable individual email-open or email-click tracking. Resend reports delivery, bounce, complaint and unsubscribe events. We keep a limited private record of event type, message or contact identifier, campaign and time to check delivery, respect subscription choices and understand aggregate results. We rely on our legitimate interests in operating a reliable email service for these delivery records.

How long we keep details

We keep a waitlist record while it is needed to manage your beta place. Newsletter choices and consent records are kept while needed to manage your subscription, respect withdrawals and demonstrate the permission you gave. We use whether beta recruitment is still active, whether an invitation is still relevant and whether you have withdrawn your request to decide when the record should be removed. You can ask us to remove it at any time.

Website analytics events are removed after 90 days, delivery reporting events after 365 days, and analytics rate-limit records after one day, by a daily cleanup. Signup request-limit records older than one day are removed when a later valid signup request runs. Provider security logs and backups follow their own retention arrangements.

Your choices and rights

You can stop newsletter emails without giving up your beta place, or withdraw your request for beta emails and leave the waitlist. Reply to an email from us or use the contact email above to change your preferences. We will stop using your details for that purpose. Withdrawing consent does not affect processing that was lawful before withdrawal.

You can also ask for access to your information, correction, deletion, restriction or a portable copy where these rights apply. You have the right to object to processing based on legitimate interests. We may need to check that a request comes from the person concerned before disclosing or changing information.

If you are unhappy with how your information is handled, contact us first or raise a concern with the Information Commissioner’s Office. We do not use this waitlist for automated decisions with legal or similarly significant effects.