Privacy policy

Recurring Work Items for Jira — last updated 13 August 2026.

We do not receive your data

Recurring Work Items for Jira is an Atlassian Forge app. It runs entirely on Atlassian's own infrastructure, inside your Atlassian Cloud site. It has no servers of ours, no external database, and no network access to anywhere outside Atlassian — the app's manifest declares 0 external domains, which is why it carries the Runs on Atlassian badge. Nothing you enter into it, and nothing it reads from Jira, is ever transmitted to us or to any third party.

What the app stores, and where

To do its job the app keeps, in Atlassian-hosted app storage inside your own site:

• the recurrence rules you create — their schedules, and the issue templates you fill in, which may contain a reporter's and an assignee's Atlassian account ID;
• your project's working-day and holiday settings;
• a history of each scheduled run, recording when it ran, what issue it created, and any warning or failure.

It reads project, issue-type, field, user and issue-status information from Jira as needed to present the rule editor and to create issues.

Data residency

Because all storage is Atlassian's app storage, your data stays wherever your Atlassian site's data resides, and follows the same data-residency guarantees Atlassian gives the host product.

Retention and deletion

Rules and settings persist until you delete them. Run history records expire automatically 180 days after they are written. Uninstalling the app removes its stored data with the installation, per Atlassian's own app-data lifecycle.

Analytics

None. The app collects no telemetry and sends no usage data anywhere.

The assistant on this website

This documentation site — and only this site, not the app — has a chat panel that answers questions about the product. It is a feature of the website. It is not part of the Forge app, it has no connection to your Atlassian site, and nothing you type into it can reach, read or change your Jira data. Everything above about the app remains true whether you use it or not.

When you send a question, three things go to OpenRouter, which routes it to the model that writes the answer (~deepseek/deepseek-v4-flash-latest): your question, the earlier questions and answers in that same conversation, and the text of the pages of this site. Nothing else — there is no account, no cookie and no identifier attached to it. The request is restricted to model providers that do not retain or train on what is sent to them.

• We keep no transcripts. The conversation lives in your own browser, in session storage, and is gone when you close the tab. Our server writes only the fact that a question was answered and how many tokens it cost — not the question, and not the answer.
• Your IP address is used to count requests against a per-minute limit, so that one visitor cannot exhaust the assistant for everyone. It goes no further: it is not written to our logs, not attached to the question, and never sent to the model.
• Do not paste anything confidential into it. It answers from published documentation, so it never needs your issue keys, your project data or any credential.
• It can be wrong. It is a language model reading these pages. The pages are the authority — every answer links to the one it came from.

The permissions the app asks for

Jira asks an administrator to consent to these at install. Each is listed with what stops working without it:

The app never asks anyone for a token, a password or any credential. All access to Jira goes through Forge's own authenticated bridge, using the scopes consented to at install.

Contact

support@tiraisoft.com. See Support.