Last updated 16 August 2026
There is no server of ours. This app runs entirely inside Atlassian's own infrastructure on the Forge platform. Nothing it reads or writes is sent anywhere else, because there is nowhere else for it to go.
The app creates Jira issues on a schedule you set. To do that it holds your schedules: the summary and description you typed, the project and issue type you chose, the time and timezone, and a record of what it last created so it does not create it twice.
That is stored in Forge storage, which is Atlassian's, scoped to your installation, and deleted when you uninstall the app.
| Permission | What it is for |
|---|---|
| read:jira-work | To list your projects and their issue types, so the setup form can offer real choices instead of guessing. It is not used to read the contents of your issues. |
| write:jira-work | To create the recurring issue. That is the job. |
| storage:app | To remember your schedules and what has already run. |
There is no permission here for user directories, attachments, or site administration, and none is requested.
The app does not collect personal data. It does not read your users, your profiles, or your issue contents. The only text it stores is text you typed into it yourself when setting up a schedule.
Issues it creates are reported by the app rather than by a person, and it does not assign work to anyone unless you configure it to.
None. No analytics, no tracking pixels, no third-party scripts, no telemetry back to us. Atlassian collects its own platform-level operational metrics about app invocations, as it does for every Forge app, and that is described in Atlassian's own privacy policy.
Inside your Atlassian instance, in the region Atlassian hosts it in. The app makes no outbound network calls to any other host. It is eligible for Atlassian's Runs on Atlassian programme, which is their check for exactly this: that an app stores its data on Atlassian infrastructure and does not egress.
Uninstall the app. Its storage goes with it. Issues it already created are ordinary Jira issues and stay in your project, where you can delete them like any other.
Support requests reach us by email. If you send us a description of a problem, we hold that email in order to answer it, and for no other purpose. We do not add support contacts to any mailing list.
If this policy changes, the date at the top changes with it. If a change ever made the statement at the top of this page untrue, that would be a different product, and it would be said plainly here and on the listing rather than buried in a revision.