Unitlane Apps policies
Unitlane Privacy Policy
This policy covers the Unitlane public website, support handling, and Unitlane software products including Seatwise, Bunlings: Scrum Poker & Retrospectives for Jira (with its two free editions), the Bunlings sprint apps (Bunlings Sprint Forecast, Bunlings Free Sprint Forecast, Bunlings Sprint History and Bunlings Free Sprint History), and Request Evidence Control for JSM, which is retired and no longer offered.
Who we are
- Provider: Jonas Nilsson, trading as Unitlane
- Privacy contact: Unitlane support
- Primary website: https://unitlane.net/
Scope
This policy applies to the public website, public documentation, support handling, and product operations where Unitlane acts as controller or processor as applicable.
Data we may process
- Contact information submitted through support or evaluation requests
- Tenant and site context needed to operate the products
- Operational product data required for review workflows, evidence handling, and settings
- Website access and security metadata needed to operate and protect the site
- Visit statistics for the website from Cloudflare Web Analytics: which pages are read, the referring site, browser and country, counted in aggregate. It uses no cookies, does not track you across other sites, and is not used to identify you.
Why we process it
- To provide and support the products
- To operate, secure, and improve the website and services
- To handle customer requests, trust review, and incident response
Seatwise
- Seatwise stores, for people on the customer’s Jira site: Atlassian account IDs, display names and avatar links, the groups that give them a Jira seat, facts about their Jira use (for example “no Jira work for 180 days”), and what they own (filters, dashboards, space lead and space roles).
- It also stores the reasons an administrator enters for keeping someone, the history of changes and who made them, and what Undo needs (for 30 days).
- If an administrator uploads Atlassian’s user export, Seatwise reads it in the browser and keeps only each person’s account ID, “last seen” date and “added to organization” date. The file itself is never kept.
- Seatwise does not store email addresses or anything from work items.
- Everything is stored in Forge app storage, hosted by Atlassian, and follows the site’s data residency. Seatwise makes no calls outside Atlassian, and its logs contain no names, account IDs or other personal data.
- Seatwise reports the accounts it stores to Atlassian about once a week. When Atlassian says an account was closed, Seatwise erases that person’s data; when a profile changes, it refreshes the stored name.
- After the app is uninstalled, Atlassian keeps the app’s storage for up to 30 days, then deletes it. Seatwise keeps no copy anywhere else.
Bunlings
- Bunlings: Scrum Poker & Retrospectives for Jira stores, for people on the customer’s Jira site: Atlassian account IDs linked to estimation rooms, rounds, votes and notes left with votes; retro cards, groups, votes, actions and lessons; personal settings. It also stores sprint snapshots and a summary of finished work per board, and the customer’s admin settings.
- Bunlings does not store email addresses or passwords. Names and pictures are read from Jira when a screen is shown.
- Everything is stored in Forge app storage, hosted by Atlassian, and held in the same location as the customer’s Jira. Bunlings makes no calls outside Atlassian, and its logs contain no names, account IDs or text people write.
- Changes in Jira (saved estimates, created work items, comments, hidden search markers) are made only when a person clicks, as that person. They are ordinary Jira data and stay in Jira.
- Bunlings keeps its data while the app is installed, so it can remember earlier sprints.
- Bunlings reports the accounts it stores to Atlassian about once a week. When Atlassian says an account was closed, Bunlings removes that person’s data from its storage.
- AI Referee is off by default. If a Jira admin on a paid licence turns it on, the text on screen, with names, mentions and email addresses removed, is sent to the AI model Atlassian provides to Forge apps. Nothing leaves Atlassian.
- After the app is uninstalled, Atlassian keeps the app’s storage for its retention period, then deletes it. Bunlings keeps no copy anywhere else.
Bunlings Sprint Forecast and Bunlings Sprint History
- This section covers Bunlings Sprint Forecast, Bunlings Free Sprint Forecast, Bunlings Sprint History and Bunlings Free Sprint History, Forge apps by Unitlane for Jira. They follow the same data practices as Bunlings above.
- They run on Atlassian (Forge) and are eligible for Runs on Atlassian. They use read-only Jira scopes and do not change anything in Jira.
- They store derived sprint data (figures worked out from finished sprints) and the customer’s settings in Forge app storage, held per Jira site and in the same location as the customer’s Jira. They do not store email addresses or passwords.
- Display names are read from Jira and kept in a cache for 1 hour, then discarded.
- They make no calls outside Atlassian and run no servers of Unitlane. Their logs contain no names, account IDs or text people write.
- They report the accounts they store to Atlassian about once a week. When Atlassian says an account was closed, the apps remove that person’s data from their storage.
- After an app is uninstalled, Atlassian keeps the app’s storage for its retention period, then deletes it. Unitlane keeps no copy anywhere else.
Effective date: April 15, 2026. Updated: 9 November 2026 (Bunlings Sprint Forecast and Sprint History apps added).