Legal
Privacy policy
Stepwise Checklists, Stepwise Approvals and Stepwise Secret & PII Scanner, each 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, keep your data inside Atlassian. We, the vendor, operate no servers and do not receive the content of your Jira or Confluence site.
In short
- Checklists are stored inside your work items in Jira and with your pages in Confluence. Templates are stored in Atlassian-hosted app storage. So are approvals, rules and the approval log of the Stepwise Approvals apps, and the estimation sessions, test cycles and results, saved reports, calendars and presets of the apps in section 2C. Test steps and risks are stored inside your Jira work items.
- The apps send nothing to us or to anyone else. There are no external servers, no analytics, no advertising and no third parties.
- The checklist apps do not store account ids, names or email addresses. The Stepwise Approvals apps store the account ids of requesters and reviewers, only in Atlassian-hosted app storage, report them to Atlassian every week and erase them when an account is closed. They never store names or email addresses (see section 2A). The Stepwise Secret & PII Scanner apps store where a finding is and what kind it is, never the found value, a hash of it or text around it, and no account IDs (see section 2B). Stepwise Poker keeps the account id of a person who joins a session only while a session of that person is open, and reports it to Atlassian every week; Stepwise Test Management stores account ids in the same way as the approval apps; Stepwise Excel & PDF Exporter and Stepwise Risk Register store none; Stepwise Time in Status stores none either, only a one-way hashed label of the author of a saved report (see section 2C).
- We receive personal data only when you contact us, and in the licence records that Atlassian shares with every Marketplace vendor.
- This website measures visits from our Google ads with Google’s tag, which can set Google cookies (see section 5). The apps have no trackers.
1. Who we are
Stepwise Checklists for Jira, Stepwise Checklists for Confluence, Stepwise Approvals for Jira, Stepwise Approvals for Confluence, Stepwise Secret & PII Scanner for Jira, Stepwise Secret & PII Scanner for Confluence, Stepwise Poker for Jira, Stepwise Test Management for Jira, Stepwise Excel & PDF Exporter for Jira, Stepwise Time in Status for Jira and Stepwise Risk Register for Jira are provided by Anatolii Voloshyn, Londres 8, 38660 Adeje, Santa Cruz de Tenerife, Spain (“we”, “us”). You can reach us at stepwise@pr.tools.
They are separate apps. In this policy “the app” means whichever of them you use, and everything said about it holds for all of them unless a product is named. Sections 2, 2A, 2B and 2C describe what each family of apps stores.
This policy covers the app, this website and our support by email. It does not cover Jira, Confluence or other Atlassian products, which are governed by Atlassian’s own privacy policy and by your organisation’s agreement with Atlassian.
2. What the app processes
The checklist apps work with two kinds of content that people in your organisation create:
| Content | What it contains | Where it is stored |
|---|---|---|
| Checklists | The text of each step, its state (open, done or not applicable), whether it is required or protected, the time it was completed, and progress numbers | Jira app: in the work item it belongs to, as a Jira issue property, on your Jira Cloud site. Confluence app: with the page it belongs to, as a Confluence content property, on your Confluence Cloud site. |
| Templates | Name, description, steps, and whether a template is added automatically (in Jira, for which work types) | In Forge hosted storage, the app storage that Atlassian provides for your site, kept separately for each of the two apps |
The checklist apps do not store account ids, names or email addresses, and they do not record who completed a step. While somebody uses the app, Jira or Confluence checks that person’s permissions; this happens inside Atlassian and the result is not kept by the app. The Confluence app also asks Confluence whether the current person is a Confluence admin: only the answer is used, and nothing from the person’s profile is read or kept.
Checklist and template text is written by your users. If they type personal data into a step, that text is stored like any other step text, in the places named above.
2A. Stepwise Approvals: what the apps process
Stepwise Approvals for Jira and Stepwise Approvals for Confluence also keep a record of who asked for and who gave an approval, because that is what an approval is. Unlike the checklist apps, they therefore store Atlassian account IDs. They store them only in Forge hosted storage on your site and nowhere else.
| Data | What it contains | Where it is stored |
|---|---|---|
| Approvals | For each request: the steps and their reviewers, the quorum, the state, the requester, the message and due date, the page version (Confluence), and each vote with its time and the comment the reviewer wrote (up to 500 characters) | Forge hosted storage of the app, kept separately for each site |
| Rules | Name, description, steps, reviewers, order, quorum and, in Confluence, re-review period and read confirmation; in Jira, work types and statuses | Forge hosted storage of the app |
| Approval log | One entry per event: time, action, the page or work item and its title, the version, the round, who did it and details such as step, decision and comment. Entries are linked by SHA-256 hashes. | Forge hosted storage of the app |
| Read confirmations (Confluence) | That a person has read a given approved version, and when | Forge hosted storage of the Confluence app |
| Account IDs | The Atlassian account ID of each requester and reviewer, linked to a random reference. Approvals, rules, the log and read confirmations contain the reference, not the account ID. Names and email addresses are not stored: names are shown as Atlassian returns them at the moment they are displayed. | Forge hosted storage of the app |
| State for search (Jira) | The approval state, the number of missing approvals and the round number. No names and no account IDs. | In the work item, as the Jira issue property stepwise.approval |
| Notification comment (Confluence) | A normal Confluence comment that mentions the reviewers, posted in the name of the person who requested the approval or pressed Remind reviewers | In Confluence, with the page, like any other comment |
The Confluence app writes no properties to pages. The Jira app writes nothing else to a work item. Reviewers are notified in Jira by an email notification that Jira sends.
Personal data reporting. Because the apps store account IDs, they follow Atlassian’s personal data reporting requirements. Once a week the apps send the stored account IDs, with the date each was received, to Atlassian through its Personal Data Reporting API. When Atlassian answers that an account is closed, the apps erase that account ID and its link to the random reference. The person’s earlier actions stay in the approval log as “Former user”, and the log can still be verified.
Comments, messages and titles are written by your users. If they contain personal data, it is stored like any other text, in the places named above. The apps do not write personal data or user text to their technical logs.
2B. Stepwise Secret & PII Scanner: what the apps process
Stepwise Secret & PII Scanner for Jira and Stepwise Secret & PII Scanner for Confluence read the text people write in your site, in order to find passwords, keys, tokens, card numbers and personal data. They keep a record of where something was found, not what it was. They store nothing outside Forge hosted storage on your site, and the Confluence app has no permission to change your content.
| Data | What it contains | Where it is stored |
|---|---|---|
| Findings | The space, the work item or page (its id and key), the field or comment, the kind of data, severity, state, the length of the match and its line and column, the page version (Confluence), whether a JSM comment was public or internal, when it was found and last seen, and whether the app or a person changed its state | Forge hosted storage of the app, kept separately for each site |
| Journal | One entry per event: time, action (found, masked, dismissed, scan started and so on), space, item, field, kind, and app or user | Forge hosted storage of the app |
| Settings | Which kinds are on, values to ignore, excluded spaces, the masking and create-check choices, alert group ids (Jira), and custom patterns (Premium) | Forge hosted storage of the app |
| Scan state and old-version notes | The position of a history scan and its counters; for Confluence pages, the numbers of the versions that held a kind of data | Forge hosted storage of the app |
| The found value, a hash of it, text around it | Not stored | Not applicable |
| Account IDs, names, email addresses | Not stored. The author’s address, if an admin chooses to email authors, is passed straight to Jira for that one email and not saved. | Not applicable |
While a person uses the app, Preview reads the text with that person’s own permissions and shows a short stretch of it with every found value hidden. It is not saved anywhere. The Jira app writes to your site in one case only: when an admin turns masking on, it replaces a found value in a comment with a label such as ***REDACTED: AWS key***. The scanner uses no AI and no outside service.
Because the apps store no account IDs, they do not need Atlassian’s personal data reporting. Group names are shown but not stored. Alert emails go out through Jira. The apps do not write found values or user text to their technical logs.
2C. Poker, Test Management, Excel & PDF Exporter, Time in Status and Risk Register: what the apps process
These five apps for Jira are separate from each other and from the apps above. Like the others, they keep everything inside Atlassian: in Forge hosted storage on your site and, for two of them, in properties of your work items. They send nothing to us or to anyone else.
Stepwise Poker for Jira
The app lets a team vote on work items and writes the accepted estimate to Jira. To show who is in a session it stores Atlassian account IDs, but only while a session of that person is open, and only in Forge hosted storage on your site.
| Data | What it contains | Where it is stored |
|---|---|---|
| Sessions | For each session: its name, the work items it covers (id, key and title), the deck, the mode (live or async), the state and the results of each round | Forge hosted storage of the app, kept separately for each site |
| Votes, notes and members | A card and an optional note (up to 300 characters) for each vote, and the list of people in a session, tied to a random reference. They stay while the session is open. When a work item is finished, its votes and notes are deleted; when the session is closed, all remaining votes and members are deleted. | Forge hosted storage of the app |
| Summaries of closed sessions | For each work item: the number of votes, the lowest, the highest, the average, the median, the agreement and the final estimate, with the title of the work item. Deleted 13 months after the session is closed. | Forge hosted storage of the app |
| Settings | The default deck, the field the estimate is written to, the round timer and the custom decks of each space | Forge hosted storage of the app |
| Account IDs | The Atlassian account ID of each person who joins a session, linked to a random reference. Sessions, votes and members contain the reference, not the account ID. A person is erased from the table when none of that person’s sessions is open any more. Names and email addresses are not stored: names are shown as Atlassian returns them at the moment they are displayed. | Forge hosted storage of the app, in one table |
| The accepted estimate | One value, written when the person who runs the session accepts it. The app writes nothing else to a work item, and no work item property. | In the work item, in the estimate field chosen in the settings |
Live updates use the Forge platform’s Realtime channel; the signal carries no card, no name and no work item. Personal data reporting. Once a week the app sends the account IDs it still holds to Atlassian through its Personal Data Reporting API and erases the account ID of every account that Atlassian reports as closed. The same weekly job closes sessions that nobody touched for 30 days and deletes the summaries of sessions closed more than 13 months ago. Session names, notes and titles are written by your users; if they contain personal data, it is stored like any other text, in the places named above.
Stepwise Test Management for Jira
The app records who ran a test and who is assigned to it. Like the approval apps, it therefore stores Atlassian account IDs, only in Forge hosted storage on your site.
| Data | What it contains | Where it is stored |
|---|---|---|
| Test steps | The precondition, the steps and the data sets of a test. No people. | In the test work item, as the Jira issue property stepwise.test |
| Search copies | For each test, a result status, a count and a date; for each requirement, a coverage state and a count. No people and no step text. | In the work item, as the Jira issue properties stepwise.testresult and stepwise.coverage |
| Cycles and runs | For each cycle: name, version or label, environment, description and state. For each run: its status, the result of each step with the text the tester wrote, a note, the time, the defect keys and a copy of the steps taken at the first result | Forge hosted storage of the app, kept separately for each site |
| Run log | One entry per action in a cycle. Entries are linked by SHA-256 hashes. | Forge hosted storage of the app |
| Settings | The work types, the link type, the defect type and the environments of each space | Forge hosted storage of the app |
| Account IDs | The Atlassian account ID of each tester, assignee and author, linked to a random reference. Cycles, runs and the log contain the reference, not the account ID. Names and email addresses are not stored: names are shown as Atlassian returns them at the moment they are displayed. | Forge hosted storage of the app |
Defects, imported test cases and coverage links are ordinary Jira work items and links, created as the person who acts. CSV and JUnit files are read in the browser. Personal data reporting. Once a week the app sends the stored account IDs to Atlassian through its Personal Data Reporting API and erases the account ID of every account that Atlassian reports as closed. Test steps, notes and titles are written by your users; if they contain personal data, it is stored like any other text, in the places named above.
Stepwise Excel & PDF Exporter for Jira
The app builds Excel, CSV, PDF and Word files in your browser. It reads your work items through Jira as the signed-in person and never changes them.
| Data | What it contains | Where it is stored |
|---|---|---|
| Presets of a space or of the whole site | A name and the settings of an export: format, columns and their names, extras, layout | Forge hosted storage of the app, kept separately for each site |
| Templates | A person’s own Excel or Word file with placeholders, up to 1 MB each | Forge hosted storage of the app |
| A person’s own presets | The same settings, saved by a person for themselves | In that person’s browser only. Nothing is sent to a server. |
| Work items and the files built from them | Not stored. The browser reads them from Jira, builds the file and saves it to the person’s device. | Not applicable |
| Account IDs, names, email addresses | Not stored | Not applicable |
Because the app stores no account IDs, it does not need Atlassian’s personal data reporting.
Stepwise Time in Status for Jira
The app reads the change history of your work items through Jira as the signed-in person, computes its reports in the browser and writes nothing to Jira.
| Data | What it contains | Where it is stored |
|---|---|---|
| Saved reports | A name and the settings of a report: the query (JQL) as typed, grouping, statuses, period, calendar and unit, and a label of the author (see below) | Forge hosted storage of the app, kept separately for each site |
| Working calendars | Hours for each weekday, holidays and a time zone | Forge hosted storage of the app |
| A random value of your installation | Used only to make the author labels | Forge hosted storage of the app |
| Work items, change history, report results | Not stored. The browser reads them from Jira and computes the report on screen. | Not applicable |
| Account IDs, names, email addresses | Not stored. The author of a saved report is remembered by a label: the first 16 characters of a one-way hash (HMAC-SHA256) of the account ID with the random value of your installation. This is a pseudonym, not anonymisation. If a person types an account ID into a saved query, it stays in that query as typed; the screen warns before saving. | Not applicable |
Assignee names come from Jira’s change history while a report is built; they are shown on the screen and in a CSV file that the person downloads, and are not stored. Because the app stores no account IDs, it does not use Atlassian’s personal data reporting.
Stepwise Risk Register for Jira
A risk is a property of an ordinary work item. The app stores no account ID and no name: the owner of a risk is the assignee of the work item.
| Data | What it contains | Where it is stored |
|---|---|---|
| A risk | Probability and impact before and after measures, the strategy, the category, the review date, the ids of the work items that are its measures, a summary for search (score, level, number of measures) and the time of the last change | In the work item, as the Jira issue property stepwise.risk |
| Score history | Time, steps, score and level of each change, up to 100 entries for a risk. No people. | In the work item, as the Jira issue property stepwise.risk.history |
| Space settings and models | The work types that are risks, the risk model of a space (steps, levels, categories) and the shared models | Forge hosted storage of the app, kept separately for each site |
| Account IDs, names, email addresses | Not stored. The name of the assignee is read from Jira when a screen is shown. | Not applicable |
Everyone who can see a work item can read its properties, so they hold only numbers, dates, category names and work item ids. Because the app stores no account IDs, it does not need Atlassian’s personal data reporting. The apps in this section do not write personal data or user text to their technical logs.
3. What we receive from the app
Nothing. The app runs entirely on Atlassian Forge, Atlassian’s platform for cloud apps. It has no connection to any server of ours or of a third party, and the platform does not let it open one. We cannot open your Jira or Confluence site, your work items, your pages, your checklists or your templates.
When an operation in the app fails, the app writes a short technical line to the platform log that Atlassian keeps: the operation that failed and the type of error. These lines contain no checklist text, no template text, no approval comments, no votes or notes, no test steps, no report queries, no risk data and no account ids. We can read them in Atlassian’s developer tools to find and fix faults. Atlassian lets site admins decide whether an app’s logs are shared with its vendor.
4. Atlassian’s role
Atlassian hosts Jira, Confluence and the Forge platform, and therefore stores and processes the content described in section 2 as the platform provider. It does so under your organisation’s agreement with Atlassian, including Atlassian’s data processing terms and privacy policy. Your organisation decides what is entered into Jira and Confluence and who may see it, and remains responsible for that content.
Atlassian also runs the Marketplace through which the app is obtained. Orders, payments, invoices, refunds and trials are handled by Atlassian under Atlassian’s Marketplace terms. We do not receive or process payment card details.
5. Personal data we do receive
When you contact us
If you write to us for support, to report a security problem or with a question, we receive your email address, your name if you give it, and whatever you put in the message or attach to it. We use this to answer you, to fix what you report and to improve the app. Please do not send confidential content from your Jira or Confluence site; hide it in screenshots.
Licence records from Atlassian
Atlassian makes licence and sales records available to every Marketplace vendor. For an installation of the app these can include the name of the organisation, the address of the Atlassian site, which app it is, the edition and licence dates, and the names and email addresses of the technical and billing contacts on the order. We use these records to administer licences, to provide support, to keep our accounts and to meet legal obligations. We do not use them for advertising and do not sell them.
This website
This website is a set of static pages with no forms. The pages themselves set no cookies. To measure the visits that come from our Google ads, we use Google’s tag (Google Ads): our content delivery network, Cloudflare, adds it to the pages and serves it from this website’s own address. The tag can set Google cookies, such as _gcl_au and _ga, and sends Google information about your visit, which can include the page, the time, your browser and device and your IP address. Google handles this information under its own privacy policy, policies.google.com/privacy. You can block these cookies in your browser settings or with a tracker blocker; the website works the same without them. The tag runs only on this website, never inside the apps. Cloudflare and the company that hosts the website may keep standard server logs (such as IP address, time and the page requested) for security and operation.
6. Why we may use this data
Where the law asks for a legal basis, we rely on the following: answering your request and providing the app under our terms (performance of a contract, or steps before entering one); our legitimate interest in keeping the app secure and working and in administering licences; and legal obligations, for example keeping accounting records.
7. Who we share it with
We do not sell personal data. Apart from Google’s tag on this website, which measures visits from our ads (section 5), we do not share it for advertising. We use service providers only for what is needed to run our business, such as email and accounting, and they may process the data described in section 5 on our behalf. We may disclose data if the law requires it. Content stored by the app (section 2) is never part of this, because we do not have it.
8. How long data is kept
- Checklists stay in a work item or with a page for as long as that work item or page exists, or until somebody removes the checklist. They are deleted together with it.
- Templates stay until an admin deletes them or the app is uninstalled.
- Approvals, the approval log and read confirmations stay in the app’s storage while the app is installed. Rules stay until an admin deletes them. An account id and its link to a random reference are erased when Atlassian reports the account as closed.
- Scanner journal and findings stay in the app’s storage while the app is installed. Journal entries are removed after 13 months and findings marked as removed after 180 days. Settings stay until an admin changes them or the app is uninstalled.
- Poker votes and notes are deleted when a work item is finished. All remaining votes, the members of a session and their account ids are deleted when the session is closed, either by the person who runs it or by a weekly job after 30 days without activity. Summaries of closed sessions are deleted after 13 months, and settings stay until an admin changes them or the app is uninstalled. An account id is also erased when Atlassian reports the account as closed.
- Test Management cycles, runs, results and the run log stay in the app’s storage while the app is installed; an account id and its link to a random reference are erased when Atlassian reports the account as closed. Test steps and search copies stay in the work item for as long as it exists.
- Excel & PDF Exporter presets and templates stay until an admin deletes them or the app is uninstalled. A person’s own presets stay in that person’s browser.
- Time in Status reports and calendars stay until a person or an admin deletes them or the app is uninstalled.
- Risk Register risks stay in their work items for as long as the work item exists; space settings and the model library stay until an admin changes them or the app is uninstalled.
- Cookies set by Google’s tag on this website stay in your browser until they expire or you delete them; Google keeps the information under its own policy.
- Support messages are kept for as long as needed to resolve the request and to keep a record of it, and are then deleted.
- Licence records are kept for as long as the licence is active and afterwards for as long as accounting and tax rules require.
9. Uninstalling the app
When the app is uninstalled from a site, the templates in the app’s storage are removed with it by Atlassian. Checklists are your Jira and Confluence data: they remain in the work items as issue properties, or with the pages as content properties, and become visible again if the app is reinstalled. To delete them, remove the checklist in the app before uninstalling, or delete the issue property stepwise.checklist through Jira’s REST API or the content property stepwise_checklist through Confluence’s REST API. We cannot do this for you, because we have no access to your site.
For the Stepwise Approvals and Stepwise Secret & PII Scanner apps: Atlassian keeps Forge hosted storage for 28 days after an app is uninstalled and then erases it, and a reinstall does not automatically restore it. In Jira, the issue property stepwise.approval remains in the work items; you can delete it through Jira’s REST API. In Confluence, the notification comments remain with the pages as ordinary comments.
The same holds for the apps in section 2C: Atlassian keeps their Forge hosted storage for 28 days after an uninstall and then erases it. What they wrote into Jira stays: the issue properties stepwise.test, stepwise.testresult and stepwise.coverage (Test Management) and stepwise.risk and stepwise.risk.history (Risk Register); you can delete them through Jira’s REST API. Presets that people saved in their own browser stay in that browser. Stepwise Poker wrote no work item properties; the estimates it wrote to the estimate field stay in the work items like any other value of that field.
10. Where data is located
Content stored by the app stays within Atlassian’s cloud and follows the data residency of your Jira or Confluence site: checklists are part of your work items and pages, and Forge hosted storage supports data residency. The app does not transfer this content anywhere else.
Support messages and licence records are processed where we and our service providers operate. Where that involves a transfer of personal data to another country, we use the safeguards the applicable law requires.
11. Your rights
Depending on where you live, you may have the right to ask for access to your personal data, for its correction or deletion, to restrict or object to its use, to receive a copy of it, and to complain to a data protection authority. To use these rights for data we hold (section 5), write to stepwise@pr.tools.
For content inside Jira or Confluence, including checklists, templates, approvals, the approval log, estimation sessions, test cases and results, reports and risks, please turn to the administrator of your Atlassian site or to your organisation. They control that data; we have no access to it.
12. Security
The app relies on the security of the Atlassian platform and adds no systems of its own that could be attacked. How it is built is described on the security page.
13. Changes to this policy
If we change this policy, we will publish the new version on this page and change the effective date above. If a change affects how the app handles your data, we will also describe it in the release notes of the app.
14. Contact
Anatolii Voloshyn
Londres 8, 38660 Adeje, Santa Cruz de Tenerife, Spain
stepwise@pr.tools