Security and data
Built so that your data never leaves Atlassian
Stepwise Checklists, Stepwise Approvals and Stepwise Secret & PII Scanner, for Jira and for Confluence, and Stepwise Poker, Stepwise Test Management, Stepwise Excel & PDF Exporter, Stepwise Time in Status and Stepwise Risk Register, for Jira, run on Atlassian Forge and nowhere else. The vendor operates no servers, so there is no second place where your checklists, approvals, findings, estimation sessions, test results, reports or risks could be copied, read or lost.
Architecture
The two checklist apps are built the same way and are installed separately. Each keeps checklists inside the product it belongs to and its own templates in its own Forge storage. They do not exchange data with each other.
Stepwise Checklists for Jira
- The checklist panel reads and saves the checklist of the open work item through Jira’s own interface, acting as the signed-in person. Jira applies that person’s permissions.
- For templates, the panel calls the app’s function, which runs on Atlassian Forge. The function first asks Jira whether the person may do what they ask: only space admins can change the templates of a space, only Jira admins the shared library.
- The function keeps templates in Forge hosted storage.
- When a work item is created, Jira notifies the function, and the function adds the templates that an admin has set to add automatically. This is the only time the app acts on its own rather than as a person.
Stepwise Checklists for Confluence
- The checklist, opened from the page byline or shown by the macro, reads and saves the checklist of the open page through Confluence’s own interface, acting as the signed-in person. Confluence applies that person’s permissions and page restrictions. The Checklists page of a space finds its pages the same way, with a Confluence search run as that person.
- For templates, the checklist calls the app’s function, which runs on Atlassian Forge. The function first asks Confluence whether the person may do what they ask: only space admins can change the templates of a space, only Confluence admins the shared library.
- The function keeps templates in Forge hosted storage.
- When a page is created, Confluence notifies the function, and the function adds the templates that an admin has set to add automatically. This is the only time the app acts on its own rather than as a person.
That is the whole system, for both apps. Neither declares any external address, so the Forge platform does not let them send data anywhere outside Atlassian.
Stepwise Approvals for Jira and for Confluence
The two approval apps are built like the checklist apps: Atlassian Forge only, no external address, no server of ours. They are installed separately and share no data with each other or with the checklist apps. Each keeps approvals, rules and the approval log in its own Forge hosted storage, kept separately for each site.
- A person opens the Approval panel or the Approval button under a page title. What they do in the app runs with their own permissions, so Jira and Confluence apply their own rules.
- The app reads and writes the approval in Forge hosted storage. Each action is one transaction: the approval and the log entries are saved together, or not at all, so two votes at the same moment are both recorded and the log chain does not fork.
- In Jira, a workflow validator checks the approval in the app’s own storage, not in a work item property, which anyone with edit rights could change. If the approval cannot be read, the transition does not pass.
- In Confluence, the badge under the title is computed from the approval record every time the page is shown. The app writes no page properties.
- Where no person is involved, the app acts on its own: the weekly personal data report and the automatic start of an approval by a rule. The Confluence app never calls Confluence as itself. The Jira app calls Jira as itself only to update the approval state used for search, to email reviewers when a rule starts an approval, and to look up a work item by its key for the transition check.
What the approval apps store
| Data | Where | Notes |
|---|---|---|
| Approvals: steps, reviewers, quorum, state, votes with comments, page version (Confluence) | Forge hosted storage of the app | People are stored as random references |
| Rules and read confirmations (Confluence) | Forge hosted storage of the app | Read confirmations hold references, not account IDs |
| Approval log | Forge hosted storage of the app | Entries are linked by SHA-256 hashes, one chain per space |
| Account IDs, linked to the random references | Forge hosted storage of the app | Needed to know who signed. Reported to Atlassian every week; erased when the account is closed. |
| Names, emails | Not stored | Names are shown as Atlassian returns them at the moment of display |
| State, missing approvals and round number for JQL (Jira) | In the work item, as the issue property stepwise.approval | No names, no account IDs |
| Page properties (Confluence) | Not written | The app writes none |
Personal data reporting and erasure
A scheduled job runs once a week and reports every stored account ID, with the date it was received, to Atlassian’s Personal Data Reporting API. If Atlassian answers that an account is closed, the app erases the account ID and its link to the reference. The person’s earlier actions stay in the log as “Former user”, and the log chain still verifies, because it is calculated from the reference. The apps do not write personal data or user text to their technical logs.
The approval log
Every log entry carries a SHA-256 hash of its content and of the entry before it, so any edit or deletion of an entry changes the chain. Premium can verify the chain of a space and export the log as CSV. The log is tamper-evident: a change is detected, not prevented. It is not a legal electronic signature.
Stepwise Approvals for Jira: five permissions
| Permission | Why the app needs it |
|---|---|
read:jira-work | To show the Approval panel, to fill the Approvals page of a space, and to ask Jira what the current person may see |
write:jira-work | To write the approval state and counters for JQL, and to send the email notification to reviewers |
read:jira-user | To search for people and groups when reviewers are picked, to show names at the moment they are displayed, and to know which groups a voting person belongs to |
storage:app | To keep approvals, rules and the log |
report:personal-data | To report stored account IDs to Atlassian every week |
Stepwise Approvals for Confluence: nine permissions
| Permission | Why the app needs it |
|---|---|
read:page:confluence | To read the title, the version and what the current person may do with the page |
read:space:confluence | To show the name of the space and to check whether the current person is a space admin |
read:confluence-user | To check whether the current person is a Confluence admin, to show names at the moment they are displayed, and to know which groups a voting person belongs to |
read:confluence-groups | To search for groups when reviewers are picked |
search:confluence | To search for people when reviewers are picked |
write:comment:confluence | To post the comment that mentions reviewers when approval is requested or reviewers are reminded, in the name of the person who clicked |
read:confluence-content.summary | To be told when a page is created or edited, so that rules start and edits are noticed |
storage:app | To keep approvals, rules and the log |
report:personal-data | To report stored account IDs to Atlassian every week |
The Confluence approval app has no permission to change pages. Neither approval app asks for any outside address.
Who can see and change what
- In Jira, seeing the approval requires access to the work item. Reviewers must be able to see it. The person who requested an approval cannot approve it.
- In Confluence, seeing the approval requires access to the page, requesting needs permission to edit it, and reviewers need only see it. Page restrictions apply.
- Rules are managed by space admins. The vendor has no access to your site or to the app’s storage.
When an approval app is uninstalled, Atlassian keeps its Forge hosted storage for 28 days and then erases it; a reinstall does not automatically restore it. In Jira the property stepwise.approval stays in the work items until you delete it through Jira’s REST API.
Stepwise Secret & PII Scanner for Jira and for Confluence
The two scanner apps are built like the others: Atlassian Forge only, no external address, no server of ours, no AI. They are installed separately and share no data with each other or with the other apps. Each keeps findings, the journal and its settings in its own Forge hosted storage, kept separately for each site.
- When Jira or Confluence reports that text was created or changed, the app reads that text as itself, because no person is present, and looks for secrets and personal data with built-in patterns and checks such as a checksum. The text is held in memory for the check only.
- The app saves a finding: where it is, what kind it is and its state. It does not save the value, a hash of it or any text around it.
- When an admin opens Preview, the app reads the text with that person’s own permissions and shows a short stretch of it with every found value hidden. Nothing is saved.
- In Jira only, and only if an admin turns it on, the app replaces a found value in a comment with a label. Before it writes, it checks that nothing else in the comment would change, and it keeps the comment’s visibility. If a check fails, it leaves the comment alone. It can also send an alert email through Jira to the groups an admin chooses. A workflow validator checks the text of a transition.
- In Confluence, the app has no permission to write. For old page versions it keeps only the numbers of the versions that held a kind of data.
- A history scan runs in the background in small chunks. Its position and counters are kept in the app’s storage.
What the scanner apps store
| Data | Where | Notes |
|---|---|---|
| Findings: space, work item or page, field or comment, kind, severity, state, match length, line and column, page version, timestamps | Forge hosted storage of the app | Removed findings are deleted after 180 days |
| Journal: time, action, space, item, field, kind, app or user | Forge hosted storage of the app | Entries are deleted after 13 months. Premium can export it as CSV. |
| Settings, scan state, old-version notes | Forge hosted storage of the app | Custom patterns (Premium) are stored here too |
| The found value, a hash of it, text around it | Not stored | A hash of a short value such as a card number or an SSN can be guessed, so none is kept |
| Account IDs, names, emails | Not stored | So the apps need no personal data reporting |
| Work item and page properties | Not written | The Jira app writes a masked comment only when an admin turns masking on |
Stepwise Secret & PII Scanner for Jira: four permissions
| Permission | Why the app needs it |
|---|---|
read:jira-work | To read work items, comments and text fields for the checks, to run the history scan, and to ask Jira what the current person may see |
write:jira-work | To save a masked comment when an admin turns masking on, and to send the alert email |
read:jira-user | To search for groups when alert recipients are picked. Group names are shown, never stored |
storage:app | To keep settings, findings, the journal and the scan state |
Stepwise Secret & PII Scanner for Confluence: six permissions
| Permission | Why the app needs it |
|---|---|
read:confluence-content.summary | To be told when a page, blog post or comment is created or edited |
read:page:confluence | To read pages and blog posts with their text and old versions |
read:comment:confluence | To read footer and inline comments |
read:space:confluence | To list spaces and to check whether the current person is a space admin |
read:confluence-user | To check whether the current person is a Confluence admin |
storage:app | To keep settings, findings, the journal and the scan state |
The Confluence scanner has no permission to change content. Neither scanner asks for any outside address.
Who can see and change what
- Jira and Confluence admins open the scanner, change rules and run scans. Space admins see the findings of their space and cannot change the rules.
- Findings show where something is, not what it is. Preview shows only what the person who opens it may see in Jira or Confluence.
- The vendor has no access to your site or to the app’s storage.
When a scanner app is uninstalled, Atlassian keeps its Forge hosted storage for 28 days and then erases it; a reinstall does not automatically restore it. Comments the Jira app has masked stay masked.
Stepwise Poker, Test Management, Excel & PDF Exporter, Time in Status and Risk Register for Jira
The five apps are built like the others: Atlassian Forge only, no external address, no server of ours, no AI. They are installed separately and share no data with each other or with the other apps. They differ in where each keeps its data and in how much each asks Jira for.
Stepwise Poker for Jira
- Everything a person does on a screen runs with that person’s own permissions: the screen and the app’s functions call Jira as the signed-in person. When a person joins a session, the app asks Jira what that person may do in the space, and asks again about every five minutes; a person who loses access to the space leaves the room.
- The only thing the app writes to Jira is the accepted estimate, to the estimate field, as the person who runs the session. Jira applies that person’s permissions and may refuse; then the estimate is not accepted, and the facilitator can retry, pick another card or accept without writing. The app writes no work item property.
- Sessions, votes, notes, the members of a session and settings are kept in Forge hosted storage. The server decides what a person sees: votes stay hidden until the facilitator reveals them, and a vote is saved by a transaction that checks the round is still open, so a vote and a reveal never cross.
- Live updates use the Forge platform’s Realtime channel. The signal carries no card, no name and no work item; every open screen then asks the app’s function for the room.
- The app listens to no Jira event and makes no call to Jira as the app. Its one background job runs weekly: it closes sessions that nobody touched for 30 days, deletes the summaries of sessions closed more than 13 months ago and reports the account IDs it still holds to Atlassian.
Stepwise Test Management for Jira
- The steps of a test are saved in the test work item as a Jira property, by the browser, acting as the signed-in person. Jira applies that person’s permissions. The server never writes steps.
- Cycles, runs and results are kept in Forge hosted storage. Each change of a cycle is one transaction, so two testers marking at the same moment cannot overwrite each other.
- Two more work item properties hold a result status and a coverage state for search. They hold no people and no step text, and decisions never read them: the transition check and the coverage report use the app’s own storage.
- Defects, imported test cases and coverage links are created as the signed-in person. CSV and JUnit files are read in the browser.
- Where no person is involved, the app acts on its own: the workflow check of a transition, a link made or removed in Jira, an hourly refresh of the search copies that a tester could not write, and the weekly personal data report.
Stepwise Excel & PDF Exporter for Jira
- When a person presses Export, the browser reads the chosen work items, with comments, worklogs and change history if asked, through Jira’s own interface as the signed-in person. Jira applies that person’s permissions, so a file holds only what that person may open.
- The file (Excel, CSV, PDF or Word) is built in the browser and saved to the person’s device. No server of ours ever sees a work item or a file.
- The app’s function keeps presets shared by a space or by the whole site, and template files, in Forge hosted storage. Its only call to Jira is to ask what the current person may do, before a shared preset is changed.
- The app has no events, no schedule and no background work. It never acts on its own.
Stepwise Time in Status for Jira
- The browser reads the work items of a query and their change history through Jira’s own interface as the signed-in person, and computes the report on screen. A work item the person may not open is not in the report.
- The app’s function keeps saved reports and working calendars in Forge hosted storage. Calendars are changed only by Jira admins, which the function checks with Jira.
- The app writes nothing to Jira and acts on its own in no case: it has no events and no schedule.
Stepwise Risk Register for Jira
- A risk is a Jira property of its work item, read and saved by the browser as the signed-in person. Jira applies that person’s permissions. The owner of a risk is the assignee of the work item; no account ID is stored.
- Space settings and the model library are kept in Forge hosted storage; settings are changed by space admins, the library by Jira admins.
- The two workflow rules that block a transition for an unassessed risk are Jira expressions that Jira evaluates itself. No function of the app runs, and the app is not involved.
- When a work item of a risk type is created, Jira notifies the app, and the app gives the new work item an empty risk, so that the rules can tell an unassessed risk from a work item that is not a risk. This is the only time the app acts on its own rather than as a person.
What the five apps store
| Data | Where | Notes |
|---|---|---|
| Poker: sessions (the work items they cover with their titles, the deck, the state, the results of each round) and settings | Forge hosted storage of the app | When a session is closed, only numbers for each work item stay, for 13 months |
| Poker: votes (a card and an optional note) and the members of a session | Forge hosted storage of the app | Tied to a random reference. Votes and notes are deleted when a work item is finished, all remaining votes and members when the session is closed. |
| Poker: account IDs of the people in an open session | Forge hosted storage of the app, in one table | Kept only while a session of that person is open. Reported to Atlassian every week; erased when the account is closed. Names and emails are not stored. |
| Poker: the accepted estimate | In the work item, in the estimate field chosen in the settings | Written as the person who runs the session. No work item property is written. |
| Test Management: steps, precondition and data sets of a test | In the test work item, as the Jira property stepwise.test | No people |
| Test Management: result status, counts and dates; coverage state | In work items, as the Jira properties stepwise.testresult and stepwise.coverage | For search only. No people, no step text. |
| Test Management: cycles, runs, latest results, the run log, settings | Forge hosted storage of the app | People are stored as random references. The run log is linked by SHA-256 hashes. |
| Test Management: account IDs of testers, assignees and authors | Forge hosted storage of the app | Needed to show who did what. Reported to Atlassian every week; erased when the account is closed. Names and emails are not stored. |
| Excel & PDF Exporter: presets of a space or of the whole site, and template files | Forge hosted storage of the app | A person’s own presets stay in that person’s browser only |
| Excel & PDF Exporter: work items and the files built from them | Not stored | Read and built in the browser, saved by the person to their own device |
| Time in Status: saved reports and working calendars | Forge hosted storage of the app | A saved report remembers its author by a one-way hash of the account ID with a random value of your installation, never by the account ID itself |
| Time in Status: work items, change history, report results | Not stored | Read from Jira and computed in the browser |
| Risk Register: a risk (probability, impact, strategy, category, review date, measures, summary) | In the work item, as the Jira property stepwise.risk | Numbers, dates, category names and work item ids. No people. |
| Risk Register: score history | In the work item, as the Jira property stepwise.risk.history | Time, steps, score and level. No people. |
| Risk Register: space settings and model library | Forge hosted storage of the app | Work types, risk models and categories |
| Account IDs, names, emails: Excel & PDF Exporter, Time in Status, Risk Register | Not stored | So these three apps need no personal data reporting |
Stepwise Poker for Jira: five permissions
| Permission | Why the app needs it |
|---|---|
read:jira-work | To read the work items of a sprint, the backlog or a query, the card shown in the room and the list of number fields, and to ask Jira what the current person may do |
write:jira-work | To write the accepted estimate to the estimate field, as the person who runs the session. Nothing else is written |
read:jira-user | To show the names of the people in the room. Names are shown, never stored |
storage:app | To keep sessions, votes and their notes, members and settings |
report:personal-data | To report stored account IDs to Atlassian every week |
The app asks for no Jira Software permission: a sprint, the backlog or a query is a JQL search, run as the person. It does not ask to manage Jira configuration.
Stepwise Test Management for Jira: five permissions
| Permission | Why the app needs it |
|---|---|
read:jira-work | To read work items, spaces, versions and link types, to search work items by JQL, and to ask Jira what the current person may do |
write:jira-work | To save the steps of a test and two search copies as work item properties, to create defects and imported test cases, and to create and remove coverage links, as the person who acts |
read:jira-user | To show tester names and to search for people when a run is assigned. Names are shown, never stored |
storage:app | To keep cycles, runs, results, the run log, settings and the people table |
report:personal-data | To report stored account IDs to Atlassian every week |
The app does not ask to manage Jira configuration: it does not create work types or link types.
Stepwise Excel & PDF Exporter for Jira: two permissions
| Permission | Why the app needs it |
|---|---|
read:jira-work | To read, as the signed-in person, the work items of a search with their comments, worklogs and change history, the field list, saved filters and spaces, and to ask Jira what the current person may do |
storage:app | To keep presets shared by a space or by the whole site, and template files |
The app has no write permission: it never changes a work item.
Stepwise Time in Status for Jira: two permissions
| Permission | Why the app needs it |
|---|---|
read:jira-work | To read, as the signed-in person, search results, change history and the lists of statuses and fields, and to ask Jira what the current person may do |
storage:app | To keep saved reports and working calendars |
The app has no write permission and does not ask to read users: the person’s time zone comes with the page, and assignee names come with the change history.
Stepwise Risk Register for Jira: three permissions
| Permission | Why the app needs it |
|---|---|
read:jira-work | To read work items, their risk property, spaces and search results for the register, to ask Jira what the current person may do, and to be told when a work item is created |
write:jira-work | To save a risk and its score history as work item properties, to create a work item when a person adds a measure, and to give a new risk work item its empty risk |
storage:app | To keep space settings and the model library |
The app does not ask to read users: the name of the assignee comes back with the work item. None of the five apps asks for any outside address.
Who can see and change what
- Poker: taking part in a session requires access to the space. The person who creates a session runs it, and a space admin can run it as well; the settings of a space are changed by space admins. The estimate is written with the rights of the person who runs the session, so Jira checks that person’s right to edit the work item.
- Test Management: seeing tests and results requires access to the space. Creating or changing a cycle, recording a result and assigning a run require “Edit work items”; deleting a cycle and changing the settings of a space require a space admin.
- Excel & PDF Exporter: a file holds only what the signed-in person may open in Jira. Presets of a space are saved by its space admins or by Jira admins; presets of the whole site by Jira admins.
- Time in Status: a report never shows more than Jira would show the person who runs it. Calendars are managed by Jira admins.
- Risk Register: seeing a risk requires access to the work item and assessing it requires “Edit work items”. Space settings are managed by space admins; the model library and the overview of all spaces by Jira admins.
- The vendor has no access to your site or to the storage of the apps.
When one of these apps is uninstalled, Atlassian keeps its Forge hosted storage for 28 days and then erases it; a reinstall does not automatically restore it. The properties the apps wrote into work items stay until you delete them through Jira’s REST API: stepwise.test, stepwise.testresult and stepwise.coverage for Test Management, stepwise.risk and stepwise.risk.history for Risk Register. Stepwise Poker wrote no properties; the estimates it wrote to the estimate field stay in the work items like any other value of that field.
Checklist apps: what is stored, and where
| Data | In the Jira app | In the Confluence app | How long |
|---|---|---|---|
| A checklist: the text of each step, its state, whether it is required or protected, the time it was completed, and the progress numbers | In the work item, as the Jira issue property stepwise.checklist | With the page, as the Confluence content property stepwise_checklist | As long as the work item or the page. It moves and gets deleted with it. |
| Templates: name, description, steps, and whether the template is added automatically | Forge hosted storage of the Jira app, kept separately for each Jira site. Includes the work types for automatic adding. | Forge hosted storage of the Confluence app, kept separately for each Confluence site | Until an admin deletes the template or the app is uninstalled |
| Account ids, names, emails | Not stored by the app | Not stored by the app | Not applicable |
Both apps record when a step was completed, not who completed it.
Checklist apps: permissions
Each app asks only for what it uses. Every permission has one job. The permissions of the approval apps are listed above.
Stepwise Checklists for Jira: three permissions
| Permission | What it allows | Why the app needs it |
|---|---|---|
read:jira-work | Read work items and spaces | To show the checklist of a work item, to fill the Checklists page of a space, to learn when a work item is created, and to ask Jira what the current person is allowed to do |
write:jira-work | Change work items | To save the checklist as a property of its work item. The app writes nothing else to a work item. |
storage:app | Use Forge hosted storage | To keep templates |
The Jira app does not ask to read users, to manage Jira configuration or to reach any outside address.
Stepwise Checklists for Confluence: seven permissions
Confluence splits access into narrower permissions than Jira does, so the list is longer.
| Permission | What it allows | Why the app needs it |
|---|---|---|
read:page:confluence | Read pages | To show the checklist of a page and to ask Confluence what the current person may do with that page |
write:page:confluence | Change pages | To save the checklist as a content property of its page. The app does not change the text of a page, and saving a checklist creates no new page version. |
read:space:confluence | Read spaces | To show the name of the space and to ask Confluence whether the current person is a space admin, before templates are changed |
read:confluence-user | Read the current user | Only to ask Confluence whether the current person is a Confluence admin, before the shared library is changed. Nothing from the profile is read or stored. |
search:confluence | Search Confluence | To find the pages with a checklist for the Checklists page of a space. The search runs as the signed-in person, so it returns only pages that person can view. |
read:confluence-content.summary | Read summaries of content | To be told when a page is created, so that templates set to add automatically can be added to it |
storage:app | Use Forge hosted storage | To keep templates |
The Confluence app does not ask to manage Confluence configuration or to reach any outside address.
Who can see and change what
- In Jira, seeing a checklist requires access to the work item, and editing it requires Jira’s “Edit work items” permission for that work item.
- In Confluence, seeing a checklist requires access to the page, and editing it requires permission to edit that page. Page restrictions apply.
- Templates of a space are managed by its space admins. The shared library is managed by Jira admins in the Jira app and by Confluence admins in the Confluence app.
- The vendor has no access to your site, your work items, your pages or your templates.
Data residency
Checklists are part of your work items and your pages, so they are stored wherever Atlassian keeps your Jira and Confluence data. Templates are in Forge hosted storage, which supports data residency and follows the location of your site. There is nothing to set up, and no data in any other region or with any other provider. The same holds for the other apps: what they keep is in Forge hosted storage or in properties of your work items, and follows the location of your site.
What is logged
Errors only. When an operation fails, the app writes one line to the Forge platform log: which operation failed, the type of error and the platform’s short message. It never logs checklist text, template text, test steps, votes, notes, report queries, risk data, request contents or account ids. This holds for every app.
The logs are kept by Atlassian on the Forge platform. The vendor can read them there to diagnose a fault. Atlassian gives site admins control over whether an app’s logs are shared with its vendor; the app keeps working either way.
Uninstalling
When an app is uninstalled, its templates are removed with it. Checklists remain where they are, because they are your Jira and Confluence data; reinstalling the app shows them again.
- Jira: checklists remain in the work items as issue properties. To remove one for good, use Remove checklist in the panel before uninstalling, or delete the property
stepwise.checklistthrough Jira’s REST API. - Confluence: checklists remain with the pages as content properties. To remove one for good, use Remove checklist in the checklist before uninstalling, or delete the content property
stepwise_checklistthrough Confluence’s REST API.
Uninstalling one app does not touch the other.
Report a vulnerability
Tell us what you found, how to reproduce it and what it could lead to. Please do not include real customer data in the report, and give us a reasonable time to fix the problem before you describe it in public. We aim to reply within 2 business days.
See also the privacy policy and the data sections of the docs: for Jira, for Confluence.