Privacy Policy — Sprint Goals Board for Jira

Last updated: October 15, 2026 · Publisher: Denis Simon Consulting · Contact: denis.simon.consulting@gmail.com

Sprint Goals Board for Jira (“the extension”) is a Chrome extension that displays Jira Cloud Scrum and Kanban boards as swimlanes grouped by Goal, directly within their Jira pages. This page explains which data it uses, where it goes and how to delete it.

The Sprint Planning references below apply only to the local development version loaded from dist/. This experimental feature is disabled in the distributed package.

Summary

• The extension reads your data directly from your Jira site, from your browser, using your own session.
• No data is automatically sent to the publisher: no publisher collection server, no analytics, no advertising, no sale of data.
• Your personal preferences stay in your browser. The board settings you change are saved in your Jira site, to be shared with your team.
• The extension writes to Jira only after an explicit action from you.

Data accessed

Only on the Jira Cloud site (*.atlassian.net) you choose to connect, and only after you approve Chrome's permission prompt:

• your Jira account (account ID and display name), for filters such as “My issues”;
• the Jira page language and, when needed, your Jira account language preference, to display the extension automatically in French, Spanish or, for other languages, English;
• boards, sprints, columns, quick filters and issue types, and whether you may edit the board (so that only people who can save its settings are offered to change them);
• issues in active sprints for Scrum, or in the board scope for Kanban: key, summary, status, type, priority, assignee, story points, labels, links, status history and the fields you choose to display;
• Atlassian Goals linked to issues or pinned to the sprint or Kanban board, read through your Atlassian site's gateway;
• card color JQL queries and their suggestions: text is sent to Jira for validation, value suggestions and matching issues, even before applying settings;
• in Sprint Planning, future sprints, their text objectives and issues, the board backlog and unfinished issues from active sprints;
• Jira issue type and priority icons.

The extension code exchanges this data with your authorized Jira site's APIs over HTTPS. Settings and changes saved in Jira are accessible according to your organization's permissions.

Issue views and transition forms are native Jira pages opened within the host Jira page. Their code, resources and any installed apps are provided by Jira, Atlassian and your organization, with their own data handling. The extension preserves their operation and does not fill in or submit their forms. It does not ask for or read passwords, tokens or cookie values: the browser uses your Jira session to authenticate requests.

Data stored in your browser

In Chrome local storage (chrome.storage.local), on your device only, never synced to your Google account:

• the address of the connected Jira site;
• the last board URL chosen in the launcher, for the next launch;
• the boards you added and a copy of their display settings: columns, swimlane order and colors, card fields, color rules, daily duration, etc.;
• interface preferences: selected language (Auto, Français, English or Español), filters, collapsed swimlanes, sidebar width, health panel open or closed, Sprint Goals button position and dismissed messages. The selected language is personal, applies across boards in this browser and is not saved to Jira;
• Sprint Planning drafts: objective text and order, selected issue keys and assignments, planned capacity and a baseline used to detect changes in Jira. They are removed when forgetting the board or disconnecting from the site;
• a log of the writes made to Jira from the extension (500 at most): date, site, action, issue key, before and after, outcome. It lets you check what the extension did;
• a technical setting for the Atlassian Goals gateway;
• the five latest technical loading measurements, recorded automatically: date, version, timings, counts and error categories, without issue content, URLs, JQL or Jira identifiers. They stay local, are replaced as further loads occur and are removed on disconnect. Their viewing dialog is not shown in the current Jira view.

What the extension writes to Jira

Only after your explicit action (drag and drop, form submission, button), in your Jira site and with your permissions:

• an issue status change (transition), with the transition form fields you fill in: comment, time spent, story points, etc.;
• an issue's rank (order);
• linking an issue to an Atlassian Goal, or unlinking it;
• the Goals pinned to the sprint, in a sprint property;
• after confirming Sprint Planning, a future sprint's objective text, additions of selected backlog issues and their objective assignments in the sprint property, visible to authorized Jira readers;
• board settings (issue type groups, swimlane order and colors, Goals pinned to the Kanban board, card fields, JQL color rules, daily…), each time you change them, in a board property, and only if you are allowed to edit that board. They contain display settings plus the name and account ID of the last person who changed them, visible to anyone who can view that board.

When you click it, the diagnostic tool can also write a test property on a sprint and delete it immediately.

Permissions requested

• Access to the Jira site you choose (https://your-site.atlassian.net/*), requested when you connect: to read and write what is described above. API calls from the extension code are limited to the authorized site; native Jira pages retain their own operation.
• Storage: to keep your settings in your browser.
• Active tab (activeTab): when you click the extension icon, to read the address of the displayed tab and recognize your Jira board without asking you to type it. Only selected board addresses are retained; the extension does not collect general browsing history.
• Jira integration (scripting): to display the Sprint Goals board on the authorized site when the board URL contains sprintGoals=1, and open native Jira issue views and forms. After a drag, it may select the intended transition in Jira to show its form. Without this parameter, Jira keeps its usual interface, with a plain "Sprint Goals" button on its boards. The extension does not automatically fill in or submit forms.
• Network header rule (declarativeNetRequestWithHostAccess): so that your site's Atlassian Goals gateway accepts the extension's requests. The rule only affects those requests, sent by the extension to your site.

Retention and deletion

After installation, a welcome tab asks for your Jira address; no site is authorized and no data is sent before your click. On launch, the launcher recognizes the current board or asks for its URL, requests site permission, then opens Jira. It does not read any issues. The board cannot run in a standalone extension tab: it requires the authorized Jira page.

• Disconnecting (Jira site → Sign out) deletes the site, the boards, their settings, local drafts, dismissed messages, loading measurements and the write log for that site, and removes Chrome's permission for the site. General interface preferences stay local.
• Uninstalling the extension deletes everything it stored in your browser.
• What was written to Jira (statuses, ranks, Goal links, sprint or board properties) stays in Jira, like any change made in Jira. It is governed by your organization and by Atlassian. A Jira administrator can delete the sprint or board properties.

Limited Use

The use of information received by the extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is used only for the extension's single purpose: displaying and updating your Jira board. It is not sold or used for advertising, creditworthiness or unrelated purposes. Exchanges with Jira and sharing with authorized Jira users support this purpose. The publisher has no automatic access to your Jira data. If you choose to send a report or information for a support request, it may be read to handle that request.

Changes

If this policy changes, this page will be updated along with its date.

Contact

For any question: denis.simon.consulting@gmail.com.