DevClock Privacy Policy

 ·  DevClock Chrome Extension

Effective date:

Overview

DevClock is a Chrome extension that converts timestamps between timezones and generates provider-ready log query windows for engineers. It runs entirely within your browser and does not communicate with any remote server. No analytics, telemetry, or tracking of any kind is included.

This policy describes what information DevClock accesses, why it needs it, and what it does with it.

Data Collection

DevClock does not collect, transmit, or store any personal data outside your own browser. Specifically:

All processing happens locally. The extension has no back-end and makes no outbound network requests.

Permissions

The following permissions are declared in the extension manifest. Each is limited to the minimum required for the stated feature.

storage Saves your preferences (target timezone, source timezone list, query provider, display format) to Chrome's sync storage so they persist across browser restarts and devices signed in to the same Chrome profile.
clipboardRead Allows the extension to read the clipboard when you paste a timestamp into the popup input field. No clipboard content is stored or transmitted.
contextMenus Registers a right-click context menu entry so you can send a selected timestamp directly to DevClock from any web page without opening the popup manually.

Third-Party Libraries

DevClock bundles the following open-source libraries locally. They are included as static files inside the extension package and make no network requests of their own.

Luxon DateTime parsing and timezone-aware formatting (DST-safe). Bundled locally as lib/luxon.min.js. MIT license.
chrono-node Natural-language date/time parsing fallback (e.g. "next Friday 4pm", "2 hours ago"). Bundled as part of the vendor build. MIT license.
any-date-parser Log-native and loose-format date parsing fallback pipeline (Apache CLF, syslog, space-separated datetimes). Bundled as part of the vendor build. MIT license.

Changes to This Policy

If this policy is updated, the revised version will be published at this URL and the effective date above will be updated. Because DevClock collects no personal data, policy changes will typically only reflect updates to declared permissions or bundled libraries following an extension version release.

You can review the full history of changes to this page in the GitHub repository.

Contact

If you have questions about this privacy policy or DevClock's data practices, please open an issue on GitHub:

github.com/kokilaw/dev-clock-extension/issues