You enter an origin, destination, date, time window, timezone, and interval. Green Light uses those values to validate addresses and compare route times.

Address suggestions, address validation, geocoding, and traffic-aware route estimates are sent to Mapbox. Green Light keeps its Mapbox access token server-side and does not expose it to the browser.

When you are signed out, recent route pairs and trip-result snapshots—including the addresses you enter—are saved in this browser so you can reuse them. A random visitor token is also saved to count usage fairly during the beta. The token is generated in your browser, contains no personal information, and is not a cookie. Clear Green Light site data to remove this local information.

When you are signed in, completed plans—including their addresses—are encrypted and saved to your account history. They are not copied into the signed-out browser history. You can export or delete your account data from the account menu.

On requests that may cost money, that visitor token is sent to Green Light so per-visitor beta limits can be applied. If the token is unavailable, a one-way salted hash of your IP address is used instead as a fallback; the raw IP address is never stored.

Green Light records aggregate product analytics with Cloudflare Workers Analytics Engine — page views and counts for planning and address-suggestion activity, together with operational details such as status, latency, result mode, slot count, and a coarse error category. By design these records avoid full addresses, raw IP addresses, session tokens, and API keys. Cloudflare Workers Logs capture similar operational events under the same constraints.

When activity looks automated, Green Light may load Cloudflare Turnstile, a privacy-focused challenge that helps tell humans from bots. It is used today to protect the contact-email reveal, and may also appear after repeated planning requests in a short time.

Questions or deletion requests can go to the contact email.