Privacy Policy

Last updated: February 2026

This Privacy Policy explains how the Delivery Trajectory app ("the app," "we," or "the developer") handles data. Delivery Trajectory is a Jira app that reads data from your Jira site and presents delivery projections (timelines and completion forecasts) based on your existing issues, their relationships, and your team's historical throughput.

Data the App Accesses

The app reads Jira data that you (the signed-in user) already have permission to view: issues and their fields, such as status, dates, estimates, links, and issue types. It reads the fields you configure it to use; if your configuration includes a field that identifies people, the app reads that information to group and label work. It uses this only to produce your projections and does not store it, so the user data the app reads, if any, is determined by your own configuration. Access is read-only: the app does not modify your Jira issues, and it cannot see anything you do not already have access to.

How Your Data Is Used

The Jira data the app reads is used solely to compute and display projections to you. The forecasting itself runs within your own browser session: the app reads your data, calculates the schedule and forecasts, and renders them on screen. The app's server-side component (running on Atlassian's Forge platform) handles only your configuration; it does not process your Jira issue data. Jira data is used only to produce the views you request and is not retained by the app after your session.

Data the App Stores

The only data the app stores is your configuration: for example, which Jira fields map to teams, how work size is estimated, which statuses count as done, dependency link types, and display colors. The configuration is designed not to require issue content or personal data; it holds the field names and settings you choose.

Configuration is stored in Atlassian's Forge hosted storage, scoped to your app installation and kept within Atlassian's infrastructure. It is not copied to any infrastructure operated by the developer.

Data Sharing and Disclosure

The app does not transmit your Jira data to developer-operated infrastructure or to any third-party service. It has no external backend and sends no data to analytics or tracking services. Your Jira data travels only between Atlassian's services and your own browser to render the views you request. (Because the app runs entirely on Atlassian's Forge platform, any external data transmission would have to be declared in the app's manifest, and none is.)

Your Choices and Rights

You control all stored configuration directly through the app's configuration page, where you can view and change it at any time. After uninstallation, configuration is retained and deleted according to Atlassian's Forge hosted-storage data lifecycle and retention practices. Because the app does not retain your Jira issue data and stores no personal data on developer-operated infrastructure, there is no additional personal data held by the developer to access, correct, or delete.

Data Security

The app runs on Atlassian's Forge platform and relies on Atlassian's security controls for data access and storage. Because the app transmits no data to external systems and stores only configuration within Atlassian's infrastructure, its data exposure is intentionally minimal.

Changes to This Policy

We may update this Privacy Policy from time to time. Any changes take effect when posted here, and the "Last updated" date above reflects the most recent revision. We encourage you to review this page periodically.

Contact

Questions about this policy or about how the app handles data can be sent to support@deliverytrajectory.com.