01Calculator data
Calculator data
Start and end times, dates, calculation rules, and results are handled in browser memory. Results are generated locally, and Calculation State is not persisted by default.
No calculation or business API receives raw calculator inputs or exact results. Those values and Share Fragments are not sent to Google Analytics, and TimeDateLab defines no custom calculator-interaction events.
On request
Now and Today read the device-local date or time only when you click them. They do not use geolocation or an external time API.
02Local preferences
Local preferences
TimeDateLab stores the 12-hour or 24-hour time-display choice locally in this browser. It does not store an analytics consent choice. The MVP has no account or user profile system.
Local preference
Time display
12-hour or 24-hour display · Stored in this browser
Clears the saved time-display choice. It does not clear calculator fields, Share links or URL fragments, Google Analytics cookies, browser history, or clipboard contents.
03Shared calculations
Shared calculations
Share is explicit. Only after you choose Share does TimeDateLab create a versioned Share Fragment containing the normalized inputs and calculation rules needed to reproduce the calculation.
The URL fragment is not included in ordinary HTTP requests to TimeDateLab. That does not mean it can never leave your device.
Where a Share Fragment can appear
- Browser address bar
- Browser history
- Browser synchronization
- Clipboard
- Messaging applications
- Screenshots
- Recipient devices
Copy result writes localized result text to the clipboard only after you choose Copy. It does not create a Share Fragment.
04Hosting and network requests
Hosting and network requests
TimeDateLab does not send calculator inputs to a calculation service. Like any website, loading TimeDateLab still creates ordinary HTTP requests needed to deliver pages and static assets. The static site is served through Cloudflare infrastructure.
These hosting requests are distinct from submitting calculator state. Calculator controls and actions do not create a calculation or business API request.
Page-level measurement
TimeDateLab loads Google Analytics 4 (Measurement ID G-VJCH0VTQ5T) immediately only when the browser's exact runtime origin is https://timedatelab.com. The production Origin gate isolates environments; it is not a consent decision or a consent-management platform. Localhost, previews, staging hosts, unknown hosts, HTTP, subdomains, and non-standard ports do not load or connect to Google Analytics. On the production origin, one page view uses the canonical address without query parameters or Share Fragments. Google Analytics may set first-party _ga cookies containing analytics identifiers. TimeDateLab sends no calculator inputs, results, errors, or custom interaction events; Google signals and ad-personalization signals are disabled, and no Google Ads, GTM container, Clarity, or other telemetry platform is enabled.
05Contact
Contact
- Operator / data responsible party
- Timedatelab Team
- Privacy contact
- support@timedatelab.com
The MVP has no web contact form. The Contact page uses a mailto link to open your email client with a fixed subject, the clean Contact route, and locale. You choose what information to include.
Sending an email moves the information you voluntarily provide outside the local calculator boundary. Calculator inputs, results, errors, query parameters, and Share Fragments are not inserted automatically. Do not send sensitive information.