Privacy policy

Jira ticket to prompt, a Google Chrome extension.
Last updated: October 15, 2026.

Jira ticket to prompt runs in your browser. When you open it on a Jira ticket, it reads that ticket, builds a text prompt for a coding assistant, and shows attachment previews. It copies the prompt or an image only after you click Copy.

Ticket content is not sent to the developer of this extension. There is no developer server, account, analytics, advertising, or telemetry. The only network requests are to your Jira Cloud site and to Atlassian’s media host, which already stores that ticket’s attachments.

Who this policy covers

This policy describes the Chrome extension named Jira ticket to prompt (the “extension”), published by Shopifyexpert.xyz. It applies to the extension distributed through the Chrome Web Store and to the copy you install in Chrome. It does not describe Jira, Atlassian, or any coding assistant you later paste a prompt into. Those services have their own policies.

The same disclosures appear in the extension’s Privacy tab. The link in that tab and the privacy-policy URL on the Chrome Web Store listing both point here.

Single purpose

The extension converts the Jira ticket you are viewing into a structured text prompt, and lets you copy that prompt or the ticket’s image attachments. It uses Jira data only for that purpose.

Information the extension uses

The extension reads ticket content only on a Jira Cloud ticket, when you open the popup or, if you turn auto-open on, when you move to another Jira ticket. It does not read Confluence pages (/wiki) or Jira settings pages.

Jira ticket content

From the ticket page, the extension reads:

the issue key and title
description and acceptance criteria
fields shown on the ticket, including type, status, priority, project, labels, components, versions, sprint, epic or parent, dates, story points, environment, and resolution, when those fields are present
comments and replies, including comments that are collapsed on the page
links in the ticket
the attachment list (file names and the Jira links needed to download them)

Assignee, reporter, and comment-author profile names are not extracted as their own fields. A name, email address, or other personal detail that someone wrote in the title, description, a comment, or another copied field is included in the prompt as written. Ticket text can contain confidential business information.

To include collapsed comments, the extension activates the page’s “Show more” and “View replies” controls. It does not edit the ticket, post comments, or change fields, status, or workflow transitions.

Attachments

While the popup is open, the extension downloads previews from your Jira site: up to 20 attachments, two at a time. Image previews are limited to 512 KB each. For .txt, .md, and .json files, it reads only the first 4 KB. A full-size image, up to 12 MB, is downloaded only when you click Copy image.

The open button does not upload anything. It opens that attachment’s Jira URL in a new browser tab.

The address of the current tab

When you open the popup, the extension reads the address of that tab only to decide whether it is a Jira ticket. If it is not, the extension does not read the page and does not save the address. It does not record a browsing history. In the background it only receives addresses for Jira Cloud pages it is allowed to read, and it uses those only to notice a move between tickets when auto-open is on.

Settings you choose

Two settings are saved on your device:

Custom instructions, the optional text you type so it can be added to the prompt.
Auto-open, a yes/no preference. It is off until you turn it on.

If your custom instructions include personal information, that text is stored with the setting and included in the prompt. Ticket content is not stored.

Information the extension does not collect

The developer does not receive, and the extension does not transmit to the developer or to any analytics, advertising, or crash-reporting service:

ticket text, comments, or attachments
custom instructions or the auto-open setting
clipboard contents
cookies, passwords, access tokens, or other credentials
browsing history, location, contacts, or data from sites other than the Jira Cloud pages described above

The extension does not use Google APIs and does not receive Google account data from Google. It does not create an account with the developer. It does not use chrome.storage.sync, so these settings are not synced through your Google account by the extension.

Where information goes

Your browser. The prompt is built locally in the extension. Ticket content stays in memory while the popup is open. It is not written to the developer’s servers, because there are none.

Your Jira site and Atlassian’s media host. The extension requests attachment metadata and file bytes from the Jira Cloud site you are already signed in to (https://*.atlassian.net or https://*.jira.com). Jira may redirect a file download to https://api.media.atlassian.com, which is Atlassian’s host for attachment files. The extension does not upload ticket content to Atlassian or to anyone else. Requests to any other host are blocked or discarded.

Your clipboard, only when you click. Opening the popup does not copy anything. Copy prompt writes the prompt to the system clipboard. Copy image writes that image to the clipboard. Other applications and clipboard-history tools on your device can then read what you copied. The extension does not read the clipboard.

Tools you paste into. If you paste the prompt or image into a coding assistant, chat, or editor, that transfer is your action and is governed by that product’s policy. This extension does not send the prompt there itself.

Before a URL is placed in the prompt, credentials are removed from it. Atlassian media URLs, live Jira attachment download URLs, and blob:, data:, and javascript: URLs are left out; attachments are listed by name. Query parameters that look like secrets (including tokens, signatures, and similar values) are removed. A secret typed in the ticket as ordinary text is not detected and remains in the prompt.

What is stored, and for how long

Custom instructions and the auto-open preference are stored in Chrome’s local extension storage on that device (chrome.storage.local). They remain until you change them, clear the extension’s data, or uninstall the extension. Chrome removes that storage when you uninstall.

Ticket content, prompts, and attachment bytes are not stored by the extension. They are discarded when you close the popup, except for what you have copied to the clipboard or pasted elsewhere yourself. A short-lived offscreen page may be created only to place an image on the clipboard after you click Copy image, and it is closed after a few seconds.

The developer has no copy of your ticket or settings, and so has nothing to delete on a server. To remove the local settings, clear the custom instructions in the popup, turn auto-open off, or uninstall the extension.

Permissions

Chrome shows these permissions because the extension needs them for the purpose above:

Active tab and scripting. Read the Jira ticket in the tab where you opened the popup, using the extension’s own bundled script. No remote code is downloaded or run.
Storage. Save custom instructions and the auto-open setting on the device.
Clipboard. Write the prompt or an image when you click Copy.
Offscreen documents. A brief fallback used only to write an image to the clipboard.
Jira Cloud sites (*.atlassian.net and *.jira.com). Read the ticket you are viewing, notice when you open another ticket, and download that ticket’s attachments with your existing Jira session.
api.media.atlassian.com. Receive attachment bytes when Jira redirects the download there.

Cookies and sign-in

The extension does not read, store, or log cookies, passwords, or access tokens. It has no access to Chrome’s cookie store. Downloads of attachments from your Jira site use the Jira session the browser already has, so Jira can authorize the download. Those session cookies are not sent to api.media.atlassian.com. On the fallback path that runs inside the Jira tab, cookies are sent only to that Jira site, not to a redirected address.

Selling and sharing

User data is not sold. It is not transferred to third parties, except in the ways this policy already describes: your browser requests attachment files from your own Jira site and from Atlassian’s media host, and your clipboard receives content when you click Copy. Data is not used for advertising, credit, lending, or any purpose unrelated to building and copying the prompt. Data is not used to determine creditworthiness.

Children

The extension is a tool for people who use Jira. It is not directed at children under 13, and the developer does not knowingly collect personal information from children.

Changes

If this policy changes, the updated version will be posted at this same URL with a new “Last updated” date. The Chrome Web Store listing will continue to link here.

Contact

Questions about this policy or the extension: contact@shopifyexpert.xyz.

Use the email address shown on the Chrome Web Store listing for this extension. Because ticket content never reaches the developer, a request to the developer cannot retrieve, correct, or delete a copy of a Jira ticket. Access to the ticket itself is controlled by your Jira site administrator.