About Days Since
Last updated: October 28, 2026
Days Since counts elapsed time from a calendar date you choose. The number on the page is a clock, not a certificate, a medical record, or an official anniversary from any institution.
Who runs it
Days Since is an independent website at days-since.app, published by the site operator. It is not a hospital, a recovery program, a government calendar office, or a publisher of legal deadlines. Questions and corrections go to contact@days-since.app. That address reaches the person who publishes the site. There is no separate support desk and no account team.
What the counter does
The homepage builds one count at a time from:
- A calendar date — either a holiday in the 2020–2026 menu, or a month, day, and year you set. The earliest year in the menus is 1960 and the latest is 2026.
- An optional event name — a label such as “Wedding day.” It does not change the arithmetic.
From that date the page shows days, hours, and minutes, and it can copy a share link or open a fullscreen view of the same count. The page opens on a sample, New Year’s Day 2026 (January 1), so the result is not a row of zeros before you pick a date. Replace it with your own date. The page shows one date at a time.
How the count works
The date is read as midnight at the start of that civil day in the time zone of the device you are using. The script subtracts that instant from the current time. Whole days are blocks of 24 hours (86,400 seconds). Hours and minutes are what is left over. On the start date itself the day figure is 0 until 24 hours have passed. A date later than “now” is clamped to zero, because this is a since-counter and not a countdown.
That rule is elapsed time, not “how many calendar boxes have I touched.” People often count the start date as day 1, or they count both the start date and today. This page does neither. It also does not convert the total into years and months. A calendar anniversary — the same month and day in a later year — can fall on day 365 or day 366 depending on whether February 29 sits inside the span. The anniversary guide and the leap-year guide walk through examples.
Time zones are the zone of the browser, not a zone you select and not UTC. A share link stores the calendar date and the optional name. It does not store a time zone or a time of day. Two people opening the same link can see hour counts that differ, and near midnight the day number can differ, because each device starts the day at its own local midnight. Daylight saving makes some civil days 23 hours long and some 25. Because the counter divides real elapsed time by 24 hours, the day figure can sit an hour away from a count of midnights crossed. The time-zone guide describes that without pretending the page knows where the original event happened.
The holiday names are labels on fixed dates in the script for 2020 through 2026. They are common U.S. observances, not a federal schedule, and a weekend holiday is not always moved to the observed weekday. During the current year the menu hides dates that are still in the future.
What it leaves out
The counter does not know the hour the event happened, only the calendar date, which it treats as midnight. It does not send reminders when a milestone arrives. It does not verify that a sobriety date or a habit date is accurate, and using it that way is personal tracking, not care from this site. It does not compute business days, exclude weekends, or follow a court holiday. Details of the arithmetic are in how calendar days are counted.
The last date you calculate, and the optional event name, are kept in this browser’s local storage. They are not uploaded to a Days Since account. The privacy policy describes share links and advertising cookies separately, because those are the cases where data does leave the device.
Advertising
The homepage and the guides may load Google AdSense. This about page, the privacy policy, the terms, and the contact page do not. Advertising pays for hosting a free counter. It does not change the day count, and an ad is not a recommendation about the date you are tracking.
Corrections
If a worked example does not match the counter, or a sentence describes the rule wrong, email contact@days-since.app with the page and the sentence. The contact page says what to include. Guide figures were checked against the Gregorian calendar and the same 24-hour elapsed-time rule on October 28, 2026.