Riskloop privacy policy

Last updated: 11 October 2026

Riskloop: Risk Register & Heat Map for Jira ("Riskloop") is published by Joao Duro De Matos, a sole proprietorship registered in Poland (NIP 9452193255), Ułanów 64D lok. 27, 31-460 Kraków, Poland.

The short version

Riskloop runs on Atlassian Forge and is eligible for the "Runs on Atlassian" programme. It has no servers of its own. Everything it stores stays in your Jira site, and it sends no data to us or to anyone else.

What Riskloop stores, and where

• Risk assessments (likelihood, impact, score, rating, treatment, mitigation, review date and the optional ISO 27001 fields) are saved as a property on the Jira issue they describe.
• Project settings (template, issue type, review interval) are saved as a property on the Jira project.
• Workflow rule: if an administrator enables the close rule, Riskloop adds its validator to the project's workflows. Nothing else is changed.

All of this lives in your Jira site, under Atlassian's hosting and data residency. Deleting the issue or project deletes the data. Uninstalling the app leaves your issues untouched.

What we receive

Nothing from your Jira content. Riskloop makes no calls outside Atlassian. Like every Marketplace partner, we can see the licensing and install information Atlassian provides to partners (for example which sites have the app installed and the licence tier) and the error logs Forge keeps for the app, which may contain issue keys. We use these only to support and improve Riskloop.

Personal data

Riskloop reads the names of Jira users (risk owners are issue assignees) only to show them on screen. It does not store or export them outside Jira. Atlassian processes your data under its own terms and privacy policy.

Contact

Questions about this policy: support@studiowebworks.com. User guide: support page.