Contact DateTime

The fastest channel is email at hhammoud@inovisum.com. Messages are read by a human; most non-urgent threads are answered within two to three business days. The maintainer reviews the inbox during weekday mornings (US Eastern). The site does not run phone, ticket, or social-DM channels for support — keeping correspondence in writing lets us cite the specific IANA tzdb release or RFC section involved when responding.

Reporting a timezone or calendar bug

For a tool that returned the wrong time, please include the tool name, the source IANA zone, the target IANA zone, the input date and time, the result the tool returned, and the result you expected with the tzdb release version you cross-checked against. The most common “bug” turns out to be a near-DST-transition edge case or a bundled tzdb release that pre-dates a recent rule change in the target country — concrete data points let us tell the difference.

Discord-timestamp questions

The Discord-timestamp tag builder emits <t:UNIX:f>-style tags that render in the reader’s local time. If a tag rendered incorrectly in a channel, send the exact tag string, the channel locale, and a screenshot — the rendering is Discord-side, but our tag string should still be correct.

Categories

Bug reports: wrong conversion, broken layout, browser-specific quirk. Tool requests: a single-purpose calendar utility you would like to see. Privacy and data: questions about analytics, advertising, or how the tools handle your time-zone input. Editorial: a tzdb release update or a holiday-calendar correction. Partnership and embedding: using a DateTime tool inside a runbook, scheduling app, or documentation site.

Commitments

We read every message. We will not add you to a mailing list, share your email, or send marketing. We will not provide individualized scheduling consulting or legal advice about contractual deadlines. We will fix a reproducible calendar bug quickly.