Privacy Policy – DORA Desk for Jira
What DORA Desk reads in Jira and Confluence, what it keeps inside your Atlassian site, and why nothing leaves it — the app declares no outside host and carries the Runs on Atlassian badge.
Data Privacy & Security – DORA Desk for Jira
DORA Desk is built by Simplify on the Atlassian Forge platform. Its code and data run on Atlassian’s infrastructure, in your Atlassian site. The app’s manifest declares no outside host, so nothing leaves your Atlassian site through DORA Desk, and it carries Atlassian’s Runs on Atlassian badge. Simplify has no server that receives your data.
What the app reads
- Work items of the project: incidents, injects, findings and their comments — to classify incidents, time decisions and write the after-action report.
- Members of the groups in the project’s roles, when a project admin chooses people for drill roles in Settings.
- Confluence spaces a person picks for the demo scenario pages and the published after-action report.
- Everything a person opens or starts is read as that person, with their permissions. The 5-minute tick that delivers injects and sends deadline reminders has no person behind it and runs as the app.
What the app writes in Jira and Confluence
- Inject work items during a drill, assigned to their roles, and findings as work items.
- The after-action report as a Confluence page, when a person publishes it.
- The evidence package — JSON and PDF — attached to the year’s evidence work item, when a person builds it.
- The demo (project DRL, TEST scenario pages and a drill), only when a person starts it. Remove demo drill sends it to the trash, where it can be restored for 60 days.
What the app keeps (Forge storage, inside your Atlassian site)
- Incidents: the work item, when it was detected and classified, the account ID of who classified it, the classification answers, and when each report was marked sent.
- Drills: title, scenario, the organiser’s account ID, speed and times.
- Injects: for each one, its role, the account ID of the person playing it, when it landed, its work item, and when and how it was decided.
- The evidence log: one entry per decision, classification, report and package — who (an account ID), what, when — each chained by SHA-256 to the one before. The app does not delete entries: they are the evidence.
- Settings: legal name, LEI, kind of entity, competent authority, bank-holiday region, the weekend rule, the time zone and the people chosen for drill roles (their account IDs only: names are looked up in Jira when Settings is shown and never stored).
Rovo
The app makes no model call of its own. Where Rovo, Atlassian’s AI, is on, the DORA Desk agents can deliver the next inject, give a hint, record a finding, classify an incident and draft the initial report — each at a person’s request. They never decide for a participant, submit a report, un-major an incident or stop a clock. 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 work item text, decisions or account IDs.
- Everything the app keeps moves with your site under Atlassian’s data residency.
Uninstalling
When the app is uninstalled, Atlassian deletes its Forge storage under Atlassian’s Forge data retention — including the evidence log, so build the evidence package before uninstalling if you still need it. Work items, reports and attached packages 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.
Consent
By using DORA 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.