Data storage and security
Forge Custom Entities
Section titled “Forge Custom Entities”Residual is built on Atlassian Forge. All data is stored in Forge storage as Custom Entities, inside the Atlassian cloud of your site. There are five kinds of records:
| Entity | Content |
|---|---|
| Register | One per Jira project: configuration of the scales and the model version |
| Risk | Title, description, category, status, owner, review date, asset reference, linked Jira issue keys |
| Assessment | Inherent or residual rating, rationale, model version, person, time |
| Treatment | Title, owner, due date, status, evidence text and link |
| Audit event | Person, time, field, old value, new value |
Risks are the app’s own records. They are not Jira work items and add nothing to your Jira schema.
What data is stored
Section titled “What data is stored”- Risk texts: titles, descriptions, rationales, treatment and evidence texts.
- Ratings: probability, impact and, if turned on, detection.
- Atlassian account IDs of the people who create, own, assess or change risks and treatments.
Display names are looked up from Jira when a page is shown. They are not stored by the app.
No data outside Atlassian
Section titled “No data outside Atlassian”Residual makes no connections to systems outside Atlassian. MAKOA LLC runs no servers for the app and does not receive your data. PDF and CSV exports are generated in your browser.
Runs on Atlassian
Section titled “Runs on Atlassian”Because the app runs entirely on Atlassian infrastructure and has no egress, Residual is eligible for Atlassian’s Runs on Atlassian program.
- Security for the scopes of the app and why each is needed.
- Privacy Policy for retention and deletion.