RepeatWise Privacy Policy
Last updated: October 11, 2026
1. Who we are
RepeatWise is an app for Jira Cloud (Atlassian Forge) published by Cocoon Care LLC (“we”, “us”). Cocoon Care LLC is a limited liability company formed in New Mexico, United States. Contact: admin@mycocooncare.com, 8206 Louisiana Blvd NE, Ste A #3669, Albuquerque, New Mexico 87113, United States.
2. Where your data lives
RepeatWise uses Atlassian Forge and makes no calls to outside servers: manifest.yml declares no permissions.external, and the app uses no analytics or email service. When a schedule fails, the app may ask Jira to send its owner a Jira notification about an issue the schedule created; Jira sends it, inside Atlassian. App records are stored in Atlassian-hosted Forge SQL; recurrence properties are stored on created Jira issues. The Custom UI also keeps a few values in your browser (listed in section 4 and never sent anywhere): the last selected project key and your Quick Start mode in localStorage, and whether you dismissed the attention banner in sessionStorage. CSV exports are built in your browser and saved to your device or clipboard; the app sends them nowhere. Feedback options open the Marketplace or your own email app; the app itself sends no email. We do not copy customer data to systems that we operate. Rovo conversations, Forge logs and backups are handled by Atlassian under Atlassian’s terms (see sections 4, 6 and 9).
3. Roles
- For the data described below, your organization decides why and how the data is used. In data-protection terms, your organization is the controller and Cocoon Care acts as a processor (or equivalent) when RepeatWise handles that data. We process it only to provide the app as described in this policy. If your organization needs a data processing agreement, write to us at the address in section 1.
- Atlassian hosts the data and is the infrastructure provider (a sub-processor of the app). Atlassian’s own terms and privacy policy apply to that hosting and to Jira itself (Atlassian Privacy Policy, Atlassian Trust Center).
4. Data RepeatWise stores
Stored in Forge SQL, per Jira site (tables from src/db/migrations.ts):
| Data | Content | Personal data? |
|---|---|---|
| Schedules | Name, Jira project key and id, owner’s Atlassian account id, status, recurrence rule, time zone, target time, holiday and exception settings, chaining and sprint options, run dates, error messages | Account id |
| Issue templates | Text you write for the issues to create: summary, description, sub-task summaries and descriptions, labels, priority, component/version/parent references, custom field values, chosen assignees, and for a service request the service desk and request type (id and name) | Account ids for assignees, including sub-task assignees and user-type custom fields, and any personal data you type in the text |
| Occurrence work | A copy of the issue template for an occurrence whose parent issue was created, plus created issue keys, warnings and error text | The same personal data as the template and possible personal data in error text |
| Request dispatch | For a service request: the summary, issue type, request type and time of the last create sent, kept to find that request again | Any personal data you typed in the summary |
| Occurrence log | Per planned run: date and time, status, created issue key, attempts, error text, due date | Indirectly (through the schedule owner) |
| Candidate log | Runs skipped or merged (for example holidays, or licence inactive) | No |
| Retry leases | Technical lock and next-retry time per occurrence | No |
| Occurrence dispatch | Account id that sent the last issue create, plus retry bookkeeping | Atlassian account id |
| Schedule audit | Action, time and what changed (in words, never an account id) for schedule changes, Run now and settings changes | Actor’s Atlassian account id |
| Review prompt | A user’s choice to defer or stop review reminders, and the time it was last updated | Atlassian account id |
| Settings | Who may create schedules, default time zone and holiday country, catch-up window and licence state | No |
RepeatWise also sets an issue property named recurrence (schedule id, occurrence number, UTC planned time and, for sub-tasks, index) on created issues. This is stored in Jira. The browser stores these values: in localStorage, repeatwise.lastProject (the last selected project key) and repeatwise.quickMode.<your Atlassian account ID> (Quick Start mode, form or natural); in sessionStorage, rw-attention-dismissed:<account ID> and rw-attention-announced:<account ID> (whether the attention banner was dismissed or announced in this browser session). Two of these keys contain your Atlassian account ID. They stay in your browser, which you can clear at any time, and RepeatWise does not send them anywhere.
For people identifiers, we store Atlassian account ids, not names, email addresses or avatars as separate identity fields. User-entered template text and Jira error text may themselves contain personal data; account ids are redacted from stored error text. When the app shows a person’s name (for example in the owner picker), it reads it from Jira on demand and does not store it as a separate identity field. Stored instants use UTC.
The Rovo suggestion action searches recent Jira issue keys, summaries, creation times and recurrence properties as the requesting user. It does not store those search results in Forge SQL; its response enters the Rovo conversation. The Rovo list action returns visible schedule details, including names and project keys, to the conversation. The Rovo create action 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 terms for Rovo and its AI features (Atlassian AI and Rovo trust); RepeatWise does not receive or store the conversation.
We do not knowingly process special categories of data. Because template text is free text, do not enter sensitive personal data in it.
5. Why we use it
- To create Jira issues on the schedule you defined, once and only once per occurrence (idempotency).
- To create those issues as the schedule owner (Forge impersonation), so Jira permissions apply.
- To show, edit and audit schedules and their history.
- To check that the app licence is active. The scheduler reads the licence state from the Forge invocation context; no other service is called.
- To suggest recurrence from recent Jira issues through Rovo, when requested by a user.
- To create and list schedules through Rovo, when requested by a user.
We do not sell data or use it for advertising, and we do not use it to train AI models. RepeatWise includes Rovo actions; the AI processing behind Rovo is done by Atlassian under its own terms, and RepeatWise has no AI model of its own.
Legal bases (if GDPR applies): performance of the contract with your organization and our legitimate interest in operating a reliable service.
6. Third-party access and sharing
We share data with no one. Atlassian hosts it as described above. Where we need to answer a support request, we may ask you for information; we never need direct access to your Jira site. We cannot browse your Forge storage. RepeatWise writes technical log lines: schedule ids, planned times, issue keys, statuses, error types and Jira error messages with account ids removed. It does not log templates, but a Jira error message can quote a value that was sent to Jira, such as a field value. For a production installation we can only read these logs if your site administrator allows log sharing with the app developer in Jira’s app settings.
7. International transfers
We do not transfer customer data ourselves. Location of storage and any transfer between Atlassian regions is governed by Atlassian’s Forge platform and its data residency features (Forge data residency). Where Atlassian supports it for Forge hosted storage, app data follows the data residency location of your Jira site.
8. Retention and deletion
- Schedules, templates and settings have no age-based purge while the app is installed. Deleting a schedule removes its schedule, template, candidate log, occurrence work and dispatch rows. Its occurrence history and schedule audit remain for the retention purge.
- 24-month deletion threshold: an hourly job deletes occurrence and candidate log rows by their event times, schedule audit rows by action time once their schedule is deleted (the audit of an existing schedule is kept while it exists; settings changes are deleted after 24 months), and review prompt choices when their
updated_attime is older than 24 months. When a user checks the review prompt, a choice older than 12 months is refreshed; a “never ask” choice therefore remains for active users and can be forgotten after 24 months of inactivity. The job uses bounded batches, so deletion may occur after the threshold rather than at an exact instant. - Execution records of an occurrence (the template copy and dispatch bookkeeping) are deleted about one day after the occurrence is final, and after 24 months in any case; those of an occurrence still in progress are kept until it ends. Expired retry leases and orphaned template, candidate, work and dispatch rows are also removed by maintenance.
- Uninstall: app data stored in Forge hosted storage is kept by Atlassian for 28 days after uninstall and then deleted. Within 21 days of uninstalling, you may ask us to request its recovery for a reinstalled app; we only do so with your consent (Forge storage reference). Jira issues created by the app stay in your Jira site.
- If the licence is inactive, maintenance pauses and deletes nothing until a later eligible run.
9. Security
- No external egress, so data is not sent outside the Atlassian platform.
- Requests to Jira use the minimum Forge scopes:
read:jira-work,write:jira-work(with impersonation of the schedule owner),read:sprint:jira-software,write:sprint:jira-software,read:board-scope:jira-software,read:project:jira,read:jira-user,read:servicedesk-request,write:servicedesk-request(Jira Service Management service requests), andreport:personal-data(the personal data report to Atlassian described in section 10). - Transport encryption, encryption at rest, backups and hosting security are provided by Atlassian’s Forge platform (Atlassian Trust Center).
- No secrets are stored in the app code.
No system is perfectly secure. If we become aware of a security incident affecting your data, we will inform affected customers without undue delay, and within 72 hours where the law requires it.
10. Your rights
Depending on where you are, you may have rights of access, correction, deletion, restriction, portability and objection. Because your organization is the controller, please contact your Jira site administrator first; we will help them answer. You can also write to us at the address in section 1. You may lodge a complaint with your data protection authority. We answer requests within 30 days. RepeatWise also follows Atlassian’s personal data reporting for apps: every 7 days it reports the Atlassian account ids it stores to Atlassian. When Atlassian says an account was closed, RepeatWise erases or anonymises the references to it: assignments go to the project default, user field values and mentions are removed, schedules owned by that account stop until an administrator gives them a new owner, and audit entries keep an anonymous actor. Records of an issue creation still in progress are kept until it ends, then deleted by maintenance within about a day.
11. Third-party notices
Public holiday data comes from the open-source date-holidays library, embedded in the app (no network calls). See the EULA, section 11, for attributions.
12. Changes
We may update this policy. We will change the date at the top and, for material changes, tell customers through the Atlassian Marketplace listing or the app at least 30 days before they take effect.
13. Contact
Cocoon Care LLC, 8206 Louisiana Blvd NE, Ste A #3669, Albuquerque, New Mexico 87113, United States. Email: admin@mycocooncare.com.