Jira privacy policy

What this covers

This policy covers only the optional Jira Cloud connection in Butterneck. The rest of the product is covered by the Butterneck privacy policy. Connecting a site is your choice. Butterneck works without it.

What we access

When a partner admin connects a Jira Cloud site, Atlassian asks them to approve read and write access to Jira work, plus offline access so the connection can be refreshed.

We read the sites they grant, project names, and the issue key, summary, description, and status they pick. We do not browse Jira beyond that search.

What we store

The site name, site URL, and encrypted access and refresh tokens for that client. The link from a sandbox to an issue key, summary, and issue URL. If the app is tied to one Jira project, we store that project key and name.

Starting work copies the issue summary, description, and link into a sandbox chat so the assistant can act on it. That chat is stored like any other Butterneck conversation.

What we write back

When a linked chat finishes a turn, we comment on that Jira issue. The comment is a short line from the issue description and the preview link. It does not include the full chat. People who can see the issue can open the preview.

How long, and how to stop

Tokens stay until a partner disconnects the site. Unlinking a ticket stops future comments. The sandbox chat remains. Disconnecting the site deletes the stored tokens.

Email support@butterneck.com to ask about Jira data we hold.