Privacy Policy

Prism for Jira is developed and published by OpsShark. References to “we,” “us,” or “our” mean OpsShark. You can reach us at travis@opsshark.com.

This Privacy Policy describes how Prism for Jira collects, uses, stores, and protects information when you install or use the app in your Atlassian Jira or Jira Service Management environment. By installing the app, you agree to the practices described here.

Prism for Jira is built on the Atlassian Forge platform. This means the app runs entirely within Atlassian’s infrastructure. There are no OpsShark-operated servers, databases, or backends. All data the app creates or reads remains inside your Atlassian environment and is governed by Atlassian’s own privacy, security, and data residency policies.

4.1 Link Records — When an agent connects a Jira Service Management request to a Jira Software work item, Prism stores a record of that relationship (forward and reverse). This record contains only the issue keys of the two connected items and the Atlassian account ID of the agent who created the link. No personal details beyond the account ID are stored.

4.2 App Settings — Prism stores administrator-configured settings (e.g., which Jira spaces are enabled, whether progress bars or target dates are displayed). These settings contain no personal information.

4.3 Cached Issue Data — To reduce API calls and improve performance, Prism caches limited issue data: issue key, summary, status, issue type, progress percentage, children count, and target date. This data mirrors what is already in Jira and is refreshed automatically. No data beyond these fields is cached.

4.4 User Account ID — Atlassian provides the current user’s account ID when an agent performs a linking action. We store this solely for attribution (to record who linked a ticket) and do not use it for any other purpose.

4.5 What We Do Not Collect — We do not collect: passwords or credentials, payment or billing information, email addresses, names or personal profiles, browsing behavior, analytics, or any data unrelated to the linking and progress features of the app.

All data is stored using Forge Key-Value Storage (Forge KVS), a storage layer managed entirely by Atlassian. OpsShark has no direct access to this storage layer outside of what the Forge runtime allows during normal app execution. Data residency is determined by your Atlassian organization’s data residency settings, not by OpsShark.

We use the data solely to provide the features of Prism for Jira: displaying linked work items and their progress to agents and portal customers, applying your organization’s display settings to portal panels and issue panels, and attributing link creation to the correct agent for audit purposes.

We do not use your data for advertising, profiling, benchmarking against other customers, or any purpose unrelated to operating the app.

We do not sell, rent, or share your data with any third party. Because the app runs on Atlassian’s infrastructure, your data is subject to Atlassian’s data processing agreements as the sub-processor. No data flows to OpsShark’s own systems.

Data persists in Forge KVS for as long as the app is installed on your Atlassian site. When you uninstall Prism for Jira, Atlassian automatically deletes all Forge KVS data associated with the app. There is no additional step required to purge data. Atlassian’s data deletion policies govern the exact timing of permanent deletion from Atlassian’s infrastructure.

Depending on your jurisdiction, you may have rights including access to, correction of, or deletion of personal data we hold. Because Prism for Jira stores minimal personal data (limited to Atlassian account IDs) and all data is held within Atlassian’s infrastructure:

You can request an export of any stored data by contacting us at travis@opsshark.com. You can delete all app data permanently by uninstalling the app. You can exercise Atlassian-platform data rights through Atlassian’s own privacy channels.

Prism for Jira is a business productivity application not directed at children under the age of 13 (or the applicable age threshold in your jurisdiction). We do not knowingly collect personal information from children.

Security of the Forge platform infrastructure is the responsibility of Atlassian. OpsShark follows secure development practices for Forge apps, including respecting Jira’s native permission model so that users can only access data they are already authorized to see.

We may update this Privacy Policy from time to time. We will update the “Last Updated” date at the top of this document and, where required, notify you through the Atlassian Marketplace listing. Continued use of the app after changes constitutes acceptance of the updated policy.

This Privacy Policy is governed by the laws of the State of Texas, United States, without regard to conflict of law principles.

If you have questions or concerns about this Privacy Policy, please contact us at support@opsshark.com.