Last updated: 9 November 2026
Qurio Q&A for Confluence ("Qurio", "the app") is a 100% Atlassian Forge app published on the Atlassian Marketplace by nxb labs. This statement explains what data the app processes, how and where it is stored, how it is secured, and how it is retained and deleted. For the full legal privacy terms see the Privacy Policy.
In short: Qurio runs entirely on Atlassian Forge. There is no external backend, no server we operate, and no outbound network calls. All data is stored in Forge Storage inside the customer's own Atlassian Cloud instance and is encrypted at rest by the Atlassian platform. Your content is never transmitted to nxb labs or to any third party outside Atlassian's platform.
Qurio only processes data that users create, or that Atlassian provides to the app in order to render its features:
| Data | Purpose |
|---|---|
| Questions, answers, tags, votes and "accepted answer" status | Core Q&A functionality that users explicitly enter. |
Atlassian accountId and public display name of the acting user |
To attribute questions/answers, compute statistics and expert rankings, and manage moderators and permissions. |
| Space key and page ID references | To scope content to a space and link questions back to their source page. |
| Group membership (read via the Confluence API, read only) | To enforce the optional "who can ask / answer" permission settings and moderator role. |
| In-app notifications | To notify a question's author or followers about new or accepted answers. |
| Per-macro and instance configuration (e.g. heading, scope, display mode, voting on/off) | To remember how each embedded macro and the instance is configured. |
Qurio does not collect email addresses, IP addresses,
passwords, tokens, payment information, or any special categories of
personal data. We store only the Atlassian accountId as the
identifier — never passwords, tokens, emails, or usernames — and we never
log credentials or secrets. The app uses no cookies, no
third-party analytics, and performs no AI/LLM processing
of your content.
Data is used solely to provide the app's functionality inside your Confluence instance. We do not sell, rent, share, or use your data for advertising, profiling, or any purpose unrelated to operating the app.
storage:app (its own data store),
read:confluence-user (resolve a display name for the
signed-in viewer) and read:confluence-groups (enforce the
who-can-ask/answer and moderator settings). It holds no write scope on
Confluence content and reads no page, space, or document bodies.
Content remains in Forge Storage until it is deleted through the app or until the app is uninstalled. When you uninstall Qurio, Atlassian removes the app's Forge Storage data according to the Forge platform lifecycle. Within the app you can delete data in two ways:
See the Privacy Policy for the controller / processor relationship and how to exercise data-subject rights.
external.fetch / egress
permissions. Data lives only in Forge Storage within the customer's
Atlassian Cloud instance (encrypted at rest; follows Atlassian data
residency).
npm audit) before a production deploy, following
a documented pre-release checklist.
npm audit on dependencies.
If you believe you have found a security vulnerability in Qurio, please report it privately — do not open a public GitHub issue.
Please give us a reasonable window to investigate and fix the issue before any public disclosure. We do not currently operate a paid bug-bounty program, but we credit reporters who responsibly disclose valid issues (with their consent). The latest version published on the Atlassian Marketplace is the supported version and receives security fixes.
We maintain a documented incident response plan. In the event of a confirmed security incident or critical vulnerability, we notify affected customers and Atlassian in line with Atlassian's Marketplace security policies.
For general questions about this app's data handling, contact nxb labs through our support portal or at support@martinnxb.atlassian.net. For security vulnerability reports, please use the private channel described in section 6 (Reporting a vulnerability) above.