Your call stays yours.

The website call checker and calendar-file tools calculate in your browser. Wait, What Time? does not automatically upload meeting fields or imported calendar files to an application server. There is no signup, advertising, app analytics, or calendar-account connection.

Our hosting provider, Vercel, can process ordinary access logs, including IP addresses and requested URLs. This is separate from the app’s local calculations.

Your light or dark appearance preference is saved in this browser’s local storage. Meeting inputs are not saved there.

Comparison links encode the selected time zones, dates, hours, duration, cutoff, policy and review date in the URL fragment (after the #). Anyone who receives the full link can read these values. They are not encrypted. Share only information you intend the recipient to see. Links are snapshots, not subscriptions; changes require a new link.

The team planner also includes its meeting title and participants’ time zones and working hours in shared links. Original calendar files, attendee lists and descriptions are not included. If you import a call, its selected schedule becomes part of the comparison. Copying a message or downloading a file does not send it to anyone.

The Use my AI button creates a brief and comparison JSON locally. Pasting the brief or attaching the JSON shares the selected meeting settings with your chosen AI provider. Review links are readable snapshots, not permission to act.

When an agent explicitly calls our MCP endpoint or JSON API, the supplied time zones, dates, duration, cutoff and policy are sent to Wait, What Time?’s Vercel functions for calculation. The app does not persist request bodies or deliberately log them. Vercel may process ordinary hosting telemetry. The API accepts only documented scheduling settings; it rejects extra fields such as calendar titles, attendee lists, descriptions, credentials and account identifiers.

The sample connection check sends fixed synthetic settings. Agent tools do not access calendar accounts, send messages or change invitations. The agent should obtain your confirmation before using its own separate tools for those actions.

Email and WhatsApp buttons pass the draft and its comparison link to the selected app. Anyone receiving the link can read the selected times and settings. You choose the recipient and send the message yourself. The chat-copy action only copies text for pasting into Slack, Teams or another app; it is not an account connection.

The Google Calendar button passes one selected proposed occurrence to Google’s new-event form. You review and save it there. Calendar downloads contain four separate proposed events for the previewed dates, including when the request is ongoing. These actions create new copies; they do not edit the original invitation, send attendee notices or provide ongoing sync.

The call checker can read a local .ics file and offer compatible weekly calls. It imports only simple indefinite weekly patterns with a recognized time zone, a duration of 15–180 minutes and no changed, excluded or extra occurrences. Unsupported records are listed for manual entry. The latest eligible past occurrence becomes the reference; it may already be after an earlier clock change. Review or change that date if you need an earlier baseline. Calendar files, titles and attendee metadata are not saved to local storage.

The call checker models one weekly pattern using the reference date and time you provide. It does not verify the original invitation, existing moved or cancelled instances, holidays, another person’s availability or collisions with other meetings. An unknown anchor produces conditional scenarios. A finish-by check is not an availability guarantee.

The next four calls are after the chosen review date in the source time zone. Calls on that date are excluded. Ongoing policies can extend beyond the 52-week forecast. Missing or repeated local clock times in the proposed dates require an unambiguous input. Future time-zone laws may change.

The team planner’s calendar checkup compares occurrences inside a 90-day window. It can miss a shift immediately before the first checked occurrence. Include the previous occurrence when choosing the start date. Unsupported records require manual review. It does not detect overlapping meetings.

ICS downloads add separate events. They do not update original invitations or send attendee notices. After agreement, the organizer must edit the existing invitation and verify the resulting dates in both zones.

No payment or account is required. Your result remains a proposal until the people involved agree. No claims of guaranteed attendance, automatic rescheduling or detected calendar availability are made.

Check a call →