Terms of Service
Last updated: 12 August 2026
1. Agreement
By using UTCTime (utctime.app) — the website, the tool pages, or the JSON API — you agree to these terms. If you do not agree, do not use the service. We may update these terms; material changes will be reflected in the date above.
2. What the service is
UTCTime displays and converts times, dates and timestamps, and exposes the same computations through a public JSON API. All results are derived from the host's system clock and the IANA time zone database.
3. Accuracy, and the limits of it
We take correctness seriously: values are computed at request time from current tzdata rather than stored offsets, and the host is NTP-synchronised. Even so, the service is provided as is, with no warranty of accuracy, fitness for a particular purpose, or uninterrupted availability.
Do not use this service as the sole time source for anything safety-critical, legally binding, or financially settled. Network latency alone puts a floor under how accurate any HTTP-delivered time can be, daylight-saving rules can change with little notice, and a host can be wrong. Systems that need authoritative time should run NTP against a recognised time authority.
4. The API
- The API is free, requires no key, and may be used in commercial products.
- The published fair-use limit is 10 requests per second per IP address. We may throttle or block traffic that materially degrades the service for others, and we will always prefer contacting you over silently blocking.
- Response fields may be added over time. Fields will not be removed or renamed without notice on the API documentation page. Parse defensively and ignore unknown keys.
- No uptime guarantee or SLA is offered on the free tier. If your project cannot tolerate an outage, cache the last good response and degrade gracefully — the same advice we would give about any free API.
- Do not present the API as your own service, resell raw access to it, or use it to build a mirror whose purpose is to replace it.
5. Acceptable use
Do not attempt to disrupt the service, probe it for vulnerabilities without contacting us first, scrape it in a way that imposes load out of proportion to your actual need, or use it to facilitate unlawful activity. Automated access to the HTML pages should respect robots.txt; if you want the data, use the API — it is cheaper for both of us.
6. Your content and preferences
Values you type into the converters are processed to produce a result and, for the client-side tools, never leave your browser at all. Display preferences are stored in your browser's local storage under the key utc:prefs:v1. We do not hold an account for you, and there is nothing for us to lose or leak.
7. Intellectual property
The site design, copy and code are ours. Time values, offsets and zone rules are facts and are not claimed as property; the underlying zone data comes from the IANA time zone database, which is in the public domain. Code snippets shown on this site are provided as examples and may be used freely without attribution.
8. Third-party links
Some pages link to external references and to calendar providers (Google Calendar, Outlook). We do not control those services and are not responsible for their content or their handling of your data.
9. Limitation of liability
To the maximum extent permitted by law, we are not liable for any indirect, incidental, or consequential damages, or for any loss arising from reliance on a time value obtained from this service, including missed deadlines, mis-scheduled events, or incorrect timestamps written to your systems.
10. Termination and changes
We may modify, suspend, or discontinue any part of the service at any time. If the API is ever retired we will announce it on the API page ahead of the shutdown rather than letting it quietly fail — precisely the failure mode this project exists to answer.
11. Contact
Questions about these terms: contact us.