We sell dates that other people set. That makes the honest description of our own limits part of the product, not the small print at the end of it.
—
If this page does not display correctly, read the terms as plain text.
timesys compiles temporal data — public holidays, exchange closures, deadline calendars — from official and other reliable public sources. It is a reference product. It is not legal, tax, accounting or regulatory advice, and it does not replace the issuing authority. Where a date is material to a legal, financial or regulatory decision, verify the current position with the authority named in the record.
Every date in this corpus is traced to the authority that set it — a statute, a gazette, a ministerial notice or an official calendar — and each source is named on the record it supports. Dates are facts about decisions public bodies have made, and facts are not owned by anyone. What we claim as ours is the work of finding them, checking them against the instrument, grading how well each is evidenced, and arranging the result: our own investment in obtaining, verifying and presenting the contents.
Contains public sector information licensed under the Open Government Licence v3.0 — https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/ . Material from other jurisdictions is used under the terms applicable in each; where a source imposes conditions of its own, those conditions are recorded with it. If you hold rights in something we have published and believe we have overstepped, write to l@naisu.pro and we will correct or remove it.
Backed by: Every source is named on the record it supports, with the date it was read. Provenance in every dossier lists them.
timesys is built and sold for business use, and the terms are written on that basis. We do not, however, stop an individual buying a dossier for their own professional work — and if you buy as a consumer rather than in the course of a business, your consumer rights apply in full regardless of anything written here. We cannot contract them away and do not try to. These terms and any dispute arising from them are governed by the law of England and Wales, and the courts of England and Wales have jurisdiction.
Checkout is operated by Stripe, which acts as merchant of record through its entity Sold through Link, LLC. Stripe is the seller for the purposes of the transaction: it takes payment, charges and remits any VAT or sales tax due in your country, and issues your invoice. Naisu Limited is the publisher of the data and the party that licenses it to you — so the accuracy, edition and liability terms on this page are ours, and the payment terms are theirs. Where the two conflict on a point of payment, theirs govern; on a point about the data, ours do. NAISU LIMITED IS NOT VAT-REGISTERED, and does not need to be for this to work. Because Stripe is the merchant of record it is Stripe, not us, that determines, charges and remits the VAT or sales tax due where you are, and Stripe's invoice is the tax document for your records. So there is no Naisu VAT number to quote on a purchase order, and asking us for one means the invoice you are reconciling was issued by the wrong party. If your finance team needs a tax invoice naming a VAT-registered seller, it is Stripe's invoice they want and it is issued automatically.
Naisu Limited is not registered for VAT. Value added tax and sales tax on transactions are determined, collected and remitted by Stripe, Inc. and Sold through Link, LLC as merchant of record.
Backed by: Your invoice will name Sold through Link, LLC — Stripe's merchant-of-record entity — not Naisu Limited. That is expected, and it is why it is said here first.
Payment is taken by Stripe as merchant of record, and Stripe cannot accept customers in a small number of countries: **China, Cuba, Iran, Kosovo, North Korea, Russia, Syria, Ascension Island and Tristan da Cunha**. If you are in one of those, checkout will not complete, and we would rather you read that here than discover it at the last step. Write to sales@timesys.pro and we will tell you honestly whether there is anything we can do. This is about where a CUSTOMER is, not about which countries the data covers. The corpus holds all 241 jurisdictions including every one named above, and those calendars are on sale to anyone who can buy at all — a Syrian public holiday is a fact about the world, and we sell facts about the world.
Customer eligibility is determined by Stripe, Inc. and Sold through Link, LLC as merchant of record, not by Naisu Limited. Data coverage is unaffected by it.
Every record identifies its source, its assurance level and the date it was last reviewed. We take reasonable care in preparing and maintaining the data. What we record is what the authority published at the time we read it — and authorities move dates, declare holidays at short notice, and publish corrections of their own. A record labelled compiled or corroborated is explicitly not a confirmation from the authority. When a date changes, we change it and log it. What we do not do is pretend the first answer was final.
We do not represent that the data is complete, current or free from error, and we give no warranty of fitness for any particular purpose beyond those that cannot lawfully be excluded.
Backed by: Every record carries assurance.level, sources[] and reference_urls[] — see any row on Coverage.
Singapore Calendar Intelligence
Edition 2026.09
Published: 1 September 2026
corpus fb9145ab4cfc2e9a · supersedes 2026.08
Every dossier opens on a block like this one.
Every artefact we publish carries an edition label, a publication date and a digest of the corpus it was built from. A report reflects the information available on its publication date; subsequent changes by issuing authorities may not be reflected in it. Editions are immutable. A correction produces a NEW edition and an errata entry — we do not silently rewrite an edition you may already have cited.
Backed by: edition.digest is a SHA-256 over the observance corpus, computed at build time. Quote it back to us.
When we get something wrong we publish it. The errata log names the record, the edition the error appeared in, the edition that corrected it, and what changed. Holders of an affected edition are notified. The log is public and is not pruned.
Backed by: Published below, from the same feed the product reads. Not pruned.
Two companies process data on our behalf, and no others. **Stripe** is the merchant of record, invoicing through its entity Sold through Link, LLC: they take payment, charge and remit tax in more than 80 countries, handle disputes, and hold the billing details — we never see your card. **SMTP2GO** delivers our email: purchase confirmations, sign-in links and edition notices. They are an EU-GDPR compliant processor and they see the address we send to and whether delivery succeeded, because a bounced sign-in link is a customer locked out of what they paid for and we have to be able to tell. WHAT WE DO NOT DO WITH EMAIL. We do not use open pixels, and we do not act on click data — nothing we send is targeted, scored or segmented by what you opened. Our sending provider does operate a link-tracking facility on its own infrastructure as part of the service, so we will not claim it is switched off at every layer; what we will say is that we do not collect, read or use it, and that no such data reaches a report anyone here looks at. What we rely on is whether the mail server accepted the message — delivery health, not behaviour — because a bounced link is a customer locked out of what they paid for. There is no analytics on the pages you reach after signing in, and our own logs redact your address to the first two characters. We do not sell, share or rent your details, and we do not send marketing you did not ask for. Ask us at any time what we hold about you and we will tell you; ask us to delete it and we will, subject only to the invoice records tax law requires us to keep. We count visits with **Umami**, which we host ourselves on our own server in **Nuremberg, Germany** — inside the EU, and adding no company to the two named above. Your page views are not sent to an analytics company at all. It sets no cookies and stores no identifier that could follow you to another site, which is why you were not asked to accept anything on arrival. What it records is the page, the referrer, and a coarse country and device type; that is enough to know which jurisdictions people look up, and it is what decides what we build next.
Data controller: Naisu Limited, registered in England and Wales, company number 16039918, 71–75 Shelton Street, Covent Garden, London WC2H 9JQ. Processors: Stripe, Inc. and Sold through Link, LLC (payments, merchant of record) and SMTP2GO Limited (transactional email). Site analytics are self-hosted (Umami, Nuremberg, Germany) and are not processed by a third party. Contact sales@timesys.pro for any data request.
An API key is issued to one organisation and is yours to keep secret; anything done with it is treated as done by you, so tell us at once if it leaks and we will replace it. Free Developer keys are issued on review rather than automatically, one per organisation, and are licensed for evaluation only — not for use in a product you sell or operate commercially. Paid plans carry the commercial licence. INACTIVE FREE ACCOUNTS ARE CLOSED. A free key that goes unused for six months is withdrawn and the account with it. We will email you at least fourteen days beforehand, and using the key once in that time keeps it. This is housekeeping rather than a penalty: unused credentials sitting in inboxes are a liability to you and to us, and protect nothing. You can ask for a new key whenever you need one. Paid plans are never closed for inactivity — you bought the right not to call us. SUSPENSION IS IMMEDIATE WHERE THE REASON IS SERIOUS. If a key is being used unlawfully, shared or resold, driven to extract the corpus wholesale, or used in a way that threatens the service or other customers, we will suspend it at once and tell you at the point we do it, with the reason. We do not need to warn you first — waiting would defeat the purpose — but we will always say what happened, and if we have got it wrong we will put it back and make good any paid time you lost. OTHERWISE WE GIVE NOTICE. For any other reason, on a paid plan, we will give you reasonable notice and refund the unused part of what you paid. We are not going to take money for a period and then end it without giving it back. A free key we may withdraw at any time, with notice where it is practical to give it. WE MAY CHANGE THESE TERMS, and will publish the change with the edition record. A change never applies retroactively to an edition or a period you have already paid for: if we change something material during a term you have bought, the version you agreed to governs that term, and you may cancel from the next renewal. If you are a consumer, your statutory rights are unaffected — we cannot vary them and do not try to.
You may query the API, store the results in your own systems, and use them to run and build your own products, within the scope your plan covers. Caching is expected and encouraged — this data changes on a schedule, and hammering the API for a value you already hold helps nobody. What you may not do without a redistribution licence is republish the corpus, or a substantial part of it, as a dataset, feed or competing product. The line is not the number of calls: it is whether the output is your product using our data, or our data presented as your product. Redistribution is included from the Business plan up; if you are unsure which side of the line you are on, ask us before you build, not after. Systematically extracting the whole corpus through an evaluation key is the one thing that is clearly outside the terms, and it is also the one the scope limits already make impractical. A DOSSIER IS LICENSED TO ONE LEGAL ENTITY, and inside that entity you may circulate it as widely as you like — put it on the intranet, send it to every office, quote it in a board pack. We are not going to count readers, because a reference document is not worth less to the second person who reads it and pretending otherwise would only buy us a policy nobody can verify. The boundary is the ENTITY, not the headcount. A separate company — a subsidiary, an affiliate, a joint venture, a client you advise — needs its own licence, and a group buying centrally should tell us how many entities it covers so we can price it once rather than argue about it later. Passing a dossier to someone outside your organisation, or building it into something you sell, is redistribution and needs a redistribution licence. We know we cannot enforce most of this technically. Every dossier carries the buying entity's name on every page, which is enough to make an accidental leak obvious and nothing like enough to stop a determined one. We would rather draw the line clearly and trust the people who care about being on the right side of it than build restrictions that punish honest customers and inconvenience nobody else.
Dossiers are digital files delivered within minutes. Because of that, the 14-day right to change your mind ends once you download — you are asked to confirm that at checkout, in two separate tick boxes, neither pre-ticked. That waiver covers change of mind and nothing else. If a file is defective, incomplete or not as described, tell us: the first remedy is a corrected file, and if we cannot put it right you are entitled to a refund. Your statutory rights are unaffected.
Backed by: Both checkout confirmations are stored against the order with a timestamp — a waiver we cannot evidence is a waiver we do not have.
Our total liability to you arising out of or in connection with the data and the service — whether in contract, tort (including negligence), breach of statutory duty or otherwise — is limited to the fees paid for the product giving rise to the claim in the twelve months before it arose, whether those fees were paid to us or to our merchant of record on our behalf. The cap for a dossier is what you paid for that dossier. We state it that way rather than with a figure because a number written into a liability clause is a number that stops matching the price list.
We are not liable for indirect or consequential loss, loss of profit, revenue, business or anticipated savings. Nothing here limits liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, for breach of the statutory terms implied by the Consumer Rights Act 2015, or for anything else that cannot lawfully be limited or excluded.
Backed by: Bounded by what you actually paid — visible on your Stripe invoice, not on ours.
We may change these terms. When we do, the change is described and dated in the changelog, and the new terms apply to purchases made after that date. A purchase you have already made keeps the terms that were in force when you made it, in the same way an edition keeps its date. Nothing we change here can take away rights the law gives you: your statutory rights, and in particular your rights as a consumer under the Consumer Rights Act 2015, stand regardless of anything written on this page. This section was added on 4 September 2026.
We do not describe this data as guaranteed, always correct, authoritative, certified or definitive — on this site, in the reports, or in sales conversations. The assurance label is the claim, and it is deliberately narrower than any of those words. This is a standing editorial rule, and it is written here so a customer can hold us to it.
Every correction we have published, oldest last. Records are never removed from this log.
No corrections have been published since editions began. This log starts at edition 2026.09 — it is empty because it is new, not because the data has never been wrong.