Data and privacy
- Atlassian hosting. RepeatWise’s app services run on Atlassian Forge. It makes no calls to outside servers and uses no analytics or email service.
- What is stored (in Atlassian-hosted Forge SQL): schedules (name, project, rule, time zone, holiday calendar, and chaining and sprint options); issue templates (summary, description, labels, sub-task text, assignees and custom fields); occurrence and candidate logs; retry leases; a work checkpoint containing a template copy, created issue keys, warnings and errors after the parent issue is created; dispatch retry bookkeeping; the time of the last owner notification per schedule; schedule audit actions (who, when, and what changed, in words); your review reminder choice; and administrator settings and licence state. Template and error text can contain personal data.
- People. Atlassian account ids are stored for schedule owners, template assignees (including sub-tasks and user-type custom fields), the account that last sent an issue create, schedule audit actors and review reminder choices. Names, email addresses and avatars are not stored as separate identity fields. Account ids are removed from stored error text; Forge logs can contain error sentences after redaction.
- Owner notifications. When a schedule stops with an error, RepeatWise asks Jira to notify the schedule’s owner about the last issue the schedule created (Jira’s issue notify API, sent as the app, to the owner only; Jira delivers it only if the owner can see that issue). Jira sends the message itself; RepeatWise does not use an email service, and no data leaves Atlassian. The message contains the schedule name, the stored error text and the time. Only the time of the last notification is stored (no content). Administrators can turn it off.
- Holiday data is built into the app; looking up holidays sends nothing anywhere. See Third-party data below.
- Created issues are normal Jira issues. Each has an issue property
recurrence(scheduleId,occurrence,plannedAt, andsubtaskfor sub-tasks only) for JQL. - Browser storage. The app stores these values in your browser and sends them nowhere: in
localStorage,repeatwise.lastProject(your last selected project key) andrepeatwise.quickMode.<your account id>(Quick Start mode); insessionStorage,rw-attention-dismissed:<account id>andrw-attention-announced:<account id>(whether the attention banner was dismissed or announced this session). Two keys contain your Atlassian account id. - CSV export. Exports are built in your browser from data you can already see, then saved to your device or copied to your clipboard. RepeatWise sends the file nowhere and stores no copy. Once saved, the file is under your control.
- Feedback. “Rate RepeatWise” opens the Marketplace in a new tab. “Suggest a feature” and “Report a problem” open your own email app with a template (app version only); you choose whether to send it. RepeatWise sends no email and collects no feedback itself.
- Rovo. When you use the recurrence suggestion action, it searches recent Jira issue keys, summaries, creation times and recurrence properties with your Jira access. RepeatWise does not save those search results in Forge SQL; its response enters the Rovo conversation. You can also create and list schedules through Rovo. Listing returns visible schedule details, including names and project keys, to the conversation. Creation returns the new schedule’s name, project key, issue type name and timing details to the conversation, and stores the schedule in Forge SQL through the same save path as the UI. Rovo conversations are processed and kept by Atlassian under Atlassian’s own terms; RepeatWise does not receive or store them.
- Retention. Hourly maintenance deletes occurrence (once final) and candidate rows older than 24 months, schedule audit rows older than 24 months once their schedule is deleted (the history of an existing schedule is kept while it exists), and review reminder choices after 24 months without an update. A choice older than 12 months is refreshed when you check the review prompt, so “never ask” remains in effect while you are active. The job deletes in batches; deletion may happen after the threshold if it is paused or interrupted. A day after an occurrence is final (created, failed or skipped), its work checkpoint (including the template copy and account ids) and its dispatch row (account id) are deleted, and a service request dispatch record keeps only the fact that the issue was raised as a request; what remains of them is deleted with the occurrence after 24 months. An occurrence still in progress is never purged: if it never settles, its work checkpoint and dispatch rows stay until the schedule is saved or deleted. Schedules, templates and settings have no age-based purge. Expired leases and orphaned rows (including owner notification rows of deleted schedules) are also removed.
- Uninstalling. RepeatWise data lives in Forge hosted storage. Atlassian keeps it for 28 days after the app is uninstalled, then deletes it; if you reinstall within that time and want your schedules back, contact support within 21 days of uninstalling so the data can be re-linked with your consent (Forge storage reference). Scheduled runs stop when the app is uninstalled. Deleting a schedule removes its schedule, template, candidate log, work checkpoint and dispatch rows; its occurrence log and schedule audit remain until the 24-month retention purge. Created Jira issues and their properties remain.
- Scopes. The manifest requests Jira work read and write, Jira Software sprint read and write, board read and Jira project read (for the board picker), Jira user read, and Jira Service Management request read and write (to list request types and raise service requests as the schedule owner). It requests no external scope.
Third-party data
Public holiday data comes from date-holidays. Its LICENSE credits Wikipedia and other community sources and calls the data CC BY-SA 3.0 and the code ISC. Its package.json calls the package (ISC AND CC-BY-3.0).
Public holiday data comes from the open-source date-holidays package by commenthol, based on Wikipedia articles, and is used unmodified under the Creative Commons Attribution-ShareAlike 3.0 licence (CC BY-SA 3.0). The package code is under the ISC licence.