Privacy policy — Recur for Jira
The short version
Recur does not send your data anywhere. It runs entirely on Atlassian Forge, inside Atlassian's infrastructure. The app declares no external network permissions, which Atlassian enforces at the platform level — it cannot make an outbound call even if it tried. The issues it creates are ordinary Jira issues on your own site.
What the app stores
Everything is stored in Forge app storage (Atlassian-hosted KVS) inside your own Atlassian tenant region.
| Data | Examples | Why |
|---|---|---|
| Templates | name, issue type, title/description templates with {{date}} and {{n}}, recurrence rule, timezone, pile-up policy |
to know what to create and when |
| Runtime state | next run time, run count, last issue key, held occurrences, position in the assignee rotation | scheduling |
| Run history | the last 20 runs: result (created/skipped/waiting/failed/paused/missed), issue key, reason for skips | so “why was there no issue” always has an answer |
| Run records | one per scheduled run: when it ran and the key of the issue it created | so a run delivered twice never creates its issue twice |
| Creator/owner references | Atlassian account ids of who created a template and who last changed it, who is assigned or in the rotation (display names are looked up from Jira when shown, not stored) | attribution and assignee selection |
| Licence state | whether the site's subscription was active when last seen, and when | so scheduled runs know whether to create issues |
Recur never stores issue content beyond what the template itself contains. It does not read or retain descriptions, comments, attachments, or email addresses.
What is never stored
- Issue descriptions or comments (beyond the template text you wrote)
- Email addresses
- IP addresses, usage analytics, or behavioural tracking
Who can see it
A project's templates and their run history are visible to people who can browse
that project. Template management is restricted to project administrators for their
own projects. Both are checked as the calling user (asUser) — never
assumed from the UI. Site-wide lists are visible to Jira administrators only.
Retention and deletion
- Deleting a template deletes its configuration, its run history and its run records.
- Held occurrences older than 30 days are dropped automatically.
- When the app is uninstalled, Atlassian deletes its Forge storage after 28 days.
Data residency
Whatever your Atlassian site's residency is. Recur adds no storage outside Forge and therefore introduces no additional residency considerations.
Sub-processors
None. Atlassian hosts everything; there is no other party involved.
Changes
Material changes to what is stored or where will be reflected here and in the Marketplace listing before they ship.
Contact
support@keelapps.atlassian.net — for questions about this policy, and for data access, correction or deletion requests.