01Summary
JiraPulse is a browser extension that displays your Jira issues in the toolbar. It is read-only: it never changes anything in Jira.
The extension has no backend of its own. There is no server operated by the developer, no proxy, no analytics and no telemetry. Your Jira credentials, your JQL queries and everything the extension reads from Jira stay in your browser profile, and the only remote system the extension talks to is the Jira instance whose address you entered yourself.
The developer never receives, sees or stores your data. This policy exists because Chrome Web Store requires every extension that handles user data to publish one — including extensions that only store data locally.
02Who is responsible
For the settings and credentials stored inside your own browser, you are in control — the developer has no access to them. For the issue data itself, the controller is your organisation, which operates the Jira instance.
| Extension | JiraPulse — Jira issues, SLA & alerts |
|---|---|
| Developer | Michał Skowroński (Pixels Riders), Poland |
| Contact | contact@PixelsRiders.com |
| Source code | github.com/sk0wr0n/JiraPulse |
03What data the extension handles
All of the following is stored in your browser profile through the extension storage API and is used exclusively to render the extension interface.
| Connection details | The address of your Jira instance, your account identifier (e-mail or username) and your API token or Personal Access Token. Needed to authenticate the requests you asked the extension to make. |
|---|---|
| Your configuration | JQL queries, list definitions, chosen columns and their widths, sort order, page size, notification triggers and thresholds, the colleagues you follow, theme, density and language. |
| Jira content shown in the popup | Issue fields returned by your queries — keys, summaries, statuses, priorities, assignees, due dates, SLA fields, comments and change history. Held in memory and in a short-lived cache so the popup opens instantly; refreshed on your schedule. |
| Operational counters | The number of API requests made in the last 60 minutes, shown in the popup footer so you can answer your Jira administrator. Local only, never transmitted. |
04What the extension does not do
- It does not send your data to the developer. There is no backend, no proxy and no third-party service in the path.
- It does not use analytics, telemetry, crash reporting or any usage tracking.
- It does not read the pages you browse. Host access is requested for a single domain — the Jira address you enter — not for all websites.
- It does not show advertising and does not build advertising or interest profiles.
- It does not sell, rent or share your data with anyone.
- It does not require an account with the developer, and there is nothing to register.
- It does not write to Jira. Every request is a read request.
05Where the data is stored
By default everything is stored locally on your device, in the storage area of your browser profile. Nothing leaves the device except the requests sent to your Jira instance.
Synchronising your configuration through your browser account is optional and off by default. It is split into two separate consents: you can sync your settings while keeping your API token strictly local. If you enable syncing, the synced values travel through your browser vendor’s account infrastructure (for Chrome, Google), and that transfer is governed by the vendor’s own privacy policy.
You can export your configuration to a JSON file and import it elsewhere. An exported file may contain your credentials — treat it like a password file.
06Where data is sent
| Your Jira instance | Every API call goes to the address you configured, over HTTPS, authenticated with your own token. Jira Cloud uses REST v3 with an API token; Jira Data Center and Server use REST v2 with a Personal Access Token. An optional separate address can be configured for links if your instance sits behind a different gateway. |
|---|---|
| Your browser account (optional) | Only if you turn on synchronisation, and only the values you consented to sync. |
| Anyone else | Never. |
07Permissions and why they are needed
The extension requests the narrowest set of permissions its features need. Nothing is requested "just in case".
| storage | To keep your settings and credentials in the browser profile between sessions. |
|---|---|
| alarms | To run the background refresh on the interval you choose (5 minutes by default). |
| notifications | To show desktop alerts for new issues, approaching SLA or due dates and changes in your issues. |
| Host access to your Jira domain | To call the Jira REST API of the single instance you entered. Granted per domain, not for all sites. |
The exact permission list for the version you have installed is always visible on the Chrome Web Store listing and in your browser’s extension details.
08Retention and deletion
- Locally stored data lives until you delete it. Removing the extension removes its local storage together with it.
- If you enabled synchronisation, clear the synced data from the extension options before uninstalling, or remove it through your browser account.
- Cached issue data is short-lived and is replaced on every refresh cycle.
- You can revoke the extension’s access at any time by revoking the API token or Personal Access Token in your Atlassian account — the extension stops working immediately and keeps no copy of anything server-side, because there is no server.
09Security
- All traffic to Jira uses HTTPS. The extension refuses to send credentials over an unencrypted connection.
- Credentials are stored through the browser extension storage API, isolated from web pages and from other extensions.
- The extension is read-only, so a compromised token cannot be used through JiraPulse to modify anything in Jira.
- Use a token scoped to the minimum your account needs, and rotate it if you suspect exposure.
- No security measure is absolute. If you find a vulnerability, report it to contact@PixelsRiders.com and it will be handled promptly.
10Your rights
Because the developer holds no copy of your data, requests for access, correction, export or erasure cannot be answered by the developer — there is nothing on our side to act on. You exercise these rights directly:
- Over the local copy — in the extension options, or by removing the extension.
- Over the synced copy — in the extension options, or through your browser account.
- Over the issue data itself — with your organisation, which operates the Jira instance and is its controller under the GDPR.
If you believe the extension behaves differently from what is described here, write to contact@PixelsRiders.com.
11Children
JiraPulse is a workplace tool aimed at professional users. It is not directed at children and collects nothing from them.
12Limited Use disclosure
The use of information received from Google APIs, and any other user data handled by JiraPulse, adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
- Allowed use — data is used only to provide and improve the extension’s single, user-facing purpose: displaying and monitoring your Jira issues.
- Allowed transfer — no user data is transferred to anyone. The only transmission is between your browser and the Jira instance you configured.
- Prohibited advertising — user data is never used or transferred for advertising, retargeting or interest-based profiling.
- Prohibited human interaction — no human, including the developer, can read your data. It never leaves your device except toward your own Jira.
13Changes to this policy
This page is the canonical version and is publicly reachable without logging in. Any change is published here with an updated date.
If a future version of the extension changes how data is handled — new data, a new destination, a new permission — the change will be disclosed proactively inside the extension before the new behaviour starts, and it will require your explicit consent. Chrome Web Store policy requires this, and so does basic decency.
14Contact
Questions, concerns or privacy requests: contact@PixelsRiders.com. Every message gets an answer.