Last updated: 24 June 2026
When Can We Go? is a zero-login trip planner. There are no accounts, no advertising, and no tracking or analytics. We only store what you actively type into a trip — your name and the days you mark — so the people who share your trip link can see it. There are no tracking cookies, so no cookie banner is needed.
The controller responsible for data processing on this website is:
Email:
See also our Imprint.
When you create or take part in a trip, the following information is stored so the planner can work:
We do not ask for an email address, password, or account. We do not collect your IP address for our own purposes, and we run no analytics, profiling, or advertising.
Each trip has a long, randomly generated ID that lives in the link's address (the part after
#). Anyone who has that link can view and edit the trip. Treat the link like a
shared document: only send it to the people you want to take part. The link is not listed
anywhere and is practically impossible to guess, but it is not password-protected.
Trip data is stored and synchronised in real time using Firebase Realtime Database, a service provided by Google. The database is hosted in Google's europe-west1 (Belgium, EU) region. Google acts as our data processor under a data processing agreement (the Firebase Data Processing and Security Terms).
To make this work, your browser loads the Firebase software library from Google's servers
(gstatic.com) and connects to the database. As a technically unavoidable part of any
such connection, your IP address is transmitted to Google. Google may process this on servers
operated by Google LLC (USA); transfers are covered by the EU Standard Contractual Clauses and the
EU–US Data Privacy Framework. More information:
firebase.google.com/support/privacy.
This website is hosted on GitHub Pages, a service of GitHub, Inc. (USA). When you open the page, your browser transmits technical data (such as your IP address and the requested file) to GitHub, which GitHub may log to deliver the site and protect against abuse. See GitHub's privacy statement: GitHub Privacy Statement.
We do not set any tracking or advertising cookies. The app uses your browser's local storage only for strictly functional purposes: to cache your trip so it loads quickly and works offline, and to remember which participant is “you” on this device. This data stays in your browser, is not used to track you, and can be cleared at any time through your browser settings. Because this storage is strictly necessary to provide the service you requested, no consent banner is required (§ 25 (2) TDDDG).
Processing of the trip information you enter is based on Art. 6 (1)(b) GDPR (performance of the service you requested) and on our legitimate interest in providing a functional, account-free planner, Art. 6 (1)(f) GDPR. Hosting and the technically required connection to Firebase are likewise based on Art. 6 (1)(f) GDPR.
Trip data remains stored as long as the trip exists, so that participants can keep using the link. We do not delete trips automatically. If you would like a trip and its contents removed, contact us with the trip link and we will delete it. Functional data in your browser's local storage is removed when you clear your browser data.
Under the GDPR you have the right to:
To exercise any of these, contact us at the email address above. You can also remove a person and their markings directly in the app, which deletes that information from the trip.
This service is not directed at children. Please only enter the names of people who are aware that their name and availability will be shared with everyone who has the trip link.
We may update this Privacy Policy as the app evolves. Changes are published on this page with an updated date above. If we ever add analytics or other non-essential technologies, we will ask for your consent first.