Data sources
useChrono uses IANA time zone identifiers through the runtime Intl API. City labels map to those identifiers before calculations are shown.
Data notes
How useChrono handles time zone data.
useChrono is built for fast time zone planning, not for legal or operational recordkeeping. This page explains what the tools calculate, what they do not know, and when you should verify the time somewhere else.
Editorial responsibility
How corrections are handled
Young reviews tool behavior and editorial updates against IANA timezone identifiers, date rollover, daylight-saving transitions, and representative cross-region meeting scenarios.
Content dates change only when the published guidance or data notes are reviewed. Report an error to support@usechrono.com with the affected URL, date, locations, and expected result.
Daylight-saving changes
DST offsets come from the runtime time zone database. Government rules can change, so older devices or outdated runtimes can disagree near rule changes.
Meeting recommendations
Suggested meeting windows compare selected working-hour ranges, meeting duration, and local date rollover. They do not know holidays, travel, or attendee availability.
Privacy boundary
The public tools do not require accounts. Calendar links and ICS files are generated from the selected slot in the browser.
Before you send a time
What to double-check
- Check both local dates when a conversion crosses midnight.
- Compare the result with the other location's working hours before sending an invite.
- Use a calendar or source system for legal, travel, payroll, trading, medical, or deadline-critical decisions.