Privacy Policy: Packet Triage for Jira Service Management

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.

What the app does

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.

Where processing happens

  • Packet Triage runs entirely on Atlassian Forge, Atlassian's app platform. Analysis runs in Forge functions operated by Atlassian.
  • The app has no servers of its own. It makes no network calls to any destination outside Atlassian, and it sends no data to Djoji or to any third party.
  • The app's data is kept in Forge hosted storage. Atlassian keeps this storage in the same location as your Jira site ("data residency") and moves it with your site if an administrator migrates it.
  • Stored data is read only by the app itself to show results. Djoji does not copy, export or browse it. Djoji can see the app's operational logs (described below), as Atlassian provides them to app developers.

What the app reads

The app may read:

  • capture files attached to Jira issues, when they are attached or when a user selects Analyze
  • basic issue information needed to show results on the right issue: the issue identifier, key and creation time

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.

What the app stores

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.

RecordContents (at most)
Analysis statusState (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 reportA 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 indexThe issue identifier and attachment identifier, used to list the captures on an issue
Sample runIf 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 windowAn optional time range a user gives the Packet Triage agent, used to check whether the capture covers the reported problem

The app never stores:

  • the capture file itself, or any copy of it
  • packet payloads, meaning the contents of network traffic
  • HTTP bodies
  • credential values. If the app detects a cleartext login (for example FTP or HTTP Basic authentication), it records only the protocol, the conversation and the frame number, never the user name or password
  • Atlassian account IDs, names or email addresses

Personal data

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.

Who can see the results

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 Packet Triage agent (Atlassian Rovo)

The app includes a Rovo agent, "Packet Triage Analyst".

  • Its answers are generated by Atlassian Rovo, not by Djoji.
  • When the agent needs facts, the app returns the stored findings for the issue being viewed, after the same permission check described above. The app does not re-read the capture file for the agent.
  • The agent is instructed to use only these findings, to state what is unknown, and never to reveal or ask for credentials.
  • Your question, the findings returned to Rovo, and Rovo's answer are processed by Atlassian under Atlassian's terms for Rovo.

Operational logs

The app writes operational log entries to Atlassian's Forge logging, which Djoji can read to troubleshoot the app. They may contain:

  • issue and attachment identifiers, the issue key and project key
  • attachment file names, sizes and types
  • processing status and error messages

They never contain capture contents, findings details, the text of agent questions, or account IDs.

Retention and deletion

  • When an attachment is deleted from an issue, the app deletes its stored status, findings and index entry for that attachment. Atlassian's documentation states that data an app deletes "is removed from primary storage and your app can no longer read it. Atlassian keeps a soft-deleted copy so the data can be restored after an accidental deletion, then destroys it at the end of the retention period".
  • When the app is uninstalled, Atlassian's documentation states: "Forge hosted storage retains data for 28 days after uninstallation." Reinstalling the app does not automatically restore earlier data.
  • While the app is installed, findings for an attachment remain until the attachment is deleted.

Your choices

  • To remove the findings for a capture, delete the capture attachment from the issue.
  • To remove all of the app's data, uninstall the app. Atlassian then handles the remaining data as described above.
  • Because the data stays in your Atlassian site, requests about personal data should go to your site administrator; contact hello@djoji.com if you need our help.
  • For questions or requests about this policy, contact hello@djoji.com.

Changes

If this policy changes, the updated version will be published at the same address with a new effective date.

Privacy Policy: Packet Triage for Jira Service Management | Djoji