Local storage is not private sharing: a copied board URL exposes its configuration to recipients and to the infrastructure serving that URL.
Scope of this draft
This page describes the current local Clock.live implementation. The operator identity and contact details are confirmed. Production hosting/log retention disclosures and applicable public privacy choices still require review. It is not a statement that those deployment details are already in place.
Public operator: Bridgetoclouds.com LLC. Operator country: United States. The contact page shows whether a public channel is configured. No account registration, contact submission form, payment processing or personal-board database is implemented.
Settings saved by the tools
These values use browser storage rather than account storage. They can be read by scripts running for the same site origin, and by someone with access to your browser profile. Browser settings, private browsing or quota limits can deny writes. Clearing site data removes them.
| Storage key | What it holds | Where it lasts |
|---|---|---|
| clock.live.display.v1 | Appearance, hour format, seconds, clock size and selected city when applicable | localStorage in this browser |
| clock.live.board.v2 | Ordered city IDs and base city | localStorage in this browser |
| clock.live.board.v1 | Supported earlier board format, read for migration | Existing localStorage until changed or cleared |
| clock.live.hours.v1 | Per-city weekdays, start/end and overnight choice | localStorage in this browser |
| clock.live.timer.v1 | Countdown checkpoint, phase, elapsed/duration, recovery clocks, next duration, sound choice and tab/version tokens | localStorage; reset replaces progress with an idle record |
| clock.live.stopwatch.v1 | Elapsed checkpoint, running/paused phase, lap totals and recovery clocks | sessionStorage for that tab’s page session |
Requests, city search and external links
Loading pages and time samples sends ordinary requests to this site. Serving infrastructure necessarily receives connection and request information; public hosting providers, log fields and retention periods must be documented before launch. No unverified deletion period is promised here.
City search runs against a downloaded catalog in the browser. The current search implementation does not send the typed query to a search service. The browser-reported time zone can initialize the local clock; precise geolocation permission is not requested.
Following an external source link sends a normal browser request to that destination. It can receive standard request information and a referrer according to the browser and site policies. Clock.live does not control those sites’ storage or privacy practices.
Website statistics and advertising
Clock.live uses Vercel Web Analytics on its production domain to understand visits and page views. Vercel describes the service as using aggregated statistics without third-party cookies, with visitor-session identification discarded after 24 hours. This is not a retention promise for every hosting log or aggregate report.
The integration removes query strings and fragments from measured page URLs and limits browser referrers to their origin. It does not send city-search text, shared-board configuration, saved settings or custom tool events as analytics properties. A fresh page load records a page view; clock ticks and changes within a tool do not create extra page views.
Analytics does not start on preview domains, localhost, fullscreen or error pages, or when the browser reports Do Not Track or Global Privacy Control. Browser blocking may also prevent measurement. No real advertising provider is enabled; an empty layout reservation is not an ad request. Privacy and contact pages contain no ad placement.
The remaining hosting disclosures and applicable privacy review are still being completed. Adding statistics does not certify those separate requirements.
Your controls and remaining launch work
Use the tools’ reset/remove actions to change stored tool state, or your browser’s site-data controls to remove the origin’s stored settings. Resetting a countdown retains an idle record to prevent stale tabs from reviving it. Clearing browser storage does not recall a shared link or erase copies retained by recipients or infrastructure.
Send privacy questions to the public contact address on the contact page. Deployment privacy disclosures still require review; passing local tests does not complete that review.