Provider: Djoji LLC
Contact: hello@djoji.com
Effective date: 21 November 2026
This policy explains what the Packet Triage app does with data when it is installed on an Atlassian Jira site. It covers the app only. Atlassian's own products, including Jira, Jira Service Management and Rovo, are covered by Atlassian's privacy policy and your agreement with Atlassian.
When a packet capture file (.pcap, .pcapng, .cap, .dmp, or a gzip-compressed capture) is attached to a Jira issue, Packet Triage reads the file and produces a summary of network findings, such as refused connections, retransmissions, TLS handshake failures and DNS errors. The summary is shown on the issue. Other attachments are ignored.
The app may read:
The app asks Atlassian only for permission to read Jira issues and attachments, and to use its own app storage. It cannot create, edit or comment on issues.
The app stores data only in Forge hosted storage. The table below is the complete list of what it may store. A record that is not listed here is never stored.
| Record | Contents (at most) |
|---|---|
| Analysis status | State (queued, running, done, failed, too large, not a capture), a status message, the issue identifier, the attachment's file name and size, the analyzer version, the analysis time, and whether the analysis started automatically or from the Analyze button |
| Findings report | A trimmed summary of the analysis: counts, up to 100 findings and up to 150 network conversations. These may include IP addresses and ports, server names from TLS handshakes (SNI), DNS query names, TLS versions and cipher suites, timings, packet and byte counts, frame numbers, and the capture’s start time and duration |
| Issue index | The issue identifier and attachment identifier, used to list the captures on an issue |
| Sample run | If a user runs a built-in sample capture on an issue, the sample’s findings report, marked as a sample. Sample captures are synthetic files created by Djoji; they contain no customer data |
| Problem time window | An optional time range a user gives the Packet Triage agent, used to check whether the capture covers the reported problem |
The app never stores:
Stored findings may include IP addresses, DNS names and TLS server names. Depending on your situation and applicable law, these may be personal data, for example an IP address that identifies a person's device. File names of attachments may be stored as given, and may contain whatever the uploader typed.
The app never stores Atlassian account IDs or other user profile data. It checks whether the person viewing results may see the issue by asking Jira at the time of the request, and it stores nothing about that person.
Results are shown only on the Jira issue the capture is attached to. Before returning results, the app asks Jira, as the requesting user, whether that user can view the issue. If Jira says no, or the check cannot be completed, no results are returned.
The app includes a Rovo agent, "Packet Triage Analyst".
The app writes operational log entries to Atlassian's Forge logging, which Djoji can read to troubleshoot the app. They may contain:
They never contain capture contents, findings details, the text of agent questions, or account IDs.
If this policy changes, the updated version will be published at the same address with a new effective date.