Privacy Policy — JQL Builder – Advanced Search
Last updated: 7 November 2026
This policy describes how the Jira Cloud app JQL Builder – Advanced Search ("the app"), published by Andrey Kashukov ("we", "us"), handles data. The app is built on Atlassian Forge and runs entirely on Atlassian's infrastructure.
Summary
- The app sends no data outside Atlassian. It has no external servers, no analytics, no tracking and no third-party services.
- We (the vendor) cannot see your Jira content or anything the app stores.
- The app stores only what you save in it: your saved searches and recent searches, kept per user in Atlassian's Forge storage, and the site templates a Jira administrator publishes for everyone.
What the app accesses
The app reads Jira data through Atlassian's APIs as the signed-in user, so it only ever sees what that user is already permitted to see: projects, fields, statuses, issue types, priorities, resolutions, boards and sprints, the filters the user owns, has starred or can see, users (for the user pickers), value and work-item suggestions, and the work items matching a query the user runs. This data is shown on screen and is not stored by the app.
The app writes to Jira only when the user explicitly chooses Save as Jira filter, which creates a normal Jira filter owned by that user. Before a site template is changed, the app asks Jira whether the user holds the Jira administrator permission.
What the app stores
In Atlassian Forge storage (server side), per user:
| Data | Contents | Limit |
|---|---|---|
| Saved searches and custom templates | name, optional description, tags, the form state (field values, operators, sort order) and the JQL it produces | 20 per user |
| Recent searches | the JQL text of the last searches the user ran | 10 per user |
| Saved-list fingerprint | a short checksum of the user's saved searches, so the app can tell whether its cached copy is current | 1 per user |
Each record is keyed by the user's Atlassian account ID, and only that user can
read or change it. Field values can include other users' account IDs where a
user picked someone in a user field (for example, assignee) — the account ID
only; the app stores no names, email addresses or avatars. A backup of the
saved searches (Back up saved searches) is JSON shown on screen for the
user to copy; the app does not keep a copy.
In Atlassian Forge storage, for the whole site:
| Data | Contents | Limit |
|---|---|---|
| Site templates | name, optional description, tags and a JQL query, published by a Jira administrator on the app's admin page and listed for every user | 30 per site |
Site templates are not linked to any account: the app does not record who
published them, and it refuses a template query that names a person by
account ID (a template is written with currentUser() or a group instead).
Stored by Jira, not by the app: the settings of a JQL Builder – Search overview dashboard gadget (its title, query and chart choice) are kept with the dashboard, like any gadget's settings, and are removed with it.
In the user's own browser (localStorage), never sent anywhere: interface preferences (pinned fields, remembered operators, the custom fields added to the form, chosen result columns, page size, the chosen language, dismissed tips), an auto-saved draft of the current form (discarded after 7 days), and short-lived caches of the saved/recent lists and of the site's option lists (projects, sprints, statuses and similar, and which fields the site supports). Clearing the browser's site data removes them.
Where data is held and how it is protected
Server-side data is held in Atlassian's Forge-hosted storage, which Atlassian operates, encrypts at rest and isolates per Jira site. Data residency follows the residency of the host Jira site where Atlassian supports it for Forge storage. How the app is secured, and how to report a security issue, is described in the Security Policy.
Retention and deletion
- Users can delete their saved searches individually and clear their recent searches at any time from within the app. Jira administrators can delete site templates on the app's admin page.
- Closed Atlassian accounts: the app reports the account IDs it stores to Atlassian's Personal data reporting API once a week, and deletes all stored data for any account Atlassian reports as closed.
- Uninstalling the app: Atlassian deletes the app's Forge storage for that site; per Atlassian's data lifecycle, the data is soft-deleted and retained for up to 28 days before permanent disposal.
Personal data and your rights
The only personal data the app processes is the Atlassian account ID used to separate each user's data, and any account IDs a user enters as search values. The site's organisation (the customer) is the data controller; the app acts on its behalf. Because we have no access to stored data, requests to access or erase data are fulfilled through the app itself, by uninstalling it, or through Atlassian. For questions, contact us below.
Changes
We will update this page when the app's data handling changes and revise the date above.
Contact
Andrey Kashukov — support@kashukov.com