JenKitAdd to Chrome
← Back to home

Privacy Policy

Last updated: July 13, 2026

This policy explains how the JenKit Chrome extension ("JenKit", "the extension") and its website at this domain ("the site") handle data. JenKit is built to keep your data on your device and to communicate only with the Jenkins instances you choose.

Summary

  • →JenKit stores a small amount of configuration on your device only.
  • →It never collects, stores, or transmits your Jenkins username, password, or API token.
  • →It includes no analytics, telemetry, advertising, or tracking.
  • →It connects only to Jenkins hosts you explicitly add and authorize.

Data stored on your device

JenKit uses chrome.storage.local, which lives in your browser profile on this machine and is never synced to a cloud server by the extension:

  • •Environment configurations - the names and Jenkins URLs you add, and the lists of jobs you follow.
  • •Passkey hashes - if you protect an environment with a passkey, only a SHA-256 hash of that passkey is stored. The passkey itself is never stored.
  • •Biometric credential ID - if you enable fingerprint unlock, a WebAuthn platform credential ID is stored locally. The credential itself is held by your operating system and browser, and never leaves the device.

JenKit does not store build logs. Console output is fetched from your Jenkins on demand and kept only in memory for the duration of a viewing session.

What JenKit does not collect

  • •Jenkins credentials, API tokens, or passwords.
  • •Personal information about you or your builds.
  • •Analytics, usage statistics, crash reports, or advertising identifiers.
  • •Cookies (the website is static and sets none).

Network access

The extension makes network requests only to the Jenkins hosts you explicitly add in its options page, and only after you grant Chrome host permission for that host. Those requests reuse your browser's existing Jenkins login session (cookies). The extension does not send your data to any other server, and its author operates no backend that receives your data.

Authentication and security

  • •Optional passkeys are stored only as SHA-256 hashes, never in plain text.
  • •Biometric unlock uses the WebAuthn platform authenticator (for example macOS Touch ID or Windows Hello). The biometric credential never leaves your device and is never included in configuration exports.
  • •You can remove an environment's passkey, or disable biometric unlock, at any time in the options page.

Configuration import and export

You can export your environment configurations to a JSON file. That file contains environment names, Jenkins URLs, followed-job lists, and any passkey hashes. It does not contain biometric credentials. Importing a JSON file merges it into your local configuration. Treat an exported file as sensitive, since it names your Jenkins hosts.

The website

This site is a static page. It does not set cookies, run analytics, embed third-party trackers, or collect personal data. Standard web server logs from the site's hosting provider may exist as part of delivering the page; those are governed by the hosting provider's own practices.

Your choices and data deletion

  • •Remove a single environment's data via the options page.
  • •Export your configuration, or clear it, at any time.
  • •Uninstalling the extension from Chrome removes the data JenKit stores in chrome.storage.local. You can also clear it through Chrome's "Clear data" controls for the extension.

Children

JenKit is not directed at children under 16, and we do not knowingly collect data from them.

Changes to this policy

We may update this policy. Material changes will be reflected by an updated "Last updated" date at the top of this page.

Contact

For privacy questions or requests, contact us [email protected]