Privacy

Your timezone planning state stays in your browser.

BeanNest Time performs timezone calculations locally from bundled IANA timezone data. The Time app does not send selected cities, timezone IDs, local dates, meeting times, or participant labels to a timezone API.

Saved settings

Saved World Clock locations, Home, clock format, and legacy preference fields are kept in browser local storage. Meeting Planner participant names and its working roster are transient and are not added to that saved Time state. You can clear saved Time settings from the World Clock, Converter, or Meeting Planner. No BeanNest account is required.

Share links

Copy Link and Share are explicit actions. Converter and legacy Meeting links use bounded version 1 hash state; the current Meeting Planner emits a bounded version 2 hash state. Normal browser requests do not send the hash fragment to the BeanNest web server. Meeting links preserve deterministic time/timezone settings but exclude participant names, email addresses, titles, notes, preferred-hour settings, and arbitrary free-form text.

Calendar handoff, export, and hosting

Meeting Planner creates its .ics file locally from the selected instant and duration. The optional Google Calendar button is a normal outbound link built from the same UTC start/end and a generic meeting title; it does not contain participant names and is not opened unless you choose it. BeanNest does not request Google Calendar access or read free/busy data. As with any website, the hosting provider can process ordinary technical request information needed to serve and protect the site, but the Time application has no server endpoint for timezone-planning inputs in this release.