XClock does not create a timekeeping account. Its tool state lives in your browser’s local storage. That makes a return visit convenient, but it is not cloud backup, synchronization or a background alarm service.
The saved record
| Tool | Saved information | On return |
|---|---|---|
| Alarm | Target timestamp, label, sound and entry ID. | Only future targets are restored. |
| Timer | Name, remaining seconds, configured duration, running flag, sound and ID. | A running entry resumes from saved remaining seconds. |
| Stopwatch | Elapsed reading, running flag and cumulative laps. | A running entry continues from its saved elapsed reading. |
The tool-state record uses the key xclock_state_v3. This is separate from consent preferences and other site storage described in the Privacy Policy.
Time away is not counted back into a countdown
A timer saves remaining seconds rather than an absolute finish deadline. Closing a page with 45 seconds saved does not create a server job that finishes it 45 seconds later. When restored, it resumes from the saved value. Similarly, a running stopwatch resumes from its saved elapsed reading; it does not add the interval during which its page was closed.
Alarms are different because they save an absolute target timestamp. If that target is still future, the restored page schedules it again. If it is past, the entry is skipped rather than replayed. These differences explain why three tools can appear to restore differently without a browser-storage failure.
Dedicated routes and the home workspace
The focused Alarm, Timer and Stopwatch pages share the same browser record, but each runs only its own tool. Moving from Alarm to Timer preserves the saved alarm fields; it does not keep the previous page running. Use the all-in-one homepage if you need all tool types active without navigation.
Avoid editing the same saved tools in several tabs at once. The pages are not a synchronized multi-tab control system; one page can save a more recent or older snapshot after another. A single active workspace is easier to reason about.
Why an entry can disappear
- You opened a different browser, profile, device, private window or site origin.
- Browser settings or cleanup software cleared site data.
- The browser did not allow storage, or an abrupt termination prevented the latest save.
- An alarm’s target passed before you reopened the page.
- You removed the entry or used the Alarm tool’s Clear All control.
Private-session data is normally cleared when that private session ends. Browser storage is separated by origin; the technical basis is explained in MDN’s localStorage reference.
A safe restoration check
- Create a named timer, leave it stopped and note its duration.
- Refresh this same page in the same browser. Check the name and duration.
- Start it, stop it and refresh again. Check the saved remaining value.
- Remove the temporary entry when finished.
To start over, use the individual Remove controls, Alarm Clear All and Stopwatch Reset. Clearing all browser data for XClock also affects consent and other preferences; do that only if you intend those consequences. There is no XClock recovery service for cleared local state.