Terms of Service

Effective 3 July 2026. Written in plain language on purpose — if anything here is unclear, ask before relying on it.

1. What Datewise is

Datewise ("the Service", operated by Miha Smrekar) is a REST API at datewise.dev that computes business-day, working-hours, and holiday answers from a versioned dataset. By using the Service — keyless or with an API key — you agree to these terms.

2. Preview status

The Service is currently a public preview. It is provided free of charge at the free tier, without an SLA or uptime commitment. We may change rate limits, endpoints (with versioning), or availability during the preview. Anything shown as "planned" on the site is not part of the Service today.

3. What we warrant — and what we don't

What we stand behind: best-effort correctness backed by a documented, auditable process (see the methodology): every answer is pinned to a dataset and tzdata version, corrections ship as new dataset versions with a changelog, and previously served answers are never silently mutated. If you pin a dataset version, your answers are reproducible.

What we don't: the Service is provided "as is", without warranty of any kind, express or implied. During the preview, we accept no liability for downstream financial, legal, or other outcomes of decisions made using the Service — including settlement dates, statutory deadlines, payroll, or SLA calculations. You are responsible for validating the Service against your own requirements before relying on it. Our aggregate liability for any claim is limited to the amount you paid us in the 12 months before the claim (for free-tier use: zero).

4. API keys and rate limits

• Keyless access is rate-limited per IP; free API keys (issued instantly, self-serve) get a higher per-key limit. Current numbers are published on the pricing page.
• Keys are personal to you or your organisation. Don't circumvent rate limits (e.g. minting keys in bulk or rotating IPs); we may revoke keys or block traffic that abuses the Service or attempts to disrupt it.
• We can't recover a lost key (we store only a one-way hash of it, never the key itself) — request a new one. We may revoke keys; see the privacy policy for the small key record we keep.

5. Data and attribution

The holiday dataset is derived from the MIT-licensed python-holidays library and is downloadable. You may redistribute it under the MIT terms with attribution. The Service's code, computation, and branding remain ours.

6. Acceptable use

Don't use the Service for anything unlawful, don't attempt to disrupt it, and don't resell raw access to it as your own API. Reasonable integration into your products — including commercial ones — is exactly what it's for.

7. Changes and termination

We may update these terms; the effective date above changes when we do, and material changes will be noted on the site. We may suspend access that violates these terms. You can stop using the Service at any time; ask us and we'll delete the email and key record we hold for you (see the privacy policy).

8. Contact

Questions, correctness reports, or anything else: use the contact page.