Privacy Policy

    Last updated: October 9, 2026

    1. Introduction

    WeGoWhen ("we", "our", or "us") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, and safeguard your information when you use our Service.

    2. Information We Collect

    2.1 Information You Provide

    • Trip Information: Trip names, start dates, and end dates
    • Participant Information: Names you provide when joining trips
    • Availability Data: The dates you mark as available for trips
    • Feedback: If you use Report a bug or Suggest a feature, the message you write, the email address you give if you choose to give one, the page you sent it from, and your browser's user agent. Feedback is read only by the person who runs WeGoWhen, is never shown to other visitors, and the email is used only to reply to you

    2.2 Automatically Collected Information

    We run privacy-preserving analytics, and no advertising or cross-site tracking scripts of any kind. There are no third-party trackers, no advertising pixels, no profiles, and nothing that follows you to other websites.

    • Page Analytics: We use Cloudflare Web Analytics, which counts page views and records which website referred you, if any. It sets no cookies, uses no device fingerprinting, and does not track you across sites or sessions. We see aggregate counts, such as how many people opened a page and how many arrived from a given site. We cannot tell from it who you are or which trip you opened
    • Server Request Logs: Our host, Cloudflare, records standard request metadata such as your IP address and browser user agent in order to serve and protect the site. We do not query, export, or link this to your trips
    • How a Trip Was Started: When you create a trip, we store one of four labels with it: that you followed the Start your own trip link on another trip's page, that you followed a link from one of our long-weekend calendar pages, that your browser had opened someone else's trip before, or none of these. Your browser works it out from the link you followed and the list of trips described below. The label says nothing about who you are, and we use it only to count how often people who were invited to a trip go on to plan one of their own, and whether our calendar pages lead anyone to plan a trip
    • Local Storage: Your tutorial preference, the language you chose for the site (if you picked one), the list of trips you have opened in this browser (each trip's name, dates and link), and the name you last used to join a trip. This is held on your device and is never sent to us; only the single label above is derived from it

    3. How We Use Your Information

    We use the collected information to:

    • Provide and maintain the trip planning service
    • Coordinate availability between trip participants
    • Display group availability and suggest optimal dates

    4. Data Storage and Security

    All trip data is stored in Cloudflare D1, Cloudflare's managed SQL database, and is served from Cloudflare's network. We implement appropriate technical and organizational measures to protect your data against unauthorized access, alteration, disclosure, or destruction.

    However, no method of transmission over the Internet or electronic storage is 100% secure. While we strive to use commercially acceptable means to protect your data, we cannot guarantee its absolute security.

    5. Data Sharing

    We do not sell, trade, or rent your personal information to third parties. Your trip data is only visible to people who have the specific trip link. We may share information in the following circumstances:

    • With Trip Participants: Availability data is shared with others who access the same trip link
    • Link Previews: When a trip link is pasted into a messaging app or social network, that service fetches a preview of it. The preview shows the trip's date range, never its name or who has joined
    • Service Providers: We use Cloudflare to host the application and to store trip data
    • Legal Requirements: If required by law or to protect our rights

    6. Your Rights (GDPR)

    If you are in the European Economic Area (EEA), you have the following rights:

    • Access: Request access to your personal data
    • Rectification: Request correction of inaccurate data
    • Erasure: Request deletion of your data
    • Data Portability: Request transfer of your data
    • Object: Object to processing of your data

    How this works in practice: we hold no accounts, no email addresses and no way to identify you across trips, so a trip can only be identified by its link. You can exercise rectification and erasure yourself on any trip you have joined - the trip page lets you rename your entry, change the dates you marked, and withdraw entirely, which deletes your name and availability. For anything else, or to have a whole trip removed, see Contact and include the trip link.

    7. Cookies and Local Storage

    We use browser local storage to save your tutorial preferences, UI state, the language you picked for the site, and a list of the trips you have opened in this browser so you can find them again without the link. That list holds each trip's name, dates and link, and nothing about other participants. This data is stored only on your device and is not transmitted to our servers. You can remove an individual trip from the list on the home page, or clear all of it at any time through your browser settings.

    8. Third-Party Services

    Our Service uses the following third-party services:

    • Cloudflare: Application hosting (Cloudflare Pages), trip data storage (Cloudflare D1), and cookieless page analytics (Cloudflare Web Analytics) (Privacy Policy)

    9. Data Retention

    Trip data is retained indefinitely. There is no automatic expiry or archival: we do not currently delete inactive trips, and we would update this policy before starting to. You can remove your own name and availability from any trip at any time using Withdraw on that trip's page. To have an entire trip deleted, contact us with its link. Feedback is kept indefinitely as well.

    10. Changes to This Privacy Policy

    We may update our Privacy Policy from time to time. We will notify you of any changes by updating the "Last updated" date at the top of this policy. You are advised to review this Privacy Policy periodically for any changes.

    11. Contact Us

    Questions about this policy, or requests about your data, go through our Contact page. We do not yet publish an email address; that page says what is available today rather than implying a channel that does not exist.