Security policy
Last updated: 10 November 2026
This policy applies to the Atlassian Marketplace app CQL Results – Search Tables for Confluence (the "App"), provided by Tsutsei Software, a brand of the sole trader identified on the Legal information page ("we").
Reporting a vulnerability
Send security issues to security@tsutsei-support.atlassian.net. Every message creates a tracked request in our support system. Please include the app, your site URL, steps to reproduce and the impact you expect. Do not include passwords, API tokens or customer data.
We confirm receipt within 2 business days, keep you informed about the fix and credit you in the release notes if you wish. Please give us reasonable time to release a fix before disclosing the issue publicly.
Architecture
- The App runs entirely on Atlassian Forge ("Runs on Atlassian"): Forge functions and UI Kit. No Forge Remote, no egress to external servers, no vendor-side servers or copies of customer data.
- The App stores nothing: it has no storage scope. A macro's settings (the query, columns) are part of the Confluence page like any macro's.
- Confluence is searched with the signed-in user's permissions (asUser), also in PDF and Word exports, so results list only what that user may see. The App is read-only: it cannot create, change or delete content.
- The App requests only the scopes its features need and never asks for passwords or API tokens.
- The App does not use AI or machine-learning models, and no customer data is processed by such models.
Secure development
- Every search runs as the signed-in user, so the App can only show what the user could find in Confluence search.
- Requests from the browser are validated (query length, page size, cursor); the space and page of a macro come from Forge's signed context; result links are used only when they point into the site; copied table cells are guarded against spreadsheet formula injection.
- Logs contain error messages only, never queries or results. Access to logs is limited to the developer (Forge developer console).
- Every change passes automated unit and end-to-end tests (including permission checks) before it is deployed to production.
- Dependencies are checked with
npm auditbefore every release; known vulnerabilities are fixed before deploying.
Access control
- Source code is in private GitHub repositories; GitHub and Atlassian accounts are protected with two-factor authentication.
- The developer workstation uses full-disk encryption, automatic operating system and security updates, a firewall and malware protection. Unsupported operating system versions are not used.
- Access to source code, the Forge developer console, the Marketplace partner account and the support site is reviewed every quarter.
Fixing vulnerabilities
Vulnerabilities are scored with CVSS and fixed within the deadlines of the Atlassian Marketplace security bug fix policy:
| Severity | CVSS | Fix released within |
|---|---|---|
| Critical | 9.0 – 10.0 | 10 days |
| High | 7.0 – 8.9 | 4 weeks |
| Medium | 4.0 – 6.9 | 12 weeks |
| Low | 0.1 – 3.9 | 25 weeks |
Forge deployments reach all installations within minutes, so customers do not need to update the App.
Security incidents
If a security incident may affect customer data, we report it to Atlassian within 24 hours and notify the admins of affected sites within 72 hours where possible. As a data processor under the GDPR, we inform controllers without undue delay. See also the privacy policy and the Data Processing Addendum.