Privacy Policy

JiraPulse — Privacy Policy

WHAT THE EXTENSION STORES JiraPulse stores, in your browser only:

• your configuration: Jira server address, account email, JQL queries, column and notification preferences;
• your Jira API token or Personal Access Token;
• a cache of the issues last fetched from your Jira instance, and a record of which alerts have already been sent.

WHERE IT IS STORED By default everything is kept in chrome.storage.local — on your device. You can optionally enable syncing through your Google account, separately for settings and for the token; when enabled, that data is handled by Chrome Sync under Google's own privacy policy. Turning a consent off removes the data from Chrome Sync.

WHAT IS SENT AND WHERE JiraPulse communicates only with the Jira instance whose address you provide. It sends your API token in the Authorization header in order to read issues, field definitions and user display names. All requests are read-only.

The developer of JiraPulse receives no data whatsoever. There is no backend service, no proxy, no analytics and no telemetry. Nothing is sold or shared with third parties.

DELETING YOUR DATA Removing the extension from Chrome deletes all of its stored data. "Restore defaults" in the settings clears the configuration and the token without uninstalling.