This page explains how the tools and written content on Zeitful are produced and kept accurate. It exists so you can judge for yourself whether a result is trustworthy, and so corrections have a clear route.
Last updated: 2026-06-16.
Everything on Zeitful is built and maintained by Vikas Dulgunde, a software engineer based in London, United Kingdom with around six years of professional experience. The same person writes the code, the calculator logic, and the editorial guides. There is no anonymous content team and no AI-authored articles published under invented bylines. Pages carry a visible byline and a published or updated date so you always know who is accountable for a claim and when it was last touched.
date-fns-tz), not hand-written offset tables. This is the same approach used in production software, and it means DST and offset changes are picked up from the upstream database rather than guessed.Tools are tested against known reference cases before they ship, and time-sensitive data (such as holiday tables and DST transitions) is revisited as the underlying sources change. When a guide is revised in a way that affects its substance, the updated date on the byline changes. Minor copy-edits do not move the date.
Some tools touch on areas regulated by law or professional bodies, such as legal deadlines, pregnancy dates, tax years, employment leave, and immigration windows. Zeitful treats these as informational only. Those pages carry a clear disclaimer, cite the official rule or authority, and tell you to confirm anything that carries real consequences with a qualified professional or the primary source. Zeitful does not give legal, medical, financial, tax, or HR advice.
Zeitful runs display advertising, explained in full on the advertising & affiliate disclosure page. We do not run affiliate links at this time. Advertising never changes a calculation, a cited fact, a ranking, or whether a competing product can be mentioned. Factual content and earning relationships are kept separate on purpose.
If you find an error, such as a wrong conversion, a stale holiday, a DST edge case handled incorrectly, or a citation that does not check out, email team@palenebula.com or use the contact page. Where possible, include the page URL, the inputs you used, the result you expected, and a source that supports the correction. Data fixes are made at the source rather than by only editing the wording, so the same fix applies everywhere the data is used.