This document describes the internal architecture, JavaScript mechanics, privacy guarantees, and security boundaries of tickr — a digital clock that tracks live seconds since January 1st of your chosen year.
tickr is a precision digital clock that serves two primary purposes:
HH:MM:SS
format, updated every single second using setInterval(), perfectly
synchronized with your device's system clock.
The tool is designed for users who need a precise, constantly updating reference of how much time has passed from a fixed annual benchmark to the present moment — whether for productivity tracking, project timelines, educational demonstrations, or simply to visualise the relentless passage of time.
Date object and Unix timestamps. No data is ever transmitted.
Every operation in tickr is executed 100% inside the browser's memory. No user input — not even the selected year — ever leaves the client.
setInterval() function fires
every 1000ms, calling new Date() to read the current system time.
The hours, minutes, and seconds are extracted and formatted locally.
change event captures the value without sending any
request. The selected year is stored only in a local JavaScript variable.
Date object for January 1st, 00:00:00 of the selected
year, then computes the difference in milliseconds between that timestamp and
Date.now(). This difference is divided by 1000 to yield the total
seconds elapsed, formatted with thousands separators.
Date API.
There are no fetch(), XMLHttpRequest, or
WebSocket calls of any kind.
// Core tick logic — runs every second
setInterval(() => {
const now = new Date();
const year = parseInt(yearSelect.value, 10);
const start = new Date(year, 0, 1, 0, 0, 0, 0);
const deltaMs = now.getTime() - start.getTime();
const deltaSec = Math.floor(deltaMs / 1000);
// update DOM — all local, no network
document.getElementById('deltaSeconds').textContent =
deltaSec.toLocaleString() + ' seconds';
}, 1000);
✅ This design guarantees that all processing happens in memory — nothing is serialised, stored, or transmitted outside the browser tab.
tickr has zero external dependencies. It is built entirely with vanilla JavaScript (ES6), standard HTML5, and plain CSS.
Date, setInterval(), document DOM
manipulation, toLocaleString(), and addEventListener().
No third‑party libraries, no npm packages, no CDN imports.
'Inter', -apple-system, BlinkMacSystemFont, ...)
to avoid any external font requests. No Google Fonts or webfont services.
tickr does not persist any data — neither on the server (there is none) nor on the client beyond the current browser session.
localStorage — The tool never writes to
localStorage, sessionStorage, or
IndexedDB. Your selected year and the current counter value
exist only in volatile memory (JavaScript variables).
document.cookie.
tickr handles no sensitive user data in the traditional sense — it only processes a year selection and the current system time. Nevertheless, the security model is absolute: nothing ever touches the network.
<select> element with a change listener.
It does not wrap a <form> and never issues a
POST or GET request.
// The only "input" is the year dropdown — processed locally
yearSelect.addEventListener('change', (e) => {
// value stays in the browser — never sent anywhere
const year = parseInt(e.target.value, 10);
// … local calculation, DOM update …
});
// No fetch(), no XMLHttpRequest, no WebSocket
// No cookies, no localStorage, no IndexedDB
🛡️ Absolute input security is guaranteed by the architecture: the browser never initiates any outbound request containing user‑derived data. Your interaction with tickr is completely offline after the initial page load.
Launch tickr and watch the seconds accumulate — live, relentless, private.