Security Policy — JQL Builder – Advanced Search
Last updated: 17 November 2026
This page describes how the Jira Cloud app JQL Builder – Advanced Search ("the app"), published by Andrey Kashukov ("we", "us"), is built and run securely, and how to report a security problem. What the app stores and why is covered separately in the Privacy Policy.
Architecture
- The app is built on Atlassian Forge and runs entirely on Atlassian's infrastructure. It is eligible for Atlassian's Runs on Atlassian programme.
- It has no servers of its own and declares no egress: no data is sent outside Atlassian, and there are no analytics, tracking or third-party services.
- Its user interface is built with Atlassian's UI Kit, which renders in a sandbox controlled by Jira. The few static pages it serves (the Copy buttons) run under Forge's Content Security Policy and load no external scripts.
Authentication and access control
- Sign-in and sessions are handled by Atlassian. The app never sees passwords, API tokens or other shared secrets.
- Every Jira request is made as the signed-in user, so the app can only read what that user is already allowed to see in Jira, and Jira's own permission checks apply to every call.
- Each user's saved and recent searches are stored under keys derived from the Atlassian account ID that Forge supplies with the request — never from data the browser sends — so one user cannot read or change another user's data.
- Changing site templates requires the Jira administrator permission. The app checks it with Jira on every change, not only by hiding the admin page.
- The app requests only the Jira permissions (scopes) it needs; each one is listed and explained on the Marketplace listing.
Data protection
- Data the app stores is held in Atlassian's Forge-hosted storage, which Atlassian encrypts at rest, isolates per Jira site and keeps in line with the site's data residency where Atlassian supports it. All traffic between the browser, Jira and Forge is encrypted in transit (TLS).
- The app stores the minimum it needs: a user's saved and recent searches, keyed by account ID. It stores no names, email addresses or avatars.
- Everything the app receives is validated and size-limited before it is stored (lengths, counts, nesting depth).
- Account IDs and stored content are never written to logs.
- Once a week the app reports the account IDs it stores to Atlassian's Personal data reporting API and deletes the data of any account Atlassian reports as closed.
- We (the vendor) have no access to customer data stored by the app.
Secure development and vulnerability management
- Every release is reviewed and passes automated checks before it is deployed: linting, type checking, an extensive unit test suite with enforced coverage, an end-to-end test suite against a live Jira site, and Forge's own manifest checks.
- Third-party packages come from a committed lockfile. Before each release the
packages that ship with the app are scanned with
npm audit; known vulnerabilities are fixed by upgrading, or by pinning a patched version of an indirect dependency, before the release goes out. - The app runs on Atlassian's current supported Node.js runtime and is kept on current versions of the Forge platform libraries.
Reporting a vulnerability
Please report suspected security issues privately by email to security@kashukov.com, with a description and steps to reproduce. Please do not disclose the issue publicly until it has been fixed.
- We acknowledge reports within 3 business days.
- We assess and fix confirmed vulnerabilities within the timeframes of Atlassian's Security Bug Fix Policy for Marketplace apps.
- We take part in Atlassian's Marketplace security processes, including vulnerabilities reported to us through Atlassian.
Security incidents
If a security incident affects customer data, we notify affected customers and Atlassian without undue delay, and within 72 hours of becoming aware of it, with what happened, what data was affected and what we are doing about it.
Changes
We update this page when the app's security practices change and revise the date above.
Contact
Andrey Kashukov — security@kashukov.com