Privacy Policy: Sentry Bridge for Jira
1. Who we are
Sentry Bridge for Jira (the "App") is published by Integration Yard, the trade name of Dheeraj Kumar, an individual developer based in Washington, USA ("we", "us"). Contact: support@integrationyard.com.
2. Where the App runs
The App is built on Atlassian Forge. Its code runs on Atlassian's Forge platform and its data is stored in Forge storage associated with your Jira site. We do not operate our own servers or databases for the App, and App data is not copied to systems we control.
3. Data the App processes and stores
- Sentry credentials you enter (the internal integration client secret and auth token) are stored in Forge's encrypted secret storage for your site.
- Connection settings: Sentry organization slug, Sentry base URL, Sentry installation id, and options such as whether AI summaries are enabled.
- Project mappings: Sentry project to Jira project, issue type, priority and field templates.
- Link records: identifiers connecting each Sentry issue to its Jira work item (e.g. Sentry issue id, Jira issue id/key, sync state), plus short-lived de-duplication markers.
- Last result: a small diagnostic record of the most recent processing outcome (time, outcome, message, issue identifiers).
- Error details from Sentry webhooks (title, culprit, environment, release, level, counts, stack excerpt, link) are processed to create or update Jira work items. That content is written into your Jira work items, comments, remote links and an issue property; it is not otherwise retained by the App.
The App does not use cookies or analytics trackers and does not sell or share personal data.
4. Outside services
The App's only external network access is to Sentry (sentry.io and *.sentry.io), used to receive issue details and to update issue status in your Sentry organization. Sentry's handling of data is governed by your agreement with Sentry.
5. Optional AI summaries
AI summaries are off by default and can only be turned on by a Jira admin. When enabled, Sentry error details are sent to Atlassian-hosted Forge LLMs to generate a short summary. No third-party AI provider or API key is used by the App, and no additional egress is involved. Use of Forge LLMs is subject to Atlassian's terms.
6. Access
We (the developer) do not have access to your Jira data, your Sentry credentials, or the App's stored data as part of normal operation. Atlassian may provide us with limited operational logs and installation/licensing information through the Forge and Marketplace platforms. If you share information with us in a support request, we use it only to resolve that request.
7. Retention and deletion
App data remains in Forge storage while the App is installed. When the App is uninstalled, Atlassian deletes the App's Forge-stored data according to Forge's data retention policy. Content the App created in Jira (work items, comments) remains in Jira until you delete it. Support emails are kept only as long as needed to handle the request.
8. Data residency
Storage location follows Atlassian Forge's hosting and data residency capabilities for your site.
9. Security
Webhooks are authenticated with HMAC-SHA256 signatures, a timestamp window and an installation id check; credentials are kept in encrypted secret storage; configuration is restricted to admins. Report vulnerabilities as described on our security page.
10. Your rights
You may contact us to ask about data relating to you. Because App data lives in your Jira site's Forge storage, most data can be removed by uninstalling the App or deleting Jira content.
11. Changes
We may update this policy and will change the effective date above. Material changes will be noted on this page.