Version 1.2 · Effective 3 November 2026
This policy explains what data NudgeRoll for Jira (Release Check-ins & Answer Log) (the "app", or NudgeRoll) reads, writes, stores and logs, and how it is secured. The app is published on the Atlassian Marketplace by Myriastra Studio ("we", "us"), and is built on Atlassian Forge. The security disclosures are in section 8, Security. The data residency declaration is in section 6.
The app runs entirely on Atlassian's Forge platform, and Atlassian's eligibility check has reported each version we have checked as meeting the technical requirements for Atlassian's Runs on Atlassian program (see section 8). We operate no servers, no database and no analytics infrastructure of our own for this app. The app's manifest requests no permission to contact any host outside Atlassian, the app makes no network requests to such a host, and we operate no system that receives your data. The app runs no mail server: its emails are Jira notifications, which Atlassian sends to the email address on each recipient's Atlassian account — see section 3.
Once an hour, for each target project whose status mapping has been saved, the app reads, as itself: the project's id, key and project lead; whether the app can browse the project; whether the project uses an issue security scheme; and the work items in the project that are not in Jira's Done status category or that are in an unreleased fix version. For each of those work items it reads the key, summary, status, work item type, assignee, due date, fix versions, project, last update time and, if the project names a reviewer field, that field. It reads whether the assignees, project leads, added project leads and reviewers are active and still have access to Jira. It also reads the display name of a person whose answer is shown in a PM's email. Before it builds each person's email, it reads that person's work items again on their behalf — key, summary, status and due date — so that an email lists only work items both the app and its recipient can view (section 8).
For the same projects, the app reads, as itself, the work items updated since its previous run (key, work item type, assignee, fix versions, project and last update time) and their change history. From that history it keeps only changes to status, assignee and due date (section 4); the rest is discarded when the run ends.
When someone opens a NudgeRoll screen, the app reads what that screen needs on that person's behalf, with their own permissions: what they may do in the project, the work items they can view, a single work item and the transitions available from its status, the project's versions, the projects offered in the administration page, and people whose names they type to choose an assignee, a project lead, a PM or the fallback recipient. It also reads, as itself, the project's statuses for each work item type, the list of fields (to offer a reviewer field), the project's lead (for the answer page, the board and the PM view), whether the project lead and added project leads are active and still have access to Jira (on the board, the PM view and its export), whether each work item's assignee and reviewer are active and still have access to Jira (on the answer page, the board, the PM view and its export), the display name of a work item's reviewer on the board, the display names of the people shown in the PM view, its history and its export, and, when a project admin checks the transitions of a status mapping, the keys of a few work items in each status and the transitions available from them. When the app looks up a person, Jira's reply also says whether that person has access to Jira and what type of account it is; the app uses these only for the checks above and does not keep them. It reads your site's base address to build links. It does not request work item descriptions, comments or attachments; Jira's change history can include changes to them, and the app keeps only status, assignee and due date changes from it.
Apart from sending emails, this app writes to your Jira site only when someone answers: it moves the work item to the status mapped for that answer, sets its due date, or changes its assignee, each as the person who answered. If no direct transition exists or Jira rejects the change, it links to the work item instead. Emails are sent through Jira's own notifications, so Jira adds the app name, the project and the work item summary.
Once an hour, from the morning hour in the time zone a site admin chooses, the app asks Jira to send each person who has something to check one email for that day, addressed to their Atlassian account. The subject is "NudgeRoll: " followed by the number of items to check. In the default Full list format, the email lists the work items assigned to the recipient, the work items waiting on them as a project lead or reviewer, and, for a PM, each version's counts. A work item assigned to the recipient, or waiting on them as a project lead or reviewer, is shown by its key, summary, status and due date, with buttons that open the NudgeRoll answer page on your Jira site; a work item assigned to the recipient whose answer could not be applied also links to the work item in Jira, and a project lead's email links to the project lead board and the PM view. A PM's rows show the version name and counts, a link to the PM view, and each open work item's key, summary and state with the last answer on it and the display name of the person who gave it, linked to the work item in Jira; if Jira asks the app to retry a PM's email, the retried email leaves that name out. An email lists up to 100 work items; the rest are counted. In the Summary only format, the email holds the counts and a link to switch formats. In both formats Jira attaches the notification to one work item the recipient can view, and Jira's own wrapping shows that work item's project, key and summary.
The people who receive an email are the active assignee of a work item that needs a look or an answer, the project lead and any project leads added in the project settings (or the fallback recipient when the project lead is no longer active or no longer has access to Jira), the user in the project's reviewer field, and the PMs added in the project settings. The app does not use or store email addresses; Jira addresses the email.
NudgeRoll stores its data in Atlassian's Forge storage: the settings an admin saves (target projects, time zone, status mapping, and the account IDs of the admin who started sending and of added project leads, PMs and the fallback recipient), each person's email format choice, and a log per work item. The log holds who answered or acted and when, the answer, a new due date or assignee when one was set, and emails sent or failed. For work items updated in a target project, it also records changes made outside NudgeRoll to status, assignee or due date, with the account ID of the person who made them. It stores account IDs, work item keys and version IDs, not summaries or descriptions. The one exception is an email Jira asks the app to retry: its text, which can include work item summaries but no display names, is kept until a later hourly run tries to send it again, or for at most two years. It also keeps operational records: for each day and recipient, whether the email was sent, retried or failed; for each PM and version, how many work items are left open; and when its hourly runs happened. Log entries are kept for two years after the last entry on a work item, and operational records for two years after their date. Uninstalling the app leads to the deletion of the stored data, as section 9 describes. The app does not send data to any server outside Atlassian.
In more detail: the site settings hold the target project ids, the time zone and the fallback recipient's account id, and the record of who started sending holds that admin's account id and the time. Each project's settings hold the status ids in each group (Working, In review and Done), by default and per work item type, the reviewer field's id, the number of days without an update that makes a work item need a look, and the account ids of added project leads and PMs. Each log entry holds the work item key, its fix version ids, the assignee's account id at the time, what happened, who acted (an account id, or the app itself) and when; an email entry also holds the recipient's account id and their role, and a failed one its reason. An answer that changes the due date or the assignee also holds the previous value, and a change made outside NudgeRoll holds the old and new value of the field (for an assignee, account ids, which can be another person's). The app records changes made outside NudgeRoll for the work items its hourly run scans, up to a set number per run; a change it cannot tell apart from its own is not recorded, and the account id of the person who made a change is missing when Jira does not provide it. Each person's email format is one of two values, with when it was last changed, kept under their account id.
The operational records are: for each day and recipient, the outcome and, for a sent email, the key of the work item Jira attached it to; markers that a day's email to a recipient, or its retry, has been claimed, and the time each day's first sending run started; an email waiting to be retried, with its subject, its text and HTML body, the key of the work item Jira attaches it to, the keys, fix version ids, assignee ids and the recipient's role (assignee, project lead or reviewer) for the work items it lists in those roles, and when it was queued, which is removed after the retry attempt, or at the latest two years after it was queued; for each PM and version, the number of work items left open and when it was last set; for each hourly run, its counts and timings; the time of the latest sending run and of the one before it; and markers for where the last change-history scan and the last deletion run stopped. The app keeps no display names, no email addresses, and no descriptions or comments of work items. An email waiting to be retried can include work item summaries, status and version names and due dates; its text does not name the person who gave an answer, by display name or by account id.
The app writes lines to Forge's application log during its hourly and daily runs and when someone loads the project lead board or the PM view, exports a workbook, or answers several work items at once on the board. The hourly run writes a summary line with counts and timings; a daily run writes a summary line for its deletion run; and lines that name a project by its id or key when it skips the project or cannot read it. The screen lines carry counts, timings and the kind of screen only. When something goes wrong, a line can also carry the account id of a recipient, the key of a work item, and the error text as Jira or Forge returned it, which can itself contain such ids. We do not write summaries, display names or email addresses to the log ourselves. If a step fails, Forge may also keep its own record of the failure, which can include the error text. Forge logs are held on Atlassian's infrastructure and are retained according to Atlassian's platform policy; we read them only to diagnose faults, and we do not copy them anywhere else.
Atlassian asks each app to define and publish what it treats as in scope and out of scope for data residency. This section is that declaration. It adds no new processing — it restates what sections 2 to 5 already describe.
In scope: the data the app writes to Forge hosted storage, as listed in section 4 — the settings, account ids, answer log and operational records, including an email waiting to be retried. All of it is held exclusively in Forge hosted storage, which Atlassian operates. We operate no storage of our own, so where that data physically sits is determined by the Atlassian platform for the site the app is installed on, under Atlassian's data residency policy rather than under any arrangement of ours.
Read "exclusively" as: this app writes in-scope data to no store other than Forge hosted storage. It does not mean the values in section 5 appear nowhere else on Atlassian's infrastructure — see Platform logs below.
Out of scope:
Your Jira data. The statuses, due dates and assignees changed when someone answers are part of your Jira site, and Jira keeps them, and their history, under its own data residency, not this app's.
Emails. The app hands each email to Jira's notification service; Jira and Atlassian's email service then hold and send it under their own policies. The app keeps a copy only of an email waiting to be retried (in scope).
Data read but not used beyond a run. Of what the app reads (section 2), only what section 4 lists is kept. The rest — such as summaries, statuses, display names, transitions, permissions and the change history it does not record — is used while a run or a screen request lasts and discarded with it, except what an email waiting to be retried contains (section 4).
Platform logs. The lines described in section 5, and any record Forge keeps of a failed step, sit on Atlassian's logging infrastructure. Their location and retention are managed by Atlassian, not by this app, so we cannot offer a residency commitment over them. If your organisation needs a residency commitment that extends to platform logs, this app cannot give you one — please write to us before you buy rather than after.
The app has no sub-processors. It shares data with no third party, and it contains no analytics, advertising or tracking code. It builds the export workbook with the open-source ExcelJS library, which runs inside the app on Forge and sends nothing anywhere. Emails are sent by Jira, which is Atlassian's product, not a third party of ours. This page itself loads a web font from Google Fonts; the rest of the page is served by Cloudflare Pages.
This section is the security policy for NudgeRoll. Myriastra Studio is a one-person studio, and this app's security rests on how little the app is able to do, rather than on a formal security program. Most of what follows is a property of the app rather than a promise about us; the commitments we make are under Reporting a vulnerability.
Who is responsible for what. Atlassian provides the platform the app runs on: the infrastructure, tenant isolation, TLS in transit, encryption at rest for Forge storage, and the authentication of the people involved. We are responsible for the app itself: the permissions it asks for, what it does with them, what it writes to logs and storage, its dependencies, and fixing it when something is wrong. Nothing below asks you to treat Atlassian's own security attestations as ours.
The app has no server or endpoint of its own. There is no Myriastra Studio server, database, queue or endpoint anywhere in this app. It exists only as functions running on Atlassian's Forge platform, and its manifest requests no permission to contact any host outside Atlassian. Consistent with this, Atlassian's eligibility check has reported the versions we have checked as eligible for Atlassian's Runs on Atlassian program; that is a check on where data can go, not Atlassian vouching for the rest of our code. There is no web trigger and no URL of ours that anyone can call: the app's functions are run only by Atlassian, on hourly and daily schedules and from the app's own screens inside Jira, and each action on those screens checks who the person is and what they may do (below).
We do not receive your credentials. The app does not ask for, receive or store any API token, password or shared secret belonging to you or to anyone on your site. It authenticates to Jira with the identities Atlassian issues to it: its own app identity, and access on behalf of a person — the person using a screen, or, when the hourly run builds an email, its recipient.
The first time someone opens a NudgeRoll screen, Atlassian may ask them to allow this app to access Jira on their behalf. The app uses that access to show work items with their own permissions and to apply their answers as them. To build each email, the app reads Jira as the recipient, so an email holds only what that person can view.
The permissions we ask for. The app requests four scopes and no others: read:jira-work, write:jira-work, read:jira-user and storage:app. These are declared in the app's manifest, which lists what the app is able to do. read:jira-work is the only scope the app may use on a person's behalf while they are not using it; it does so to read each recipient's work items for their email. write:jira-work is used for the three changes in section 3 and to ask Jira to send notifications. Jira grants these scopes more broadly than the app uses them: they would also let an app make other changes to work items it can reach. This app makes only the changes in section 3, and it sends no request that deletes anything.
Encryption and storage. The app writes your data only to your Jira site and to Forge storage hosted by Atlassian. Encryption at rest and TLS in transit are provided by the Atlassian platform, not by us. We add no encryption of our own, and we operate no storage of our own.
Who can reach what. The administration page, its settings, Set up by pattern and Start sending require a Jira admin, checked on that person's behalf. A project's settings, and copying them to other projects, require a project admin of that project or a Jira admin. The answer page opens for people who can browse the project, for target projects only, and each answer is allowed by role: the assignee can answer Ready for review, Still working, Change due date or Unassign; a project lead can give those answers and also Send back and Change assignee; the reviewer can Confirm done, as can a project lead. Each person can change only their own email format. The person acting is taken from Jira's own context for the request, not from anything the screen sends.
Each email lists only work items both the app and its recipient can view. Screens show work items with the viewer's own permissions. The board opens for project leads and reviewers; the PM view, its history and its export, for anyone who can browse the project.
Our access to the app's operation is limited to publishing new versions of the app and reading Forge's application log (section 5), through the single Atlassian developer account that owns the app. We have no access to your Jira site, and this version of the app gives us no way to read the data it stores on your installation.
How the app is built and released. The app's runtime dependencies are Atlassian's own Forge packages, React and ExcelJS; it bundles no analytics, advertising or tracking library. Each release is built from a version-controlled source tree, and before each deployment we run the project's automated checks (manifest validation, code lint and tests). This is our own practice, not a pipeline that blocks a release by itself. Updates are delivered by Atlassian, not by us. According to Atlassian's documentation, a version that asks for new permissions is held until one of your administrators approves the new scopes, so this app cannot quietly widen what it is allowed to read or write.
Reporting a vulnerability. Please write to contact@myriastrastudio.com with security in the subject line, describing what you found and how to reproduce it. If you believe an issue is being actively exploited, say so in the subject line so that it is triaged first. Please test only against a site you control, and please do not access or modify data that is not yours. Please do not put customer data, exported workbooks, work item summaries or any other confidential material in your report. That mailbox is an ordinary email account outside Atlassian — the property that data stays inside Atlassian belongs to the app at runtime, and it does not extend to an email you send us.
We will acknowledge your report and tell you what we intend to do about it. Confirmed vulnerabilities are fixed on the timeline set by Atlassian's Security Bug Fix Policy, which applies to us as a Marketplace partner. We do not run a bug bounty, do not run continuous scanning or scheduled penetration tests, and cannot offer payment. If we become aware of a security incident affecting this app, we will investigate it, report it to Atlassian as the Marketplace Security Enforcement Policy requires, work with Atlassian on containment and a fix, describe it on this page, and contact affected installations wherever we are able to identify them.
What we do not have. So that a procurement team can rule us in or out quickly: Myriastra Studio holds no third-party security report or attestation of any kind, has not completed a CAIQ Lite assessment, and offers no separate data processing agreement. If your organisation requires any of those, this app is not yet a fit — please write to us before you buy rather than after. NudgeRoll records the answers your people give; it does not decide whether work is done.
A work item's log entries become due for deletion two years after its last entry, and are then deleted together. Operational records become due two years after their date, and an email waiting to be retried is removed after the retry attempt, or at the latest two years after it was queued. A daily run deletes what is due in batches of a limited size — a single work item's log is deleted as one batch even when it is larger — so the deletion happens on or after that date rather than at a set time; it continues while the license is inactive. Records the app cannot read are kept. Settings, email format choices, the record of who started sending and the app's status records (the date of its last run and the markers of where its last scans stopped) are not part of this deletion; they are replaced as they change and stay while the app is installed. There is no screen for deleting an answer or a person's account id from the app's records sooner.
The app does not delete anything in Jira. The statuses, due dates and assignees changed by answers, and Jira's history of those changes under the name of the person who answered, stay in Jira.
Uninstalling the app stops all further processing. According to Atlassian's Forge documentation, the app's Forge storage is then soft deleted and retained for 28 days, and what happens after that follows Atlassian's own data retention and disposal policy, not any action of ours. We cannot delete it sooner, so the data is not erased the instant you uninstall. Reinstalling the app starts a new installation; it is linked to the old data only if that is requested within 21 days of uninstalling. The .xlsx export holds only the last answer for each work item, not the full answer log, so export before uninstalling if you need that.
There is no setting that pauses sending for the whole site. A Jira admin can remove a project from the target projects (at least one must remain; to stop the app entirely, see below); its emails stop, and its answer page, board and PM view say that it is not a target project. An email that Jira asked the app to retry can still go out in the next hourly run.
If the app's license is inactive, no email is sent and changes made outside NudgeRoll are not collected until the license is active again; the screens and the export still open, but answers and settings are paused. The deletion of expired records (section 9) continues.
To stop the app entirely, a Jira administrator can uninstall it (section 9).
Because the app processes data only inside your own Atlassian site, requests about a specific person's data are usually best served by your Jira administrator, who controls that site. The app has no screen for deleting one person's account id from its records, and we have no access to your site, so we cannot delete it for you. Log entries and operational records are deleted two years after the dates described in section 9, and after uninstalling, the whole of the app's storage is left to Atlassian's retention and disposal (section 9). Changes made through the app stay in Jira's own history, which your administrators manage there. If you would like to contact us about this policy or about a data request, write to contact@myriastrastudio.com. If you are reporting a security vulnerability, please read section 8 first — it tells you what to include and, more importantly, what not to.
If we change how the app handles data, we will update this page and the version and date at the top of it.