Privacy Policy
Source of the published privacy page. The Marketplace distribution form requires a Privacy policy URL before an app can be shared or listed, and a URL that asks a reviewer to sign in counts as no privacy policy at all. The published copy of this page and its anonymous-load proof are recorded in docs/APP3-LISTING.md.
Business Days JQL for Jira adds four date functions to Jira's own JQL — businessDaysAgo, businessDaysFromNow, workingDaysAgo and workingDaysFromNow — which count in working days rather than calendar days, using one working week, one time zone and one holiday list that an administrator sets for the whole site.
The app runs entirely on Atlassian's own infrastructure using Atlassian Forge. It calls no external service and it declares no remote hostnames in its manifest. Nothing this app reads or writes leaves Atlassian's infrastructure, and the vendor has no server that your data passes through.
The calendar is stored in Forge storage, hosted by Atlassian inside your Atlassian cloud environment and scoped to your installation of this app.
The working week: which of the seven weekdays count as working days.
The time zone, as an IANA name (for example Europe/Kiev) or a fixed offset.
The holiday list: dates, one per line, as YYYY-MM-DD, up to 2000 of them.
A run record for the refresh: when it last ran, how many stored answers it checked,
how many it changed, how many it did not reach, and the text of the last error if there was one.
The date each of the four functions currently resolves to, for each argument and
operator combination a search has used. This is how a Forge JQL function returns a value to Jira's search at all.
The app stores no personal data. It does not store account IDs, email addresses, display names, avatars, work item content, project names, comments, attachments, work logs, credentials or tokens. It performs no analytics, telemetry or tracking of any kind.
A holiday date and a working-week choice are administrative configuration, not personal information about anybody.
The app reads only its own data. Its two Jira scopes are read:app-data:jira and write:app-data:jira, which grant access to the app's own stored answers and to nothing else — not work items, not projects, not users, not project configuration. The app requests no read:jira-work, no write:jira-work and no manage:jira-configuration scope, and uses no offline user impersonation.
When somebody runs a search, Jira asks the app for the date a function resolves to and then applies that date to the search itself. The app is never told which work items matched, and never sees the results.
Scope | What it is for |
|---|---|
| Store the site's working week, time zone and holiday list, plus the refresh run record, in Forge storage inside Atlassian |
| Read back the stored answers this app itself registered for its four JQL functions, so the config page can show which are current and which are stale |
| Write the date each function currently resolves to, and rewrite it when the calendar or the day changes |
The app's page lives under Apps and is a global page: the working week, time zone and holiday list apply to the whole site. Changing them changes the answer every search gets.
The calendar persists until somebody changes it in the app. Stored answers are rewritten as the calendar and the date move, and are removed by Atlassian when they are no longer referenced.
Uninstalling the app removes all of its stored data, because Forge storage is scoped to the installation. No work items are affected — the app never creates or edits one.
Forge storage follows your Atlassian cloud instance's data residency. The vendor cannot choose or change where it is held.
Questions about this policy, or a request to remove data: support@maxpetrov.pp.ua
Last updated: 11 September 2026.