Visible board data
Issue keys, summaries, statuses, estimates, due dates, issue types, and visible subtasks.
Executive summary
JiraSnap accesses only the information needed to detect participants, tickets, and subtasks that are in progress on the Jira board already open by the user. Its purpose is to generate text that the user can review and copy, for example into Google Chat, without requiring automatic publication to an external service owned by the extension.
1. Information the extension may process
Only the visible Jira information needed to perform its daily-plan workflow.
Detected participants
Names or visible identifiers shown in filters or on cards, used to build the daily summary.
Local preferences
Language settings and output options stored locally through the storage permission.
2. How that information is used
Functionally, narrowly, and only to support the extension’s purpose.
01
Local reading of the Jira DOM
The extension reads the current board view using DOM selectors, visible text, and accessibility signals.
02
Filtering and selection
Users can choose participants, exclude tickets, and refine the output before copying it.
03
Daily plan generation
The output is prepared for manual copying by the user; the extension does not automatically post it.
3. What JiraSnap is not intended to collect
A reduced scope compared with analytics, tracking, or account-based services.
- It does not require users to create a JiraSnap account.
- It does not include payment or signup flows in the current implementation.
- It does not need access to websites outside the Jira domain listed in
host_permissions. - It does not rely on a dedicated external API to build the board summary in its current version.
4. Permissions and rationale
| Permission | Why it is needed |
|---|---|
storage |
Stores popup preferences such as language and copied-output options. |
activeTab |
Works against the active Jira tab selected by the user. |
https://*.atlassian.net/* |
Restricts access to Jira-hosted pages relevant to the extension workflow. |
5. Retention and user control
Limited persistence
Persistent data is limited to local functional preferences. Board content is used to generate the view and copyable output.
User control
The user decides which participants to include, which tickets to remove, and when to copy the final result.
6. Security and limitations
JiraSnap depends on Jira’s visual and semantic DOM structure. If Atlassian changes that markup, some selectors may need updates. As a best practice, users should always review the generated preview before sharing it.
7. Changes to this policy
This policy may be updated if the extension’s permissions, architecture, or functional scope changes. The current version published with the project should be treated as the active reference.