← Back to app · Blog · About
TimeZoneMeet's blog is written and maintained by the small team that builds the product. We are the same people who decide which cities to include in the lookup database, how city-name collisions are resolved, and how the Schedule tool ranks meeting windows. That overlap matters: every recommendation in a post is something we test against the actual app before we publish it.
We focus on a single topic and refuse to drift: the practical mechanics of working across time zones. That covers four areas in detail.
America/New_York is more useful than EST, how UTC offsets change throughout the year, and where ambiguous abbreviations cause mistakes.We avoid topics where being wrong is dangerous: legal compliance, immigration, payroll across borders, tax residency, and medical timing. Plenty of well-resourced publications cover those. If a guide touches an adjacent area (say, a brief mention that some labor laws restrict after-hours scheduling), we point to authoritative sources rather than paraphrase rules we don't update on a legal calendar.
The IANA time zone database is updated several times a year as governments change DST rules or shift offsets. We track those changes and refresh affected posts on a quarterly cycle, with extra passes around the spring and autumn DST transitions in the Northern Hemisphere. Each post displays a visible "Updated" date when the body changed materially.
City coordinates and time zone resolution come from a build of the GeoNames cities-15000 dataset combined with the IANA tz database via the tz-lookup library. When a city sits near a zone boundary or has changed offset recently, that is documented in the relevant post.
Most posts originate from a real scheduling failure we either lived through or fielded as a support email. We draft a post when the same mistake shows up two or three times. Drafts are reviewed against four checks before publishing:
We do not accept paid placements, sponsored content, affiliate links, or product reviews. The site shows display advertising via standard programmatic networks (currently Google AdSense on the web and Google AdMob in the iOS app); ad placement is configured globally and never per article. Premium subscriptions are sold for the website (Stripe) and the iOS app (Apple In-App Purchase) — those are our only direct revenue sources, and they are documented in the About page and FAQ.
If you spot a factual error in a post — an out-of-date DST rule, a misnamed city, or a worked example that no longer matches our app's output — please email support@timezonemeet.app with the post URL and the specific line. We update affected posts and revise the visible "Updated" date.
The site and the editorial team are operated by Scorifya LLC, the publishing entity behind TimeZoneMeet. For all editorial questions, factual corrections, or feedback on a specific post, email support@timezonemeet.app. General product, billing, and account inquiries also use the same address; we route internally.
Page last updated: May 7, 2026.