Security & data

Issue Repeater is built to keep your data where it belongs — inside Atlassian.

Runs on Atlassian

Issue Repeater is an Atlassian Forge app. All of its code and storage run on Atlassian's own infrastructure. There are no external servers operated by Runson Labs and no data egress — your Jira data is never sent to a third party or outside the Atlassian platform.

What data we process

• The schedule configuration you create — templates, recurrence rules, and settings.
• Issue metadata needed to create issues on your behalf (space, issue type, field values, and the keys of issues created).
• A run log of recent executions per schedule.

This data is stored in Atlassian's Forge storage, isolated per installation (per site). We do not build cross-tenant profiles and we do not collect analytics that identify your users.

Access & permissions

The app requests the minimum scopes required to do its job: reading Jira space, field and user metadata; creating issues; app storage; and reporting stored account IDs to Atlassian's personal data service. Scheduled runs act as the app (Atlassian's Forge app identity), which is why created issues are attributed to the app in the audit trail.

The app follows your Jira permissions. Because scheduled runs act as the app, every schedule is checked against the permissions of the person creating or changing it:

• People can only target spaces where they can create issues. Setting an assignee needs Assign Issues; making someone else the reporter needs Modify Reporter.
• People only see schedules in spaces they can browse.
• Only a schedule's creator, that space's admins, and Jira admins can edit, run, pause or delete it.

Reliability

The engine is designed around catch-up windowing and idempotency so that recurring issues are created reliably — never missing a run and never creating a duplicate.

Reporting an issue

Found a security concern? Please email support@runsonlabs.com and we'll respond promptly.