Privacy Policy – Legal Hold Desk for Jira and Confluence

What Legal Hold Desk reads in Jira and Confluence, what it keeps inside your Atlassian site and for how long, and the one outside service it talks to — CourtListener, with the party names you watch.

Legal Hold Desk is built by Simplify on the Atlassian Forge platform. Its code and data run on Atlassian’s infrastructure, in your Atlassian site. Simplify has no server that receives your data.

What the app reads

  • Confluence pages and Jira work items in a matter’s scope — their versions, to compute a SHA-256 hash of each. Page and work item content is never stored: only hashes.
  • Teamwork Graph: who created, edited, commented on or was assigned what a matter holds, checked against Confluence and Jira.
  • Events in the spaces and projects in scope: a page trashed, moved or updated, an attachment trashed, a work item deleted or updated — to restore or record them.
  • Notice requests on the linked Jira Service Management desk and the custodians’ answers.
  • Pages a person opens are read as that person, with their permissions. The guard, reminders and the hourly court search have no person behind them and run as the app.

What the app writes in Jira and Confluence

  • A matter as a Jira work item, and notices as Jira Service Management requests to each custodian, with reminders.
  • Restores a page or attachment trashed under hold, as it was.
  • Snapshots attached to the matter, when a person asks.
  • The demo matter (pages, a matter and a sample court alert, all marked Demo), only when a person loads it.

What the app keeps (Forge storage, inside your Atlassian site)

  • Matters: key, title, state, scope and the log’s head — while the app is installed.
  • The hold log: one entry per action — who (an Atlassian account ID), what, when, and the hash chain. Never deleted by the app: it is the evidence. Releasing a hold keeps the log.
  • Objects under hold: version, SHA-256 hash and a changed flag — while the hold is active.
  • Custodians: account IDs, when their notice went out, was acknowledged and reminded, and a custodian’s own words when they object (at most 600 characters) — with the matter.
  • The last graph answer of a matter: account IDs and why each person is in scope — until Ask the graph again.
  • Court hits: each docket from the court search and its state.
  • Settings: watched party names, the last court search’s status, the demo’s state. Your CourtListener token sits in Forge’s secret store and is never shown again.

People: account IDs only

The app stores no names, e-mail addresses or avatars. People are kept as Atlassian account IDs; when a screen shows a person, the name is looked up in Jira at that moment, as the person viewing it, so Jira’s profile visibility applies and a closed account reads as Jira names it. The one text a person writes that the app keeps is a custodian’s objection to a notice (at most 600 characters), with the matter.

To have data about you removed, write to our Support Desk. The hold log keeps account IDs as evidence while a legal claim needs it (GDPR Art. 17(3)(e)); the site admin can export it and decide.

Outside services

  • CourtListener (www.courtlistener.com), the Free Law Project’s public register of US federal dockets. The app sends only the party names you watch, in one search an hour over the last 7 days, the one name you type into Try a name, and a call for today’s budget — with your own token. Never matter keys, custodians or content. Because party names leave the site, the app does not carry the Runs on Atlassian badge.
  • BODACC (bodacc-datadila.opendatasoft.com), France’s register of company notices: only one reachability call from the self-check, with no data.

Rovo

The app makes no model call of its own. Where Rovo, Atlassian’s AI, is on, your Rovo agent reads the complaint and proposes the scope; notices are the app’s plain template, which your agent may reword. The text stays inside Atlassian.

Data Access & Sharing

  • Your data is never shared with third parties by Simplify, and Simplify cannot access it.
  • The app’s logs record only what failed and an error’s name — never content, names or account IDs.

Uninstalling

When the app is uninstalled, Atlassian deletes its Forge storage under Atlassian’s Forge data retention — including the hold log, so export the hold log before uninstalling if you still need it. Matters, notices, pages and attachments stay in Jira and Confluence.

Updates to the Policy

We may update this privacy policy to reflect changes in the app or legal requirements. Any updates will be posted on this page and take effect immediately.

By using Legal Hold Desk, you agree to this privacy policy and our End User License Agreement (EULA). For privacy-related inquiries, contact us via our Support Desk.

For more information, please visit Atlassian’s Privacy Policy.